Juniper Networks
NetScreen Release Notes
Product: NetScreen-Hardware Security Client, NetScreen-5XT,NetScreen-5GT, NetScreen-25, NetScreen-50, NetScreen-204,
NetScreen-208, NetScreen-500, NetScreen-ISG 2000, NetScreen-5200,
NetScreen-5400
Version: ScreenOS 5.0.0r8
Release Status: Public Release
Part Number: 093-1342-000, Rev. C
Date: 08-26-04

Contents
1. Version Summary on page 2
2. New Features and Enhancements on page 3
2.1 New Features and Enhancements for ScreenOS 5.0.0r8 on page 3
2.1.1 About the 5000-M2 on page 4
2.2 New Features and Enhancements for ScreenOS 5.0.0r6 on page 4
2.3 New Features and Enhancements for ScreenOS 5.0.0r1 on page 5
3. Changes to Default Behavior on page 5
4. Addressed Issues on page 5
4.1 Addressed Issues in ScreenOS 5.0.0r8 on page 5
4.2 Addressed Issues from ScreenOS 5.0.0r7 on page 14
4.3 Addressed Issues from ScreenOS 5.0.0r6 on page 14
4.4 Addressed Issues from ScreenOS 5.0.0r5 on page 16
4.5 Addressed Issues from ScreenOS 5.0.0r4 on page 16
4.6 Addressed Issues from Previous Releases on page 20
5. Known Issues on page 21
5.1 Limitations of Features in ScreenOS 5.0.0 on page 22
5.2 Compatibility Issues in ScreenOS 5.0.0 on page 23
5.2.1 Upgrade Paths from Previous Releases on page 24

ScreenOS 5.0.0r8

P/N 093-1342-000, Rev. C

Page 1 of 32

Juniper Networks

NetScreen Release Notes

5.3 Known Issues in ScreenOS 5.0.0 on page 24
5.3.1 Known Issues in ScreenOS 5.0.0r8 on page 24
5.3.2 Known Issues from ScreenOS 5.0.0r7 on page 26
5.3.3 Known Issues from ScreenOS 5.0.0r6 on page 26
5.3.4 Known Issues from ScreenOS 5.0.0r5 on page 26
5.3.5 Known Issues from ScreenOS 5.0.0r4 on page 27
5.3.6 Known Issues in ScreenOS 5.0.0r3 for the 5000-M2 on page 27
5.3.7 Known Issues from ScreenOS 5.0.0r3 on page 28
5.3.8 Known Issues from ScreenOS 5.0.0r2 on page 28
5.3.9 Known Issues from ScreenOS 5.0.0r1 on page 29
5.3.10 Known Issues from Previous Releases on page 31
6. Getting Help on page 32

1. Version Summary
ScreenOS 5.0.0r8 is the latest version of ScreenOS firmware for the NetScreenHardware Security Client, NetScreen-5XP, NetScreen-5XT, NetScreen-5GT,
NetScreen-25, NetScreen-50, NetScreen-200 Series security appliances, and the
NetScreen-500, NetScreen-ISG 2000, and NetScreen-5000 Series security
systems.
The ScreenOS 5.0.0r8 release is interoperable with, and provides basic support for
all versions of NetScreen Remote and ScreenOS 2.6.1 and later versions.
This version of ScreenOS is fully supported by Security Manager, Juniper
Networks-NetScreen's security management platform.
This version of ScreenOS also supports selection of either the Baseline orAdvanced version of the firmware. To access a specific Advanced feature, you needto purchase the appropriate Advanced feature key.
Refer to the following table to understand what ScreenOS versions map to which
product.

ScreenOS 5.0.0r8

Product

Firmware

NetScreen-Hardware Security Client

ns5gt.5.0.0r8.1

NetScreen-5XT

ns5xt.5.0.0r8.0

NetScreen-5GT

ns5gt.5.0.0r8.1

NetScreen-25

ns50ns25.5.0.0r8.0

P/N 093-1342-000, Rev. C

Page 2 of 32

Juniper Networks

NetScreen Release Notes

NetScreen-50

ns50ns25.5.0.0r8.0

NetScreen-200 Series

ns200.5.0.0r8.0

NetScreen-500

ns500.5.0.0r8.0

NetScreen-ISG 2000

nsISG2000.5.0.0r8.2

NetScreen-5000 Series (with 5000-M)

ns5000.5.0.0r8.0

NetScreen-5000 Series (with 5000-M2)

ns5002.5.0.0r8.3

2. New Features and Enhancements
The following sections detail new features and enhancements in ScreenOS 5.0.0
releases. For a complete list and descriptions of new features and enhancements
in ScreenOS 5.0.0, refer to the NetScreen ScreenOS Migration Guide.

2.1 New Features and Enhancements for ScreenOS 5.0.0r8
Destination NAT Enhancement – An enhancement has been added to thedestination NAT feature to allow ARP responses for addresses that are on thesame subnet as the device's interface. For further information on this featureplease see the Juniper Networks/NetScreen Knowledgebase.
Scan Engine Update for NetScreen-5GT and NetScreen-HSC – ScreenOS
now embeds Trend Micro’s new scan engine version 7.0 to provide better scanning
coverage and increase performance. All previous versions of pattern files will becompatible with this new version.
As part of the Scan Engine Update, Juniper Networks implemented the ability toincrease scanning coverage using the following commands:• set av http skipmime• unset av http skipmime
Note: The feature may impact performance on the device for traffic that may
match embedded text in HTML packets.
According to Trend Micro, the categories of viruses bypassed include HTML andJavascript. However, the subset of the bypassed viruses can be described as thefollowing:Javascript/Jscript/HTML embedded in HTML code (having HTTP content
type of text/HTML) AND is accessed through a script-enabled browser from aremote web server (via HTTP).

ScreenOS 5.0.0r8

P/N 093-1342-000, Rev. C

Page 3 of 32

Juniper Networks

NetScreen Release Notes

For example, anti-virus scanning would NOT be bypassed for the following
scenarios:
1. Javascript/HTML malware which is stand-alone in a *.js file
2. Javascript/HTML malware propagating via email attachments
So the viruses bypassed would be all Javascript and HTML based viruses, butaccessed or contained with the above characteristics in HTTP traffic only.

2.1.1 About the 5000-M2
The 5000-M2 can be installed into a NetScreen-5000 Series system, either a
NetScreen-5200, a two-slot chassis system, or a NetScreen-5400, a four-slot
chassis system. The previous version of ScreenOS firmware that supported a
5000-M2 configuration was ScreenOS 5.0.0r3.
The NetScreen-5000 Series systems can be configured with either a 5000-M or
5000-M2 Management Module. The 5000-M2 Management Module is basedaround powerful, dual 1GHz PowerPC CPUs which assists other system elements,
primarily with traffic-related tasks. The 5000-M2 management module provides
overall management and control of the systems.
Features of the 5000-M2 module include:• A management port, for WebUI management sessions or Command LineInterface sessions.
• A console port, for serial terminal emulation programs such as
HyperTerminal.
• Two High Availability (HA) ports.
• A modem port.
The 5000-M2 also has port Link and Activity LEDs, CPU utilization indicators, aHigh Availability (HA) LED, an Alarm LED, a Status LED, a Flash LED, and a
Power LED. In addition, it has a compact flash slot for flash memory card
installation.

2.2 New Features and Enhancements for ScreenOS 5.0.0r6
New Hidden Command - In response to the NISCC VULN 236929, a new
hidden command is implemented in this release. The command is set/unset flow
check tcp-rst-sequence. By default, the command is not set. This command
alters the device’s response to potentially spoofed TCP RST packets.

ScreenOS 5.0.0r8

P/N 093-1342-000, Rev. C

Page 4 of 32

Juniper Networks

NetScreen Release Notes

2.3 New Features and Enhancements for ScreenOS 5.0.0r1
NetScreen-5GT - Dial Backup, Dual Untrust, OSPF, and BGP are now available
in the 10-user version. Previously these features were only available in the Plus
version.
NetScreen-5GT - The Extended version provides the same capabilities as thePlus version with additional features: High Availability (NSRP Lite), the DMZ
security zone, and additional sessions and tunnel capacity. For information onthese features, refer to the NetScreen ScreenOS Concepts & Examples Reference
Guide for ScreenOS 5.0.0.
Note: You must register your product at www.juniper.net/support so that certain
ScreenOS features, such as antivirus or deep inspection, can be activated on thedevice. If you already have an account, enter your user ID and password; if you are a
new NetScreen customer, create your account first. To register your product, youneed the model and serial number of the device. After registering your product,confirm that your device has internet connectivity. Issue the CLI command exec
license-key update to make the device connect to the NetScreen server to activate
the feature.

