--------------------------- LANtronix --------------------------- ETS/EPS --------------------------- Terminal and Printer Server --------------------------- Software Release Notes --------------------------- Version V3.5/3 December 02, 1997 Copyright 1997, Lantronix Release notes are also available using the Lantronix media support and download system or via anonymous FTP from ftp.lantronix.com. Contact Lantronix or your reseller for more information. This document describes the Lantronix Terminal/Printer Server software release. Release Summary =============== V3.5/3 ------ V3.5/3 provides traditional terminal and print server functionality, including the TCP/IP, Novell, Appletalk, Lan Manager and LAT protocols on the ETS4P4, ETS8/16, ETS8P/16P, and EPS4/12 platforms. Appletalk, Lan Manager and Novell support is limited to print serving. V3.5/3 provides print server functionality, including the TCP/IP, Novell, Appletalk, Lan Manager and LAT protocols on the EPS2P2, EPS4P1, EPS1/2, LPS and MPS platforms. Note that these units are print servers. They will not allow outgoing connections to hosts. V3.5/3 provides terminal server functionality, including TCP/IP, Novell and LAT protocols on the MSS1 platform. Note: V3.5/3 software will only download on LPS1 units with a Boot ROM revision of V2.4 or greater. (The ECO revision must be "CA3" or greater.) Note: All Lantronix terminal and printer servers except the MSS1 are supported by EZWebCon, Lantronix's new Java based configuration tool. EZWebCon is available on the Lantronix FTP site or CDROM number 13 or greater. Note: The EZCon configuration program supports the EPS1, EPS2, MPS, LPS, EPS2P2 and EPS4P1 print servers and the MSS1 serial server. It does not support the EPS4, ETS4P4, ETS8/16 or ETS8P/16P terminal servers. New Features ============ The following is a list of new features in V3.5/3. SNMP Enterprise ID Numbers -------------------------- SNMP Enterprise ID numbers have been updated to better reflect the actual Lantronix hardware platforms. These values are returned when a "Enterprise ID" packet is requested. Product Show Version Results SNMP Enterprise ID ----------------------------------------------------------------------- Old ETS8 (Grey case) 1a 8 Old ETS16 (Grey case) 1b 9 ETS8 1c 10 ETS16 1d 11 Old EPS4 (Grey case) 2a 16 Old EPS12 (Grey case) 2b 17 ETS4P4 2c 18 EPS1 3a 24 EPS2 3b 25 EPS2P2 3c 26 EPS4P1 3d 27 LB2 4a 32 LSB4 4b 33 MPS1 5a 40 MSS1 5b 41 LPS1 5c 42 LRS2 6a 48 LRS16 6b 49 LRS1 8a 64 LRS32F 9a 72 Logging ------- When Network logging is enabled, log when outbound sessions are started and stopped. MSS1 Port Names --------------- On the MSS1, allow the port name to be changed. Use the syntax: CHANGE PORTNAME where can be up to 16 characters long. MSS1 SNMP Sets -------------- On the MSS1, allow SNMP sets if a writable SNMP community name has been defined. Use the following commands to define and display a writable SNMP community: CHANGE SNMPSETCOM SHOW SNMP where can be up to 15 characters long. Note that one read-only SNMP name ("public") is always define. To remote the writable SNMP community, use the keyword "NONE" as the community name. LPD Banner Page --------------- If the date is available from daytime responses, use it when printing out the LPD banner page. Connect Local Command --------------------- The "CONNECT LOCAL" command has been added to the ETS4P4 and ETS8P/16P terminal servers. This allows a local connection to a port. Use the syntax: CONNECT LOCAL PORT_n where PORT_n is the port name of the target port. Resolved Problems ================= Miscellaneous ------------- If a server serial port was in help mode several layers deep and a very long command line was issued, the server could crash. When parsing a BOOTP response, if there was no path in the BOOTP reply, the server software did not correctly check for a .SYS extension on the filename. This could result in a loadfile that looked like mps.sys.sys. When a value of zero was entered for the serial delay parameter, the servers would save a value of 30 milliseconds rather than the correct value 0. When entering a dialback string, the length checks for the dialback and number string were not correctly checked. (limits are 20 characters for the name and 32 characters for the number) When dedicating a port with "preferred rlogin" allow the command to include a host string. When forming a connection to a parallel port with no printer attached and then immediately disconnecting without transmitting any data, the port could get stuck in a job state and not allow any subsequent connections. When using a ETS8P or ETS16P as a outgoing protocol (LAT to TCP/IP RTEL) translation server, jobs could take a long time to start or to complete. Help text for the ETS8P and ETS16P now correctly shows the available port baud rates. On the EPS1 and EPS2, the serial port was always set to one stop bit regardless of the setting of the serial port "stop bits" value. On the MSS1, a virtual port logging out could change the serial settings of the serial port. On the MSS1, flow control could not be set to "none". Lan Manager/DLC --------------- On the MPS1 and LPS1, a LanManager string could overflow the amount of memory allocated for it. This would cause random memory corruption usually resulting in the MPS1 hanging or rebooting. When using the DLC protocol to print, if a packet was lost due to network congestion, the print servers were not being aggressive enough in retransmitting the packet. This could result in low throughput. LAT --- When forming LAT connections with the ETS4P4 and ETS8P/16P, the server could crash depending on what information the host returned in negotiation packets. When forming LAT connections on the MSS1, The LAT "Aux Data" packets were not correctly formatted for baud rates greater than 38.4 Kbaud. TCP/IP ------ When using LPD printing, the "-f" was incorrectly removing control characters that had a value in the range 0x80 to 0xff. If a incoming LPD request did not specify a service name, the job would be printed to a random physical port. These "incorrectly formatted" requests are now rejected. Incoming connections to sockets associated with physical ports (i.e. 20nn, 30nn and 40nn socket numbers) were being checked against the incoming telnet server characteristic. This server characteristic is intended only to control incoming telnet connections. If the TCP/IP protocol was disabled and the print server tried to send a SNMP trap packet, the server would stall. The server was capable of transmitting a destination packet with an invalid IP address of 0.0.0.0. The netstat command would show the owner of UDP connections as the local server's IP address rather than showing the IP address of the last packet received or transmitted. When entering a SNMP community name, the name length was not correctly checked. This would allow SNMP community names to merge together. SNMP community names are allowed to be 14 characters On the MSS1, the "NONE" keyword for the command "SET SNMPSETCOMM" was case sensitive when it should not have been. On the EPS4P4, EPS8P and EPS16P, SLIP was not working properly. On the ETS8P and ETS16P, the IP security would not work correctly when a security rule had as its last octet .255. Known Problems ============== The following problems are known in V3.5/3. Printing directly from a Windows for Workgroups machine is not supported because of a problem in WFW. If the print server is flow controlled by the printer and in turn flow controls the WFW host machine, the WFW host will abort the print job. This means that if the print job is larger than the print server's internal buffer (maximum 4Kbytes) the print job will fail. The only workaround for this problem is to spool the jobs from the WFW machine to a Windows NT machine and print to the print server from there. LPD printing from Solaris machines is problematic due to the way Sun has implemented the Solaris spooling system. This problem has been reported to Sun. Their suggested workaround is "Do not print using LPD from Solaris machines to network based print servers. Instead use the vendor supplied printer interface programs." For Lantronix print servers this is the RTEL software. Please see the RTEL man pages for more information about configuration and use.