HP JETDIRECT PRINT SERVERS - FIRMWARE HISTORY FIRMWARE HISTORY FOR HP JETDIRECT PRINT SERVERS If you have And you You can Which will Download this this have upgrade to give you these file from the product: this this features: BBS: firmware firmware revision revision: : HP J2550A A.04.06 A.04.08 Fixes Windows based HP J2552A or below described -amswine.exe (Ethernet) below. HP-UX 9.x - ahpux9e.tar HP-UX 10.x - ahpux10e.tar HP J2555A A.04.06 A.04.08 Fixes Windows based (Token or below described - amswint.exe Ring) below. HP-UX 9.x - ahpux9t.tar HP-UX 10.x - ahpux10t.tar HP J2337A C.03.00 C.03.16 Native queue Windows based HP J2338A to server mode, -cmswine.exe HP J2339A C.03.08 NetWare NDS HP J2340A support, and HP-UX 9.x - HP J2371A minor telnet chpux9e.tar HP J2372A configuration (Ethernet) enhancements. HP-UX 10.x - *Requires chpux10e.tar Flash SIMM HP J2546A/B HP J2373A C.03.00 C.03.16 Native queue Windows based (Token to server mode, - cmswint.exe Ring) C.03.09 NetWare NDS *Requires support, and HP-UX 9.x - Flash SIMM minor telnet chpux9t.tar HP configuration J2549A/B enhancements. HP-UX 10.x - chpux10t.tar If you have And you You can Which will Download this this have upgrade to give you these file from the product: this this features: BBS: firmware firmware revision revision: : HP J2382A B.03.00 B.03.16 Native queue Windows based HP J2382B to server mode, -bmswine.exe (Ethernet) B.03.10 NetWare NDS *Requires support, and HP-UX 9.x - Flash SIMM minor telnet bhpux9e.tar HP configuration J2547A/B enhancements. HP-UX 10.x - bhpux10e.tar HP J2383A B.03.00 B.03.16 Native queue Windows based HP J2383B to server mode, - bmswint.exe (Token B.03.10 NetWare NDS Ring) support, and HP-UX 9.x - *Requires minor telnet bhpux9t.tar Flash SIMM configuration HP enhancements. HP-UX 10.x - J2548A/B bhpux10t.tar HP J2593A D.04.03 D.04.04 Windows 95 bug Windows based (Ethernet) or below fix described -dmswine.exe below. HP-UX 9.x - dhpux9e.tar HP-UX 10.x - dhpux10e.tar A.04.08 - THE FOLLOWING ENHANCEMENTS HAVE BEEN MADE IN THIS REVISION OF FIRMWARE: FIXED: Default Gateway Configuration Error - 80 SERVICE ERROR 0009 or 01E0 How does the problem exhibit itself: 1) Attempts to telnet fail - "Unable to connect to remote host (refused)" 2) Attempts to print fail 3) Any attempt to reconfigure the HP JetDirect print server (via the printer front panel or telnet) will cause an 80 SERVICE ERROR 0009 or 80 SERVICE ERROR 01E0. This problem occurs when the sender (host) is on a different network than the receiver print server) and there are two paths between them. For instance, a request comes in on one path (via router A). The print server is configured to respond through the other path (via router B). If router B is down, the problem will occur. This problem can also happen if the default gateway is configured to either a node that doesn't exist or a node that is not on the same subnet as the print server. This will NOT happen when the sender (host) is on the same subnet as the receiver (print server). WORKAROUND: Download A.04.08 firmware to J255xA JetDirect print servers. FIXED: JetDirect J255xA print server/LaserJet 5Si/5Si MX printer - 80 SERVICE ERROR 01E6 The 80 SERVICE ERROR 01E6 can occur on a HP LaserJet 5Si/5Si MX printer with a JetDirect MIO print server with A.04.06 or earlier firmware installed. The failure is random and could occur at any time during printing (it could during the first print job or after 24 hours of continuous printing). It is due to a hardware timing issue between the printer and the JetDirect print server. The A.04.08 firmware addresses the hardware timing issue and thus solves the problem. WORKAROUND: 1) Power cycle the printer. (This will clear the 80 SERVICE ERROR.) 2) Download the A.04.08 firmware to the JetDirect print servers. A.04.06 - THE FOLLOWING ENHANCEMENTS HAVE BEEN MADE IN THIS REVISION OF FIRMWARE: APPLE FIXED: LocalTalk and EtherTalk Phase 1 Routing This firmware fixes a problem in previous revisions wherein the JetDirect card did not correctly respond to routed packets in certain LocalTalk and EtherTalk Phase 1 environments. In these environments, if the packet destination address network number was in the range of 65280 through 65535 the packet would incorrectly be sent directly instead of via the AppleTalk router. FIXED: JetDirect Default Zone At startup, JetDirect products try to find a local AppleTalk router by sending out a Routing Table Maintenance Protocol (RTMP) Request packet. Upon receiving any response it is presumed that there is a live AppleTalk router on the local network segment, and further, that it will provide the proper Zone name via ZIP (Zone Information Protocol) request/responses. If the AppleTalk router did not provide the ZIP response or the ZIP response was incorrectly formatted, the JetDirect firmware would never finish starting up in AppleTalk. This would leave the AppleTalk protocol on the card in an unknown state. With this firmware revision the JetDirect card uses the generic AppleTalk default Zone name of "*" if the AppleTalk router fails to provide the real Zone name. NOVELL NEW FEATURE:Nearest Service Query (NSQ) Enhancement 1) The JetDirect card uses the General Service Query to find its configured file servers on the network. The first two General Service Queries (GSQs) sent out by the card have been changed to Nearest Service Queries (NSQ). The difference between a GSQ and an NSQ is that GSQs are responded to with all the file server names that exist in the network. The NSQ request will obtain responses from local file servers only. If there are no file servers local to the subnet, a router (or a server acting as a router) will respond to the NSQ with the server name that has the least number of intermediate networks (i.e., lowest hop count). This change should alleviate traffic congestion caused by GSQ responses as well as the WellFleet router problems seen with GSQs. 2) The frequency of sending General Service Queries (GSQ) has been decreased. The card sends out 1 General Service Query (GSQ) or Nearest Service Query (NSQ) every 15 seconds for 4 attempts and then backs off to a 3 minute retry. The JetDirect card now uses GSQs only as a fallback mechanism. In other words, if the JetDirect card can find all the servers using NSQs, it will never send out any GSQs. The algorithm will work as follows: * Send 2 NSQs with a 15 second interval * Send 2 GSQs with a 15 second interval * Send subsequent GSQs at 3 minute intervals until all file servers are found. 3) The JetDirect card used to send a GSQ for a tree in NDS environment. The card now behaves similar to the way it works in a bindery (3.x servers) environment. The algorithm for a NDS environment will work as follows: * Send 2 NSQs with a 15 second interval * Send 2 GSQs with a 15 second interval (JetDirect card will still attach to the first server response of GSQ in NDS mode) * Send subsequent GSQs at 3 minute intervals until any file server on the tree is found. 4) When a JetDirect card is configured for multiple bindery servers, and one of those servers is down, the JetDirect card sends out an NSQ followed closely (40- 100ms) by a GSQ. This behavior would happen only once and subsequently the JetDirect card will send out a GSQ every 3 minutes.. NEW FEATURE:Large Internet Packet (LIP) Implementation The JetDirect cards now support LIP (Large Internet Packet). The JetDirect card can now negotiate the packet size with a server (assuming the server and other network devices are correctly set up to handle LIP). The JetDirect card sends out a LIP echo packet with the maximum packet size (1518 for Ethernet and 2084 for Token Ring). It then waits for a response. After waiting for a certain amount of time without getting a response, the card will send out another LIP echo packet with a smaller packet. When the JetDirect card does get a response to an echo packet, it will subsequently use that packet size for all subsequent transmissions. FIXED: NDS Partition (Read/Write Replica) Fix A.04.06 firmware fixes the following problem: If an NDS server does not have a read replica of a partition which holds the server object itself, the JetDirect card "bounces" back and forth between the server and the replica server, and is, therefore, not be able to service any NDS queues. With the fix in place, the JetDirect card can handle this situation and is able to service the NDS queues. TCP/IP NEW FEATURE:The IP set-community-name can now be configured using TELNET The Set-Community-Name parameter is a type of security mechanism used primarily in the network management world. In order for a remote network management tool to SET a value in the JetDirect MIB, it must know the Set- Community-Name for the JetDirect print server. To view the Set-Community-Name using telnet simply obtain the IP address of the JetDirect print server from the self test page. From a workstation type: telnet To change the Set-Community-Name from within telnet, use the "set-cmnty-name" command. At the telnet prompt type: set-cmnty-name: The Set-Community-Name can have from 1 to 32 characters. Any alpha-numeric character is valid. In addition, the minus "-" and underscore "_" characters are legal also. These are commonly used to make the name more meaningful. FIXED: Queue names used by the TCP/IP printing protocols are no longer case sensitive. Previously only lower case values could be used (for instance "raw"). Now all combinations are acceptable: lower case, upper case and even mixed case. For example "raw", "RAW", and "Raw" will all work. FIXED: LPD Banner Page Fix In previous versions of firmware, if a host system sent multiple LPD jobs on one TCP/IP connection and the banner page was enabled, then everything would work fine. However, if the banner page was disabled, then only the first job would be printed. Now, if a host system sends multiple LPD jobs on one TCP/IP connection, all jobs will be printed, whether or not the banner page is enabled. D.04.04 - EX PLUS3/WINDOWS 95 ISSUE The following EX Plus3/Windows 95 issue was fixed with D.04.04 revision of the firmware: ISSUE: When using an EX Plus3 on Windows 95 running Direct Mode IPX, the EX Plus 3 will not show up in the JetAdmin "New Printer" screen. This only affects the Ethernet EX Plus3. WORKAROUND: Upgrade the EX Plus3 to the new firmware revision D.04.04 This document will be updated when new firmware upgrades are available. If you have questions about which firmware you need to upgrade your HP JetDirect print servers, please call your local HP service provider; in the US call the HP Customer Support Center at (208) 323-2551. HP FIRST #: 7485, BPJ02930, (firmware.txt), 25-Jan-96 Windows is a U.S. trademark of Microsoft Corporation. Copyright Hewlett-Packard Co. 1995 This information is subject to change without notice and is provided "as is" with no warranty. Hewlett-Packard shall not be liable for any direct, indirect, special, incidental or consequential damages in connection with the use of this material.