3. Changes to Default Behavior
There are numerous changes in default behavior. For detailed information onchanges to default behavior in ScreenOS 5.0.0, refer to the NetScreen ScreenOS
Migration Guide.

4. Addressed Issues
The following sections detail addressed issues in each release of 5.0.0.

4.1 Addressed Issues in ScreenOS 5.0.0r8• 40292 – A potential cross-site scripting attack existed in the anti-virus scanengine when processing compressed files.
• 39458 – You could not configure 16 concurrent anti-virus messages, theexpected maximum number of messages allowed when running the antivirus Scan Manager utility in the WebUI.
• 39087 – In certain circumstances, the first attempt to access a TCP
application through a NetScreen-5000 system with authentication failed
when the ARP entry for the application was not present.

ScreenOS 5.0.0r8

P/N 093-1342-000, Rev. C

Page 5 of 32

Juniper Networks

NetScreen Release Notes• 38193 – A NetScreen-5GT could not access common public web sites when an
administrator performed an anti-virus scan for HTTP on the device. The
attempted connections will expire after they exceed the time out thresholdfor connection attempts.
• 37933, 37945 – If a number of different attacks entered the NetScreen-5000
Series system over a period of time, the system sometimes began to drop
packets.
• 36708 – You could not view the traffic logs for a Vsys if you entered the Vsys
as a root admin user.
• 36670 – You could create more VLANs on a NetScreen device than thenumber of VLANs the device officially supported. However, doing thissometimes caused unexpected results. Refer to the specifications sheet foryour NetScreen product to learn how many VLANs it supports.
• 36494 – Upon startup, NetScreen devices using PPPoE sometimes generated
a warning message informing that the interface gateway command wasinvalid. This is a result of the gateway changing whenever the device
restarts and does not effect the normal operation of the device.
• 36473 – Restarting a NetScreen device while it was performing an operationin flash sometimes damaged the data on the device and caused the device notto restart or to lose the configuration.
• 36235 – Adding the pre-defined service entry "ANY" in a multiple service
policy sometimes resulted in a system reboot.
• 36095 – You could not change the IP address of an interface if a VIP or MIP
was configured on that interface, and the VIP or MIP was used in a policy
configuration. DHCP and PPPoE could not change the interface IP address if
a VIP was configured using the same-as-interface option.
• 35977 - (NetScreen-5XT only) The NetScreen device sometimes dropped TCP
traffic because it miscalculated the length of the tcp-syn-check.
• 35904 – (NetScreen-5GT only) NetScreen devices needed to support two
incoming IPSec keys. When the software lifetime was in use and after the rekey was successful, the device should have permitted traffic using older SA's
to traverse the device.
• 35735 – A root administrator could not manage the root system from a hostthat resided on a virtual system.
• 35624 – If you set the negotiation mode on a 10/100 Ethernet port to Full
Duplex and configured the holddown time on the interface to less than one
second, it caused the interfaces to go up and down.
• 35615 – (NetScreen-5GT only) Any policies within the device indicatedtraffic shaping was active for the policy. Issuing a 'get policy' CLI command
displayed an "X" under the "T", for traffic shaping, in each policy. However,

ScreenOS 5.0.0r8

P/N 093-1342-000, Rev. C

Page 6 of 32

Juniper Networks

NetScreen Release Notes

issuing a 'get policy id <number>' CLI command indicated that traffic
shaping was turned "off".
• 35528 – In an active-passive NSRP configuration, you needed to set a
manage IP on both devices to enable each device to connect to theentitlement server and retrieve signatures.
• 34279 – (For NetScreen-5000 Series) NetScreen devices sometimes
unexpectedly dropped traffic that was processed by the CPU module andthat matched a policy in which the “Diffserv” option was enabled.
• 03396 – (NetScreen-ISG 2000 only) When you logged into a system, theEvent log displayed two incorrect messages. The messages displayed are:
The NetScreen device was unable to complete the upgrade of thefile system.
andThe NetScreen device was unable to complete the upgrade of theloader.
• 03232 – Under some conditions, an HA (High Availability) pair with a 5000M2 module installed failed. This occurred when the primary device had
4,000 sessions on it and the backup device had 100,000 sessions.
• 03147 – (NetScreen-ISG 2000 only) In the Policies dialog box under theReports menu in the WebUI, when you clicked on the counter icon thatmeasures how many bytes pass through the device associated with a given
policy, the system failed.
• 29619 – When you used the CLI to configure SCEP, you could not specify analready defined Certificate Authority as the recipient of the certificate
requests.
• 02973 – (NetScreen-ISG 2000 only) When receiving and processing
incorrectly formatted packets with unknown tags, the system sometimes
performed a coredump operation from misplacing these packets in thememory pool.
• 02940 – The device sent out multiple SNMP traps associated with the same
event after you changed the source interface for SNMP operations.
• 02926 – The number of syslog messages sent per second from the NetScreen
device were being limited by an internal process.
• 02924 – SMTP (Simple Mail Transfer Protocol) queued emails on Microsoft
Outlook 2003 clients timed out when a policy had the anti-virus option
enabled because you could not perform more than one SMTP transaction
within one session.
• 02909 – Embedded ICMP caused the DIP (Dynamic IP) pool memory leaktraffic flow to stop because the DIP allocation failed after no ports were
present.

ScreenOS 5.0.0r8

P/N 093-1342-000, Rev. C

Page 7 of 32

Juniper Networks

NetScreen Release Notes• 02897 – The WebUI displayed the autokey IKE list incorrectly in instanceswhere a listing of 5, 10, 50, or 100 entries were in the list. It displayed only
20 items per instance.
• 02896 – An SA (Security Association) sometimes was visible in the wrong
Vsys in an environment where two Vsys both had non-active dialup VPNs
configured.
• 02880 – If you enabled the anti-virus option on a policy, and ran thewindowsupdate.microsoft.com utility on the policy, the utility hung and theconsole displayed the Network Error page. The utility worked only when thethe policy had the anti-virus operation disabled.
• 02874 – A core dump occurred when the device prevented packets with thewrong/inactive virtual MAC address from being forwarded.
• 02853 – The WebUI inadvertently allowed adding a subinterface intransparent mode causing the device to reboot.
• 02841 – The device inadvertently displayed an inactive route as active in anenvironment where two route-based VPN unnumbered tunnels mapped to
one VSI. This behavior only occurred when this VSI was assigned to theUntrust zone that had an IBGP routing instance configured inside the
network.
• 02829 – When obtaining a traffic log using a specific IP address on an SSH
session by issuing the get log traffic | include command, the device
rebooted. For example, if you connected to the device using an SSH session
and you issued the following command (which contains an explicit IP
address):
get traffic log | include 10.1.1.10
the device shut down and rebooted.
• 02824 – Custom zones incorrectly supported half the number of IP address
book and group entries than predefined zones did.
• 02823 – When applying the snoop filter with a destination IP address anddestination port, the filter did not work.
• 02822 – The DHCP utility did not work on one of the redundant interfaces
on a device. The interface did not appear in the DHCP environment in the
WebUI.
• 02814 – The SNMP interface index values were inconsistent through the
SNMP tree. Interface index values uniquely identify each interface.
• 02805 – Under certain traffic conditions, some DNS and HTTP session
timers were set with higher values than the DNS and HTTP service
timeouts.

ScreenOS 5.0.0r8

P/N 093-1342-000, Rev. C

Page 8 of 32

Juniper Networks

