Juniper Networks 5XT User Manual

Page of 42
Juniper Networks
NetScreen Release Notes
ScreenOS 5.0.0r9-FIPS
P/N  093-1638-000, Rev. A
Page 21 of 42
4.3 Addressed Issues from ScreenOS 5.0.0r7
Manufacturing-only release.
4.4 Addressed Issues from ScreenOS 5.0.0r6
• 38268 – A Juniper Networks security appliance running a BGP peer virtual 
routing instance cannot use an MD5 type password when the device is 
connected to a Juniper Networks router.
• 38200 – A non-specific error in H323 caused memory leaks in device 
sessions.
• 38103 – The DHCP client was unable to obtain an IP address if Dynamic 
Track IP was enabled and the DHCP client interface was down. 
• 37711 – When you have established a VPN tunnel and tried to perform a 
Phase II rekey, the operation intermittently failed.
• 02449 – The server kept sending LCP requests as if it never received a 
packet because the PPP (Point-to-Point Protocol) request sent out never left 
the device.
• 02446 – Unfreed memory buffers could be allocated to the point where the 
device could not send management traffic data.
• 02429 – HTTP packets could not pass through the Juniper NetScreen-5200 
running ScreenOS 4.0.0 if you issue both the unset flow tcp seq and set 
flow tcp syn
 commands.
• 02419 – The WebUI label IP Sweep/Port Scan in the IP and Port Scan 
field in the Screen menu contained incorrect references to milliseconds (5000 
ms) instead of microseconds with the ms abbreviation (ms is the 
abbreviation for milliseconds).
• 02416 – If you rebooted a Juniper NetScreen-5200 after configuring NHTB 
entries in the current session on the system, the device lost the entries after 
the reboot. 
• 02415 – A RIP routing instance dropped the default route (0.0.0.0) of another 
routing instance if it learned it on an unnumbered tunnel interface.
• 02413 – When you issued the command set ike gateway, the device always 
created a test certificate peer certificate type x509-signature.
• 02411 – An NSRP Track-IP session on a sub-interface failed in instances 
when the target address and the default route (0.0.0.0) were on the same 
subnet. In these instances, the Track IP query incorrectly selected the 
default route (0.0.0.0). 
• 02387 – The command line displayed only 24 characters for a URL string, 
although ScreenOS supports URL strings with up to 64 characters.