NEW SOFTWARE RELEASE Version 1.00 1(3) ==================== Product involved: AXIS 640/642 Release date: Feb 22, 2000 Release type: PRODUCTION Software version: 6.10 Software media: AXIS 640/642 Flash Last preceding release: AXIS 640/642 6.00 instructions: See upgrinfo.txt document --------------------------------------------------------------------- Easy Release Description: 1. IPP Support has been added. 2. NDPS over IP has been added. 3. SLP V2 support has been added. 4. HTTP digest authentication has been added. 5. Partial HTTP/1.1 support added. 6. SSI realms support added. 7. Fixed a problem with DHCP lease time handling. 8. TFTP config file download problem fixed. 9. LPD problem with zero-sized jobs solved. 10. Solved a problem that the print server would consume print jobs sent to a port that had no print attached. 11. ARP for address 0.0.0.0 are not sent anymore. 12. DHCP address validation problem solved. 13. Respond to ICMP ECHO (PING) when issued to broadcast address. 14. Corrected problems with fragmented UDP datagrams. 15. ECP and Bitronics negotiations problems corrected. 16. Corrected a problem of setting NBT Scope id. 17. Network speed information on web pages corrected. 18. HTTP URNs are now case sensitive. 19. A problem when printing from the HP IPP client was fixed. --------------------------------------------------------------------- Appendix A - DETAILED TECHNICAL DESCRIPTION OF RELEASE App A Product involved : AXIS 640/642 Software version : 6.10 1. Both IPP 1.0 and 1.1 are supported. This means that ipp-adress schemes 1.0 and 1.1 is supported. Ex 1.0: http://ip_or_dnsname:621/port Ex 1.1: ipp://ip_or_dns/port 2. Support for NDPS printing over IP for Axis Gateway. 3. SLP version 2 (SLPv2) corrects race conditions present in SLPv1. In addition, authentication has been reworked to provide more flexibility and protection (especially for DA Advertisements). 4. No additional information. 5. Only HTTP/1.1 headers needed for IPP are supported. IPP chunking supported, i. e. recieving blocks of data. Persistent connections are not supported. 6. No additional information. 7. If the DHCP lease time exceeded 65536 seconds (18 hours), then a renew procedure could be started with a very short interval. This could cause the print server to deny any TCP service in rare cases. 8. When using TFTP to download a configuration file at boot time, the print server could sometimes discard the settings in the configuration file. This was caused by the fact that the TCP/IP stack restarted when it retrieved a new IP address by DHCP. 9. If a LPD client sends a job with zero bytes, the session would hang. 10. When printing to a logic or physical printer port without any printer attached, a bug would "eat" the job, ie in status, the job would be reported as printed, 0 bytes. 11. In some cases, the print server sent ARP requests for the address 0.0.0.0. This could happen when WINS was enabled but the WINS server address was set 0 0.0.0.0. This has now been corrected. 12. DHCP uses ARP to validate the IP address offered. If any host on the network replies with the ARP request, then the address is considered to be invalid. In some cases, though, another host on the network may reply on the behalf of the print server, indicating that the requesting print server has the address. The print server invalidated the IP address in these cases and sent a DECLINE message to the DHCP server. This could cause the print server to invalidate all IP addresses in the DHCP server address pool. 13. According to ICMP specification, all network nodes should reply to ICMP ECHO (PING) requests that are sent to their broadcast address. This was not done at all before, but is now implemented correctly. 14. No additional information. 15. When changing ECP and Bitronics mode between forward and reverse it could happen that one extra byte was printed or returned as reverse data. The conditions were very rare. 16. No additional information. 17. No additional information. 18. No additional information. 19. Recieiving chunked IPP print data from the HP IPP client could in some instances result in corrupt printout. --------------------------------------------------------------------- Appendix B - SOFTWARE LIMITATIONS App B Product involved : AXIS 640/642 Software version : 6.10 1. Secondary printer function doesn't work when printing from AXPUW nor AXIS Print Monitor. 2. The maximum number of simultaneous TCP connections is set to 200. If many users are monitoring the status or accounting web pages, all connections may under rare circumstances be consumed by the automatic refresh function. This can cause problems accepting new print jobs using TCP/IP printing protocols. 3. Connecting a printer to a running print server causes a 30 seconds period when the print server is not accessible. ---------------------------------------------------------------------- Appendix C - AFFECTED MATERIAL App C Product involved: AXIS 640/642 Software version : 6.10 The User's Manual version 3.2 and User's Guide version 3.2 fully describe the features of this software release.