NetScreen Release Notes• 02796 – When the device sent out a trap that indicated an SNMP
authentication failure when OSPF was enabled, the device rebooted.
• 02788 –In certain situations, an NetScreen-5000 device rebooted when it
received a high number of bad IKE packets.
• 02786 – If the packet that had both a destination broadcast subnet IP
address and a MAC multicast address attempted to enter the device, thedevice dropped it.
• 02785 – A NetScreen device rebooted continuously because an interface on
the device did not check the PPP (Point-to-Point Protocol) encapsulation
functionalities properly.
• 02771 – Traffic through a MIP (Mapped IP) address with both source-based
routing and traffic shaping enabled failed.
• 02765 – If a configuration is pushed to the device by Security Manager andthe heartbeats to the device are lost, the device would invoke theconfiguration rollback feature because the heartbeat missed threshold was
too short.
• 02768 – In some cases, a DIP port leak occurred on the backup device.
• 02740 – The Security Manager Log Viewer did not display data in the Alert
column. The Alert column now correctly displays traffic logs associated with
policies that have the Alert setting selected.
• 02736 – The Mgt-IP on a VSI replied with a virtual MAC address instead ofa physical MAC address for the Ident-reset.
• 02734 – When you performed an SNMP walk operation on the Policy MIB,
the procedure incorrectly displayed an integer to represent the custom
service. It now correctly displays a string to represent a custom service in the
Policy MIB.
• 02730 – For external LSAs (Link State Advertisements) that have aforwarding address, the priority for a forwarding route incorrectly used theinterface cost as the priority value rather than the metric of intra- and interarea OSPF routes. The metric is the correct value to use for setting a routepriority.
• 02718 – Importing a device into Security Manager failed because theheartbeat timeout was exceeded and was not user configurable.
• 02709 – When you set a manual VPN authentication setting to NULL on a
NetScreen device, the device rebooted because a Null length is invalid.
• 02707 – When performing an anti-virus scan on a NetScreen-5GT device, thedevice displayed an error-constraint-drop status.
• 02699 – When multiple interfaces belonged to different Vsys had the same
IP address and subnet mask, VPN traffic to these subnets could pass to thewrong Vsys.

ScreenOS 5.0.0r8

P/N 093-1342-000, Rev. C

Page 9 of 32

Juniper Networks

NetScreen Release Notes• 02609 – The primary NetScreen-5200 device in an Active-Passive NSRP
cluster failed, which caused a failover from the primary to the backup device.
• 02694 – ScreenOS did not send discovered SCREEN occurrences to Security
Manager when Security Manager imported a configuration from a device.
• 02692 – The DIP (Dynamic IP) allocation failed and halted traffic entering
the device, requiring the DIP allocation mechanism to be reset every twohours.
• 02688 – The CLI provided no maximum value check for BGP hold timeentered on a device, incorrectly allowing you to enter any value for the holdtime. If the value was greater than the maximum hold time setting of 65,525,
the device incorrectly accepted the value, and the output from the get holdtime command incorrectly displayed it as a negative number.
• 02687 – Traffic shaping did not work properly when the traffic shaping
policies traversed a route-based VPN on a device.
• 02685 – You could not unset the sql alg using the unset flow sql-alg
command on NetScreen-5000 Series devices.
• 02679 – Some devices generated multiple logs for information associatedwith the self log.
• 02670 – When a NetScreen-5XT device obtained a new IP address from a
DHCP server, one of the static routes did not update the default gateway
with the proper IP address and DHCP payload information assigned to thedevice.
• 02668 – A VPN tunnel incorrectly displayed two different ESP sequencenumbers which are associated with two different ASICs on the NetScreen5000 Series devices.
• 02664 – Packets were sent out with the MAC address of the inactive VSI
instead of the active VSI address in an active-active VSI cluster.
• 02663 – You could not manage two of the secondary IP addresses on aninterface of the NetScreen-100p in the WebUI.
• 02660 – After importing a CA (Certificate Authority) certificate into a device
and then rebooting the device, the device removed the certificate.
• 02655 – The event log timestamp changed to Daylight Savings Time (DST)
even though DST was not enabled.
• 02642 – After configuring SCREEN setting thresholds on a device using the
WebUI or CLI, the get config | include <screen_settings> command did
not display the configured settings.
• 02641 – The PKI IKE memory pool on a device had a memory leak caused by
the Security Manager agent.

ScreenOS 5.0.0r8

P/N 093-1342-000, Rev. C

Page 10 of 32

Juniper Networks

NetScreen Release Notes• 02637 – A session allocation with less than 1,000 sessions on a NetScreen5000 Series device failed.
• 02629 – When running a get config all command and redirecting the output
to a file on the TFTP server when the Trust interface as the source, the file
was not transferred correctly.
• 02627 – The policy move page only displayed the first 20 policies, andtherefore you could not move a policy from the initial screen from where you
copied the beyond the 20 policies displayed.
• 02624 – An anti-virus scan failed to scan .RAR files on a NetScreen-5GT.
• 02621 – When a Ping request is initiated through a VPN tunnel to a MIP
configuration on a loopback interface, the ICMP reply through the tunnel did
not get translated back to the MIP address.
• 02680 – The SNMP name command inappropriately propagated across the
NSRP cluster.
• 02682 – When using the WebUI to set information on the backup device, theprimary SNMP device was inappropriately deleted when using the unset
VSD ID 0.
• 02606 – A ping packet through a tunnel in an NSRP environment between
two NetScreen devices failed after a failover until you performed a rekey
operation.
• 02581 – You incorrectly could define the same IP address to multiple
loopback interfaces over multiple subnetworks by running the set vroutertrust-vr ignore-subnet-conflict command on a device. NetScreen devices
support defining multiple loopback interfaces on the same subnetwork, but
not with duplicate IP addresses.
• 02578 – A PPPoE (Point-to-Point-Protocol-Over-Ethernet) connection on a
device incorrectly sent an acknowledgment for an unnumbered PPP session.
The correct response to an unnumbered PPP session is a NAK (NonAcknowledgment).
• 02552 – Policy authentication with an external authenticating server could
run into the same memory corruption when authentication failed and caused
the firewall to fail.
• 02551 – An NSRP backup device indicated that a failover occurred
continuously when no failure on the primary device occurred.
• 02543 – A device rebooted because of an improperly processed checksum.
• 02542 – When upgrading a NetScreen-5GT from ScreenOS 4.0.0r4 to
ScreenOS 5.0.0r3, a PPP connection from a Windows XP client to a Windows2000 server stopped working.
• 02536 – The priority value on a WebTrends syslog message varied fromdevice to device.

ScreenOS 5.0.0r8

P/N 093-1342-000, Rev. C

Page 11 of 32

Juniper Networks

NetScreen Release Notes• 02531 – After chaning manage options in the Untrust interface with a DHCP
client configured, the device renewed its IP address with the DHCP server,
causing loss of configuration of MIPS, DIPs, and VIPs.
• 02530 – A TCP stack error caused the BGP neighbor state to change to the
Idle state before the BGP holddown time value (default of 180 seconds)
expired. The BGP neighbor state, a setting determined by whether thecurrent BGP routing instance, can detect its neighbor to be active, and is notsupposed to render the neighbor Idle until no neighbor response occurs after
the holddown time elapses.
• 02509 – A memory leak in the NSRP synchronization process between two
devices caused some FTP sessions to stop working.
• 02477 – You cannot configure the NSRP Lite feature through the WebUI
even though you applied an NS-5GT extended key.
• 02457 – The URL request function that sent content to a WebSense server
sometimes engaged the CPU on a device for too long causing the device toreboot.
• 02403 – There was a flaw in the TCP stack buffer which caused the device tofail.
• 02390 – When you created an aggregate interface on a NetScreen-5000
system, a CLI get command and an SNMP get operation indicated different
bandwidth values for the interface. In some cases, the CLI command
revealed 100 Mbps and the SNMP command revealed 0 MBps.
• 02388 – You could not set the DHCP IP address range through the WebUI
when detecting an auto-probe. By attempting to perform this operation, thesystem displayed the following message:
The DHCP IP Pool not in the same subnet with gateway/interface• 02372 – If you ran an OSPF virtual routing instance on a route-based VPN,
under heavy traffic conditions, the device could continually spawn new
sessions for the OSPF packets.
• 02369 – You could not change the IKE Authentication user’s password whenusing the WebUI.
• 02362 – In some instances, a TCP session prematurely expired.
• 02344 – When you tried to bind a PKA key to an administrator account using
the WebUI, the device generated a trace dump.
• 02342 – An OpenSSH client continued to use password authentication evenwhen password authentication was not an option for SSH.
• 02335 – The SNMP iftype value was wrong on the NetScreen-5XP.
• 02333 – When a device attempted to block files with a .exe extension, it
incorrectly blocked files with .zip extensions.

ScreenOS 5.0.0r8

P/N 093-1342-000, Rev. C

Page 12 of 32

Juniper Networks

NetScreen Release Notes• 02326 – A device incorrectly created sessions if the IP address had a unicast
destination while the destination MAC address had a multicast destination.
• 02324 – When configuring a non-default DHCP address range on the HSC(Hardware Security Client) device using the configuration wizard in the
WebUI, the Summary screen indicated that you had overwritten the default
range (beginning with address 192.168.1.33), and would not save.
• 02298 – Commands related to NHTB (Next Hop Tunnel Binding) did not run
when you used a blank character when creating a tunnel name for NHTB.
• 02297 – An anti-virus scan dropped connections with selected HTTP andHTTPS sites.
• 02116 – When the lifetime of an IKE Phase 2 SA (Security Association)
reached a threshold defined by the soft lifetime buffer, a Phase 1 rekey and adelete notification for the P2 SA was generated after the P1 rekey.
• 02026 – When a device attempted to contact a RADIUS server and theserver was unavailable, the device corrupted the server reply after it wasstored in device memory.
• 02024 – When a device contacted a RADIUS server for authentication while
the server was performing many RADIUS authentications, the device
corrupted the server reply after it was stored in device memory.
• 01957 – The WebUI did not contain the ISP connection Test button under
the Configure column in the ISP screen because a previous revision of
ScreenOS was released with the button removed. The button now appears inthis location.
• 01822 – A NetScreen-5000 device incorrectly sent packets from an inactive
VSI (Virtual Security Interface). The device now first considers whether a
VSI is active before it sends packets from it.
• 01862 – After upgrading a NetScreen-5400 to ScreenOS 4.0.1-SBR.2a2, theget ip-classification command displayed incorrect data for IP
classifications currently on the device.
• 01782 – A hidden command incorrectly dropped an incoming packet to a
NetScreen-5000 device when an ARP entry was not present on the device.
The device now responds properly to an incoming packet when no ARP entry
is present, placing the packet in a queue of other packets and forwarding it
after six seconds.
• 01779 – The Track-IP operation in an Active-Active setup on an HA pair of
NetScreen-5000 devices incorrectly selected an outgoing interface in arandom manner.
• 39499 – The CPU utilization on a device increased by 10 percent if the device
could not connect to the Security Manager Device Server.

ScreenOS 5.0.0r8

P/N 093-1342-000, Rev. C

Page 13 of 32

Juniper Networks

NetScreen Release Notes

4.2 Addressed Issues from ScreenOS 5.0.0r7
Manufacturing-only release.

4.3 Addressed Issues from ScreenOS 5.0.0r6• 38268 – A NetScreen device running a BGP peer virtual routing instancecannot 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 apacket 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 thedevice could not send management traffic data.
• 02429 – HTTP packets could not pass through the 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 (5000ms) instead of microseconds with the ms abbreviation (ms is theabbreviation for milliseconds).
• 02416 – If you rebooted a 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 anotherrouting 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 thedefault 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.

ScreenOS 5.0.0r8

P/N 093-1342-000, Rev. C

Page 14 of 32

Juniper Networks

NetScreen Release Notes• 02384 – The device failed if you connected an Ethernet cable to the untrustinterface in the v1-untrust zone while the device was in transparent mode.
• 02383 – Under some circumstances, the OSPF routing instance could notbuild an adjacency because its memory buffer was not large enough tohandle large databases.
• 02379 – You could not establish the Phase II portion of a VPN tunnel when
you referenced a custom service that had spaces in its name with no quote
marks around the string because ScreenOS did not recognize strings withspaces without quotes around the string.
• 02377 – The NetScreen-200 did not always free up memory after VPN
tunnels closed, requiring a manual device reboot to recover.
• 02375 – The device was unable to detect and defend against a ping of death
attack and would fail when these types of packets arrived at the device.
• 02372 – You could not clear sessions on NetScreen-50 devices in an ActivePassive environment in instances when the active device stopped creating
new sessions when the session table was full.
• 02370 – When you manually created a VPN tunnel in an NSRP environment
in the WebUI, using an extra comma in the key portion of the set vpn
command, the primary device failed while the backup device kept the old
configuration.
• 02368 – ScreenOS removed the quotation marks around the VPN name witha space when you configured an NHTB value on an interface.
• 02364 – The device generated an unknown keyword error to the keyword allvirtual-system when you tried to assign a new admin password to a VSYS.
• 02354 – Occasionally, the ScreenOS logging environment incorrectly
displayed unusual logs that indicated a hacker attacked the device. A typicalmessage that indicated a hacker was the following:
2004-02-11 11:45:22 system notif 00001 Address_prefix_c0000000_2_p72_ for ip address 192.0.0.0 in zone V1Untrust has been deleted by netscreen via web from host
128.32.199.217 to 128.32.199.71:80 session• 02336 – In an NSRP Active/Active environment, when the customer
disconnected all the cables from the HA1, HA2, and MGT interfaces oneither device, and they reconnected cables to the HA1 and HA2 interfaces,
the device rebooted.
• 02323 – When you ran FTP Put or Get commands to push or obtain data toor from the device, the WebUI always indicated the device had a Deny actionin its policy even when the policy was configured to permit traffic.

ScreenOS 5.0.0r8

P/N 093-1342-000, Rev. C

Page 15 of 32

Juniper Networks

NetScreen Release Notes• 02272 – HTTP and HTTPS packets passed through VPN tunnels more
slowly than expected, sometimes to the point of timing out and causing thedevice to continually retransmit the packets.
• 02250 – The device sometimes generated an error when you updated a
device and issued the following command with the following arguments:
set interface tunnel.2 nhtb 10.1.2.5 vpn• 02206 – An Apple Macintosh running Operating System 9 client using the
HTTP protocol failed to connect to the internet while a NetScreen-5GT had
AV HTTP scanning enabled.
• 02194 – The get log traffic policy command caused a device to fail when
the device contained more than 15,000 VPN tunnels and received ICMP
traffic.
• 02156 – When you enable Scan-MGR, it prevented access to certain web
pages because during the TCP 3-way handshake, the web server advertised awindow size of 0 to the client, preventing the web page window from opening.
• 02094 – The Address Negate feature had no effect on traffic entering thedevice through a VPN tunnel with a VPN tunnel policy applied to it.
• 02052 – NAT Traversal (NAT-T) for IPSec did not behave correctly whenboth the initiator and responder were behind NAT devices.
• 01793 – A redundant interface incorrectly learned an ARP when no IP
address was configured for the interface.
• 01657 – A redundant VPN did not fail over with a RTO (Run-TimeOperation) synchronization enabled.
• 02041 – The NetScreen-5000-specific command unset/set hardware wdtreset was incorrectly available on all NetScreen devices.
• 02412 – The SNMP Get response values were not correct for the ifInOctets
and ifOutOctets statistics.

4.4 Addressed Issues from ScreenOS 5.0.0r5
None.

4.5 Addressed Issues from ScreenOS 5.0.0r4
This section describes issues that addressed in the ScreenOS 5.0.0r4 release.
• 37070 – The initial configuration wizard in the WebUI required a toggled
checkbox to enable switching the mode of the device back and forth from
NAT Mode to Route Mode.

ScreenOS 5.0.0r8

P/N 093-1342-000, Rev. C

Page 16 of 32

Juniper Networks

NetScreen Release Notes• 37069 – The configuration wizard option in the WebUI that enables you toskip the wizard screens was not present on the initial wizard screen. This
option enables you to go directly to the WebUI login window to enter thedevice to manage it.
• 36669 – When 20,000 or more policies were configured on a NetScreen
device, you experienced a two- to three-minute delay when scrolling throughthe Policy List page in the WebUI.
• 36939 – The NetScreen-25 and NetScreen-50 did not support up to eight
VLANs as expected and the NetScreen-20x did not support up to 32 VLANs
as expected.
• 02259 – In an Active-Active NSRP configuration, the device did not accept
traffic that terminated on the device interface in active mode on a different
zone than the one with the source IP zone.
• 02211 – The IPSec pass-through operation failed because ScreenOS 5.0.0r3
required an incoming policy to work properly.
• 02206 – After the AV waited for HTTP get packets and did not receive themafter a few seconds, the CSP sent resets to nodes on both sides of the device.
• 02175 – By performing a policy search (a scan of a policy group to locate a
specified entry), the device failed because ScreenOS improperly initialized
policy counters which keep track of policies, and the search improperly
returned a null pointer.
• 02160 – When the Anti-Virus scan engine scanned large email messages, thedevice sometimes failed if the amount of time specified by the SMTP scantimeout elapsed before the amount of email data scanned exceeded the Max
Content Size limit.
• 02156 – When the AV Scan-MGR option enabled in a policy detected a SYNACK packet associated with a site with a window size of zero, the device
dropped the packet.
• 02153 – When trying to establish a GRE tunnel between two PCs with one
connected to the Trust interface and the other to the Untrust interface, using
policy-based source NAT, the tunnel failed because a GRE tunnel requires
fixed source and destination ports and the policy-based source NAT processchanges the port values.
• 02148 – The device might fail when Vsys traffic changes to the root sys mod
when the traffic is en route to a Mapped IP (MIP) object.
• 02145 – When SMTP traffic entered the device and combined with the SMTP
rcpt command, it sometimes bypassed the Anti-Virus scanning engine.
• 02142 – The SSH_MSG_IGNORE message and SSH-1.99- version string
were not handled by ScreenOS.

ScreenOS 5.0.0r8

P/N 093-1342-000, Rev. C

Page 17 of 32

Juniper Networks

NetScreen Release Notes• 02134 – When a policy specified a service that contained the same ranges forboth the source port and destination port, traffic associated with otherservices with the same port ranges matched the conditions of the policy andthe policy would respond with actions associated with a match occurring.
• 01981 – You could not set the priority of the modem to any values.
• 01957 – (NetScreen5XT and 5GT only) The modem TEST button was
missing in the WebUI.
• 01907 – Previous releases of ScreenOS 5.0.0 did not support Bootstrap
Protocol (BootP) requests.
• 02139 – If you created a session on the device and no other session is activeon the device, the device still generated a log. NetScreen devices should
generate logs only if you create a session on the device and at least one othersession is active on the device.
• 02117 – For a uni-directional dialup or site-to-site route-based VPN, specificroutes were required on the receiving VPN device so that the returning
traffic could go back into the correct tunnel interfaces accordingly. This wasa result of the dynamic routing failover feature in ScreenOS 5.0.0.
• 02106 – After changing the local Auth server timeout in the WebUI from thedefault value of 10 minutes to any other timeout value, you could not reset
the timeout back to 10 minutes.
• 02104 – In transparent mode, devices dropped VTP (VLAN Trunking
Protocol) and Spanning Tree packets.
• 02095 – The device failed when it performed a custom Deep Inspection
examination on a signature that contained a string of characters that waslong enough to cause the device memory buffers to overflow.
• 02094 – The address negate feature did not work for traffic coming from a
VPN tunnel policy.
• 02078 – If the same Auth/L2TP user was defined on both the device and aremote Radius server, the device did not release the assigned IP addressback to the address pool, as expected, after the user disconnected from thetunnel connection on the device.
• 02076 – (NetScreen-5XP only) The device Status LED light blinked with alonger interval between each illumination (more slowly) than it did whenrunning ScreenOS 4.0.0.
• 02072 – Several SNMP Object ID (OID) data types that identify a specificvendor were incorrect. Some counters associated with OIDs always returneda zero value.
• 02065 – SNMP traps were improperly formatted with numerical values thatindicated an incorrect trap type. SNMP maps specific integers to indicate
specific trap types, or events that generate traps. Because of thisScreenOS 5.0.0r8

P/N 093-1342-000, Rev. C

Page 18 of 32

Juniper Networks

NetScreen Release Notes

discrepancy, you had to read the text description of the trap type to identify
it. Now you can refer to the trap type value to identify it. For example, thetraditional SNMP trap type value for a Cold Start event is 0. Please checkthe ScreenOS Messages Guide for the correct values in ScreenOS 5.0.0.
• 02062 – Under certain circumstances, Track-IP was not sent out and caused
the NSRP failover operation to fail.
• 02059 – When you changed an IKE gateway from Static IP to Dynamic IP
using the WebUI, the procedure automatically changed the setting from
Main Mode to Aggressive mode.
• 02057 – Multiple custom addresses or service groups in a policy sometimes
caused a NetScreen device to fail during restart.
• 02050 – Configuring an address group from an Apple computer using
Internet Explorer sometimes caused a NetScreen device to fail.
• 02047 – When the device received a packet with Ethernet type 0x8888, thedevice failed.
• 02045 – Under certain circumstances, the device incorrectly flagged anddropped IP-Spoof packets.
• 02044 – An operation using SSH version 1 to access the device failed whenusing Radius for administration authentication.
• 02035 – The device did not allow URL filtered traffic when the URL queue
was full and the URL queue size was too small to process heavy traffic.
• 02034 – In transparent mode, when selecting the WebAuth option in the
WebUI for the V1-Untrust Zone, it appeared to take effect, but when closing
the window and then returning to the V1-Untrust configuration window, the
WebAuth option was no longer selected.
• 02019 – You could not use the WebUI to remove the key id and preshared
key of the primary NTP server.
• 02018 – The NetScreen device failed when applying debug commands, forexample, the set ffilter command.
• 02001 – If a dynamically added route and a static route on a device both used
the same interface default gateway as the next hop, when the dynamic
route’s interface default gateway changed, the static route’s gateway did notchange with it as expected.
• 01993 – You could not modify management services on interfaces configuredin the WebUI environment to obtain addresses using DHCP.
• 01986 – In an NSRP environment, the primary device sometimes had more
active XAuth users than the backup device because the garbage collection
mechanism for IPSec SA removed XAuth users from the backup device at amore accelerated rate than it did from the primary device.

ScreenOS 5.0.0r8

P/N 093-1342-000, Rev. C

Page 19 of 32

Juniper Networks

NetScreen Release Notes• 01985 – You could not schedule a policy using the WebUI.
• 01970 – Under certain circumstances, the NetScreen device did not send
email alerts.
• 01943 – When the DHCP payload (information included with the issuance ofan IP address from a DHCP server) exceeded 550 bytes in length, the
NetScreen device was unavailable to send packets associated with the
payload because the DHCP relay mechanism did not accept the packets.

4.6 Addressed Issues from Previous Releases
This section describes issues addressed in ScreenOS 5.0.0 release prior to
ScreenOS 5.0.0r4.
• 37027 – The issue described in security advisory NS#54169 was addressed.
• 36935 – You could not reset the NetScreen device to factory defaults settings
if the NSRD wizard failed to connect the device to the NSM server.
• 36881 – In certain cases, using the pinhole to reset the NetScreen device tofactory default settings failed.
• 36865 – When a serial interface had no IP address, even if it was in the “UP”
state, the routing entry pointing to the serial interface stayed inactive.
• 36838 – A device failure could occur if the interface information derived for a
non-ip packet and received on a 24FE board is invalid.
• 36822 – Entering the get policy CLI command sometimes caused the
NetScreen device to crash.
• 36819 – Under certain circumstances, IP-Spoof packets were incorrectly
flagged and dropped.
• 36814 – With dialup user group VPN manually configured proxy-id, it could
not be used for bi-directional dial-up vpn policy.
• 36773 – In Transparent mode, the IP Address Spoof Protection screen option
caused the NetScreen device to incorrectly drop packets even if the“Generate Alarms without Dropping Packet” option was enabled.
• 36766 – (NetScreen-5GT only) In transparent mode, during the initialconnection attempt where the device had no established route to thedestination, initial traffic was dropped on occasion by the device when AV
scanning was active.
• 36736 – A device configured with DHCP and via a configlet was unable toconnect to NSM.
• 36717 – When upgrading to ScreenOS 5.0.0, the maximum number ofaddress groups allowed for Layer2 predefined zones incorrectly got set to thesame number as for custom zones. As a result, if the number of address

ScreenOS 5.0.0r8

P/N 093-1342-000, Rev. C

Page 20 of 32

Juniper Networks

NetScreen Release Notes

groups in Layer2 predefined zones surpasses the maximum number allowed,
some address groups got removed during the upgrade.
• 32690 – (NetScreen-5GT only) When multiple devices were connected with
AV scanning enabled on policies, no traffic passed through the devices. For
example, if two devices were connected together and both had AV scanningenabled on policies, no traffic traversed the devices.
• 02081 – The active user table failed to clear automatically. New users weredenied until the table was manually cleared.
• 02079 – In an instance where the system was running in transparent mode,
when you enabled traffic shaping mode, the system dropped all packets.
• 02038 – Core dumps occurred occasionally when traffic matched policies
which had authentication enabled.
• 02027 – An SNMP sysObject OID reply returned in the wrong format.
• 02006 – Enabling DHCP Relay could cause a NetScreen device to crash.
• 01972 – A DHCP relay packet sometimes caused a NetScreen device tocrash.
• 01971 – You were not able to add physical interfaces (different ports) of a
NetScreen device in the same redundant interface group.
• 01968 – (NetScreen-5GT and NetScreen-HSC only) Ident-reset packets thatterminated on the device might have caused the device to restart.
• 01958 – An internal mishandling of the MAC cache could cause a NetScreen
device to crash.
• 01944 – The group addresses for V1-untrust zone were getting lost after
upgrading a device from a previous release. The group address for v1-untrust
was incorrectly set to a maximum of 8 groups while it should have been 32.
• 01812 – Using un-initialized memory space when creating an outgoingpacket caused the device to fail.

5. Known Issues
This section describes known issues with the current release.
• Section 5.1 “Limitations of Features in ScreenOS 5.0.0” identifies featuresthat are not fully functional at the present time, and will be unsupported forthis release. NetScreen recommends that you do not use these features.
• Section 5.2 “Compatibility Issues in ScreenOS 5.0.0 on page 23” describes
known compatibility issues with other products, including but not limited to
specific NetScreen appliances, other versions of ScreenOS, Internet
browsers, NetScreen management software and other vendor devices.

ScreenOS 5.0.0r8

P/N 093-1342-000, Rev. C

Page 21 of 32

Juniper Networks

NetScreen Release Notes

Whenever possible, information is provided for ways to avoid the issue,
minimize its impact, or in some manner work around it.
• Section 5.3 “Known Issues in ScreenOS 5.0.0 on page 24” describes
deviations from intended product behavior as identified by NetScreen Test
Technologies through their verification procedures. Again, wheneverpossible, information is provided to assist the customer in avoiding orotherwise working around the issue.

5.1 Limitations of Features in ScreenOS 5.0.0
The following limitations are present in ScreenOS 5.0.0.
• Vsys for Group IKE ID – Group IKE ID users cannot be used in a vsys ifthat vsys uses a shared untrust interface.
W/A: Use a private Untrust interface (tagged VLAN subinterface ordedicated physical interface) for the vsys.
• SSH Version 1 Interoperability – The embedded SSH server in ScreenOS
5.0.0 has issues with the client from SSH Communications Security when
operating in SSH version 1 mode.
W/A: Use SSH version 2 or a different SSH version 1 client, such as
OpenSSH.
• Primary & Backup Interfaces – (NetScreen-5XT) The primary andbackup interfaces bound to the Untrust security zone cannot both use DHCP
for address assignment at the same time. You can use DHCP for one
interface and PPPoE for the other. Or you can use PPPoE for both interfaces.
• Loading License Keys – The NetScreen-5XP device does not properly load
license keys via the WebUI. However, you can load license keys via the CLI
using the exec license-key command.
• Aggressive Aging – The Aggressive Aging feature is not supported on the
NetScreen-5000 Series devices.
• SSHv2 Implementations – The SSHv2 feature specification requires
support for two implementations: OpenSSH and Secure CRT.
• Upgrade Limitations – When upgrading a device to ScreenOS 5.0.0UPGR
in Transparent mode, the device experiences the following problems:– The device fails during upgrading from ScreenOS 4.0.1 to ScreenOS 5.0.0
in a VPN scenario.
– In clear text situations (where traffic is not encrypted to pass through a
VPN tunnel), after the upgrade to ScreenOS 5.0.0UPGR, the user had to
run the clear arp and clear mac-l commands to enable the device towork because some ARP entries learn on the wrong port.

ScreenOS 5.0.0r8

P/N 093-1342-000, Rev. C

Page 22 of 32

Juniper Networks

NetScreen Release Notes• Updated Message ID Numbers – The NetScreen Message Log Reference
Guide (Part Number 093-0917-000 Rev. D) now contains an updated
message ID number for Deep Inspection attack messages. The message,
formerly associated with ID number 00001, now maps to ID number 00601.
Although the ID number has already been changed in the guide, the ID
number will not change in the code until the next revision of ScreenOS 5.0.0.

5.2 Compatibility Issues in ScreenOS 5.0.0
Below are the known compatibility issues at the time of this release. Wheneverpossible, a workaround (starting with “W/A:”) has been provided for yourconvenience.
• General Compatibility Issues– Freeswan - The Freeswan 1.3 VPN client is incompatible with ScreenOS
5.0.0 in certain configurations due to IKE features that Freeswan does not
fully support. The result is that Phase 2 negotiations and Phase 2 SA will
not complete if the following commands are enabled in 5.0.0:
set ike initiator-set-commit
set ike responder-set-commit
set ike initial-contact
W/A: Unset these commands to ensure compatible configuration on the
NetScreen device.
• Compatible Web Browsers - The WebUI for ScreenOS 5.0.0 was tested
with and supports Microsoft Internet Explorer (IE) browser versions 5.5 andabove, and Netscape Navigator 6.X for Microsoft Windows platforms, andMicrosoft Internet Explorer version 5.1 for MacOS 10.x. Other versions ofthese and other browsers, were reported to display erroneous behavior.
• SNMP Trap Type Values Different in ScreenOS 5.0.0 – ScreenOS 5.0.0
uses a different numbering system than previous ScreenOS releases to
identify trap types. SNMP maps specific integers to indicate specific trap
types, or events that generate traps. For example, the traditional SNMP trap
type value for a Cold Start is 0. However, different vendors deploy different
values to indicate different trap types. Please check the ScreenOS Messages
Guide for the correct values in ScreenOS 5.0.0.

ScreenOS 5.0.0r8

P/N 093-1342-000, Rev. C

Page 23 of 32

Juniper Networks

NetScreen Release Notes

5.2.1 Upgrade Paths from Previous Releases
For detailed information on how to upgrade any NetScreen device from
ScreenOS 4.0.0 and later to ScreenOS 5.0.0, refer to the NetScreen ScreenOS
Migration Guide. The migration guide provides step-by-step upgrade
procedures and important information about upgrading NetScreen devices.
Important: To avoid downtime while upgrading devices in an NSRP
configuration (active/passive or active/active), refer to the NetScreen
ScreenOS Migration Guide which describes procedures to upgrade the devices
without causing any downtime.
The migration guide also provides a step-by-step procedure to downgrade a
NetScreen device from ScreenOS 5.0.0 to ScreenOS 4.0.0 and later using theexec downgrade CLI command.
NetScreen-5000 series only: Before you upgrade a NetScreen device to
ScreenOS 5.0.0, we recommend that you verify the amount of memory on thedevice using the get system CLI command. You need 1 gigabyte of memory
for NetScreen-5000. If you start upgrading the device and run into memory
problems, you might see the following messages: “insufficient memory, call
TAC” or “see release notes for upgrade instructions”.
To avoid network downtime while upgrading devices in an NSRP
configuration, refer to the Upgrading Devices in an NSRP Configuration
without Downtime document. You can download this document from thelocation on the CSO where the revision image resides.
NSM does not support the NSRP Configuration without Downtime feature.

5.3 Known Issues in ScreenOS 5.0.0
The following are known deficiencies in features at the time of this release. Wheneverpossible, a work-around is suggested following the description of the problem.
Workaround information starts with “W/A:” If there is no subsection for a particular
ScreenOS release, no new known issues were identified for that release.

5.3.1 Known Issues in ScreenOS 5.0.0r8• 03153 – When you attempt to download plugin and main program files in
one file, the system generates errors.
• 03152 – When running XAuth in the WebUI environment, the XAuth page
displays the CHAP fragment reassembly method selected by default.

ScreenOS 5.0.0r8

P/N 093-1342-000, Rev. C

Page 24 of 32

Juniper Networks

NetScreen Release Notes• 03132 – When using NetScreen-Remote to connect to a NetScreen-500 dialup VPN using the WebUI, the IKE Gateway Configuration displays as user
instead of user-group.
• 03128 – Mistakes occur with (MIP) Mapped IP translation when a remoteshell uses a secondary session initiated from the server for redirecting
standard error output from the console.
• 03095 – The NetScreen-5XT has a link negotiation problem when it connects
to the Cisco 3550. The link ensures only guaranteed operation of settings
when both devices have the same settings. For example, if the NetScreen5XT has Autonegotiation or manual speed and duplex settings selected, thenthe Cisco 3550 must have the same ones selected for the device to run as
expected.
• 03092 – When the device is in transparent mode, it cannot obtain the latest
virus signature updates.
• 03081 – An anti-virus parsing error slows performance for HTTP sessions.
• 03071 – If you have a group of VIPs (Virtual IP addresses) and you do not
define a service for the first VIP in the group and you add a service to any of
the other three, the VIP summary page in the WebUI displays no data.
• 03068 – When you modify the IKE Phase 1 gateway name through the
WebUI on the primary device in an environment where two NetScreen-500
devices run NSRP on ScreenOS 5.0.0r6, the primary device cannot
synchronize with the backup device.
• 03065 – When you download the asset recovery log from the WebUI, it
appears with the incorrect date and time with the date being seven years
different than the correct date.
• 03058 – A Delta Configuration session in Security Manager reveals that a
number of commands associated with interface configuration still remain
unsynchronized between the device and Security Manager. The
inconsistency occurred because Security Manager does not have a template
for the zones the interfaces map to: Null and HA.
• 03054 – After upgrading from ScreenOS 4.0.1r3 to ScreenOS 5.0.0r6, thedevice does not update its ARP (Address Resolution Protocol) table when thedevice sends traffic to or through a PC in the same subnet. Additionally, if
traffic flows between different zones, the device may have performance
problems when sending an ARP request for the destination of the traffic.
• 03042 – When you install the Unlimited Number of Users key and change
the revision of software on the device from ScreenOS 5.0.0rX to ScreenOS
4.0.0-DIAL2rX, the serial interface disappears.
• 03025 – In certain situations, when a user authenticates using WebAUTH
with SecureID, and the user in the Auth table times out, subsequentattempts to authenticate fail.

ScreenOS 5.0.0r8

P/N 093-1342-000, Rev. C

Page 25 of 32

Juniper Networks

NetScreen Release Notes• 03010 – In certain situations when you ping a NetScreen-5200-24FE
interface, an error condition occurred which sent out fragmented packets.
• 02988 – The (ALG) Application Layer Gateway on a NetScreen-5200 for acustom-defined RSH service does not work.
• 02972 – You cannot connect to a NetScreen-25 running SCP with OpenSSH
3.5p1.
• 02986 – You cannot run SSH version with RADIUS authentication on a
NetScreen-5GT.
• 02941 – If you enabled DIP (Dynamic IP address) and traffic shaping on a
device, the traffic fails during the first attempt to access an external sitethrough the device.
• 02927 – Devices upload HTTP traffic very slowly after you enable both theanti-virus and URL filtering options in a policy on the device.
• 02921 – A NetScreen-5400 stops accepting all traffic after you reset thedevice and then unset a policy with multiple services.
• 02869 – A NetScreen-5GT cannot deliver mail and the POP3 (Post Office
Protocol 3) session times out when the device runs an anti-virus scan on an
SMTP or POP3 policy.
• 02297 – An anti-virus scan drops connections with selected HTTP andHTTPS sites.
• 02266 – When you make one configuration change on a device, the device
sometimes sends out more than one entry associated with that change toboth the syslog and WebTrends servers.
• 01237 – In an NSRP configuration of two NetScreen-200 devices, you cannot
save a device configuration from flash memory on the device to slot 1.
W/A: Execute the save command first, before executing the save config
from flash to slot1 command.

5.3.2 Known Issues from ScreenOS 5.0.0r7
None.

5.3.3 Known Issues from ScreenOS 5.0.0r6
None.

5.3.4 Known Issues from ScreenOS 5.0.0r5
None.

ScreenOS 5.0.0r8

P/N 093-1342-000, Rev. C

Page 26 of 32

Juniper Networks

NetScreen Release Notes

5.3.5 Known Issues from ScreenOS 5.0.0r4• 38109 – When running 5,000 UDP sessions between two non-ScreenOS 5.0.0
devices and you upgrade one device to ScreenOS 5.0.0UPGR and the other to
ScreenOS 5.0.0r4 via ScreenOS 5.0.0UPGR, only 3,000 of the UDP sessions
synchronize properly.
• 37938 – The NetScreen-5000 or NetScreen-500 device sometimes fails after
upgrading from an older version of ScreenOS to ScreenOS 5.0.0UPGR.
• 37925 – The L2TP tunnel and Telnet utility both do not work on the
NetScreen-5000 or NetScreen-500 device after you upgrade the device from
ScreenOS 4.0.1r4.2 to ScreenOS 5.0.0UPGR.
• 37901 – After you upgrade a NetScreen-5000 or NetScreen-500 device from arunning ScreenOS 5.0.0UPGR B (backup) to ScreenOS 5.0.0UPGR M(primary), the current session on the device disappears.
• 02369 –You could not change the IKE/AUTH user password using the
WebUI. The WebUI apparently takes the change but it does NOT change it
when the configuration is viewed.
• 02297 – The Anti-Virus scanning engine drops connection with some HTTP/HTTPS sites.
• 02207 – The NS Lookup operation completes without first authenticating toa WebAuth policy. The NS Lookup utility resolves unknown hostnames andURLs.

5.3.6 Known Issues in ScreenOS 5.0.0r3 for the 5000-M2• 38001 – When you run the get session command, ScreenOS sometimes
displays the policy ID number incorrectly as a negative number.
• 37993 – When enabled on a NetScreen-5000 Series system, the inter-zone IP
record route option does not update the counter associated with this option.
The record route option records the IP addresses of the network devices
along the path that an IP packet travels. The destination device then can
extract and process the route information.
• 37974 – When attack packets associated with the syn-and-fin, blockfragment, and unknown-protocol events attempt to enter a NetScreen-5000
Series system using a 5000-24FE secure port module when the system
experiences heavy traffic, the system ASIC may not be able to transmit
packets from the device. A syn-and-fin attack is an instance where a TCP
header contains both syn and fin flags set. A block-fragment event is when
the NetScreen system attempts to deny entry of fragments of a larger packet
that have been disassembled so they may enter the device with undetectedattack content. An unknown-protocol attack is a packet that contains a
protocol that the NetScreen system does not recognize.

ScreenOS 5.0.0r8

P/N 093-1342-000, Rev. C

Page 27 of 32

Juniper Networks

NetScreen Release Notes• 37712 – You cannot remove an SSH key from a Vsys by running thecommand unset ssh pka all. When you run the command, ScreenOS does
not remove the SSH key and displays a generic error message.
• 37640 – You can create a password name with a greater number ofcharacters than the usual character limit (15) for passwords in ScreenOS for
the NetScreen-5000 Series systems.
• 37497 – You could not create more than 1,500 IKE sessions (attempting toestablish VPN tunnels) while the system experienced heavy traffic.
• 37422 – When you loaded an older ScreenOS configuration image on a new
NetScreen-5000 Series system, the system failed. If the system now
functions correctly, remaining active with ScreenOS displaying an error
message on the console indicating a mismatch between the loaded image andthe image(s) the system accepts.
• 37303 – You can create an environment variable with a greater number ofcharacters than the usual character limit (255) for environment variable
strings in ScreenOS for the NetScreen-5000 Series systems.
• 36926 – After you created the maximum number of sessions (1 million)
allowed on the NetScreen-5000 Series system, and you disable a policy, thesessions do not age out in the expected way from the system.
• 36807, 36876 – When a 100Mbps link between a NetScreen-5000 Seriessystem and another device reverts to a 10Mbps throughput level on the otherdevice, the NetScreen-5000 Series system remains at the 100Mbps
throughput level when it should synchronize with the speed of the connected
device and revert to the lesser speed.

5.3.7 Known Issues from ScreenOS 5.0.0r3
None.

5.3.8 Known Issues from ScreenOS 5.0.0r2• 35620 - (NetScreen-5GT only) If a policy is using a local address, any
modification to the netmask of the address produces a trace dump on the
console. This modification should not be a permitted action for the device.
• 36365 - In the WebUI, on the Traffic Log page for policies (under Reports),
the table displaying the information might disappear after viewing multiple
pages of traffic logs.
W/A: Refresh the Traffic Log page for policies by clicking the Refresh button
on your Internet Browser.

ScreenOS 5.0.0r8

P/N 093-1342-000, Rev. C

Page 28 of 32

Juniper Networks

NetScreen Release Notes

5.3.9 Known Issues from ScreenOS 5.0.0r1• Documentation Correction - Page 3 of the What's New in NetScreen
ScreenOS 5.0 states incorrectly that NetScreen devices support routing
based on the source interface. The current implementation does support
routing based on source IP address.
• 36018 - (NetScreen-5GT only) The two month entitlement expiration noticein the event log is triggering during the incorrect timeframe. For example, if
the AV entitlement expires in 52 day, the event log indicates "License key
av_key is about to expire in 2 months".
• 35582 - In an NSRP configuration, active/active or active/passive, if you
move a physical interface to a different zone on one device, you must
manually do the same on the other device because this type of change does
not get automatically synchronized.
• 35516 - In an active/passive NSRP configuration, when you load a PKA key
onto the master device, the master does not automatically synchronize thebackup device.
W/A: Manually synchronize the two devices.
• 35439 - (NetScreen-5GT only) Within the WebUI, identical routes are
displayed on multiple pages. When the number of routing table entries
exceeds the maximum number of routes permitted on a single page, allsubsequent pages display the routes from the first page.
• 35417 - If you set the guaranteed or maximum bandwidth (GBW or MBW)
higher than the interface bandwidth, traffic does not pass through if there isa policy configured that specifies traffic shaping.
W/A: Adjust the GBW or MBW to be equal or less than the interface
bandwidth.
• 35336 - If you enabled VPN tunneling for syslog traffic and the source
interface is bound to a zone that contains multiple interfaces, after
upgrading a device from ScreenOS 4.0.0 to ScreenOS 5.0.0, the source
interface might have changed.
W/A: After upgrading the NetScreen device, verify the VPN settings forsyslog and modify if necessary.
• 35238 - For devices in an NSRP configuration, active/active or active/
passive, you have to manually issue the delete ssh device all CLI
command on both devices.
• 34950 - (NetScreen-5000 only) Failover between two layer 2 interfaces in thesame layer 2 security zone is not supported.

ScreenOS 5.0.0r8

P/N 093-1342-000, Rev. C

Page 29 of 32

Juniper Networks

NetScreen Release Notes• 34922 - (NetScreen-50 only) You cannot configure a VSI when the NetScreen
device is in an active/passive NSRP configuration.
• 34880 - (NetScreen-5GT only) Issuing the CLI command 'set interface<interface> manage ident-reset' displays incorrectly as 'set interface<interface> ident-reset' (without the word "manage" in the configurationfile).
• 34670 - (NetScreen-5GT only) Issuing the CLI command 'set/unset firewall
exclude log-self exclude ike' does not change the state of "Log Self for IKE".
The 'get firewall' command displays "Log Self for IKE" constantly in the "Off"state.
• 34663 - Enabling the RTO mirror group direction feature using the set nsrp
rto-mirror id <id> direction { in | out } CLI command, might cause thepreempt mode feature not to work.
• 34414 - The NetScreen device does not perform a revocation check on thesignature attack database upon requesting an update.
• 34070 - (NetScreen-5GT only) The event message 'AV: Suspicious client<Source IP> <Source Port> -> <Destination IP> <Destination Port> used
<X> percent of AV resources, and exceeded the max. of <y> percent' displays
only when you issue a ‘get event' CLI command, and not when you issue a'get log event' CLI command.
• 33916 - A NetScreen device supports a maximum of 256 OSPF interfaces.
• 33598 - For inter-vsys traffic, if both vsys define a policy with user
authentication, the NetScreen device does not prompt the user forauthentication for each policy, but only once when it matches the first policy.
• 33544 - Normally upon startup, a NetScreen device with the URL filteringfeature enabled, tries to connect to a Websense server. Currently thisattempt to connect to a Websense server fails and the NetScreen device logs
the event.
• 33027 - NetScreen devices do not support policy-based dialup VPN and MIP
if the MIP is configured on the tunnel interface which belongs to a tunnel
zone.
W/A: For dialup user VPNs only: use routing-based VPN and configure the
MIP on a tunnel interface bound to a security zone.
• 32983 - You can select multiple services in a policy, but later on, if you wantto modify the services to ANY, the NetScreen device does not let you.
Instead, you get a message prompting you to use the multiple service
selection dialog box, which does not contain ANY, to modify the services.

ScreenOS 5.0.0r8

P/N 093-1342-000, Rev. C

Page 30 of 32

Juniper Networks

NetScreen Release Notes

W/A: In the multiple service selection dialog box, remove all but one service
from the previous selection, and then click OK. Next, select “ANY” from theService drop-down list.
• 32159 - NetScreen devices do not support a second level of certificate
verification if the end entity certificate and OCSP responder certificate areissued by the same CA.
• 32077 - (NetScreen-5GT only) When you enable or disable HTTP Webmail
functionality, log entries are not generated in the event log (i.e. 'set/unset av
http webmail enable'; 'set/unset av http webmail url-pattern-name <namefor the URL pattern>').
• 32072 - (NetScreen-5GT only) When you disable AV functionality for HTTP,
SMTP, and POP3, log entries are not generated in the event log (i.e. 'unset
av scan-mgr content http'; 'unset av scan-mgr content smtp'; 'unset av scanmgr content pop3').
• 31364 - When performing source port translation for passive FTP datachannel, the NetScreen device translates the source port number to the same
port number as the original destination port. This does not affect traffic.
• 30844 - When AV is enabled, you cannot download files to the NetScreen
device through a VPN using the WebUI.
W/A: Specify a permit policy and place it above the policy with AV in thepolicy list.
• 30842 - Source and destination NAT are not supported for RTP and RTCP
traffic for H.323.
• 28878 - Removing a vsys does not free the memory (30 bytes) used by thatvsys.
• 28138 - The Websense server provides erroneous protocol version
information, which the NetScreen device displays.
• 28016 - NetScreen devices do not support a MIP in the same zone as thedestination host.
W/A: Use policy-based destination NAT.

5.3.10 Known Issues from Previous Releases• 27083 - When you enter the set service command to create a custom
service, the NetScreen device does not check if you entered valid source anddestination port numbers.
• 25841 - When you configure RIP on the NetScreen device and enter the get
config command, the output displays the set protocol rip command twice.
This is a display issue that does not affect the performance of the device.

ScreenOS 5.0.0r8

P/N 093-1342-000, Rev. C

Page 31 of 32

Juniper Networks

NetScreen Release Notes

6. Getting Help
For further assistance with Juniper Networks products, visit
www.juniper.net/support
Juniper Networks occasionally provides maintenance releases (updates andupgrades) for ScreenOS firmware. To have access to these releases, you mustregister your NetScreen device with Juniper Networks at the above address.
Copyright © 2004 Juniper Networks, Inc. All rights reserved.
Juniper Networks, the Juniper Networks logo, NetScreen, NetScreen
Technologies, GigaScreen, and the NetScreen logo are registered trademarks ofJuniper Networks, Inc. NetScreen-5GT, NetScreen-5XP, NetScreen-5XT,NetScreen-25, NetScreen-50, NetScreen-100, NetScreen-204, NetScreen-208,
NetScreen-500, NetScreen-5200, NetScreen-5400, NetScreen-Global PRO,NetScreen-Global PRO Express, NetScreen-Remote Security Client, NetScreenRemote VPN Client, NetScreen-IDP 10, NetScreen-IDP 100, NetScreen-IDP 500,
GigaScreen ASIC, GigaScreen-II ASIC, and NetScreen ScreenOS are trademarksof Juniper Networks, Inc. All other trademarks and registered trademarks are theproperty of their respective companies.
Information in this document is subject to change without notice.
No part of this document may be reproduced or transmitted in any form or by anymeans, electronic or mechanical, for any purpose, without receiving written
permission from:
Juniper Networks, Inc.
1194 N. Mathilda Ave.
Sunnyvale, CA 94089-1206
U.S.A.
ATTN: General Counsel
www.juniper.net

ScreenOS 5.0.0r8

P/N 093-1342-000, Rev. C

Page 32 of 32