Lantronix ETS Reference Manual - 4.5.1 Ip Address
Server Configuration
TCP/IP Server Parameters
4-5
By default, the ETS will only query local fileservers, but this may still be too many in a large network. The
Clear/Purge Protocol NetWare Access command allows you to remove items from the access list.
The Set/Define Protocols NetWare Reset command can be used if necessary to force the ETS to rescan all
fileservers for pending jobs. This is useful after rebooting or after configuring new queues on the fileservers
to ensure that the ETS recognizes queues directed to it.
Keep in mind that fileservers cannot tell if the ETS is not polling them due to access restrictions. There will
be no error messages if a valid fileserver cannot print to the ETS due to the access list.
4.5 TCP/IP Server Parameters
If you want TCP/IP connectivity (Telnet, Rlogin, LPR, and RTEL support), you must configure IP
parameters on the ETS. First and foremost, the ETS must have a unique IP address. If this was set at boot
time (by BOOTP, DHCP, or RARP), it does not need to be reset. Other parameters are explained in this
section.
Note:
An IP address is also required for EZWebCon use.
4.5.1 IP Address
To configure the ETS’s IP address, use a command of the following form.
Figure 4-10: Setting the IP address
One of the most common problems is that of duplicate IP addresses on the network. Signs of this problem
are Telnet/Rlogin connections that fail soon after connecting and ARP requests that do not find a known
host. If the server either loses its IP address when booting or will not allow a new IP address to be
configured, another host might be using the same address. If any of these problems occur, double check to
make sure that your ETS has a unique IP address on the network.
Note:
See your Installation Guide for more information on configuring the IP address.
4.5.2 Other TCP/IP Parameters
Users can define a nameserver host if you want text TCP/IP host names to be resolved, and a default domain
name to use in case a domain is not specified. You can also set a gateway host, which allows TCP/IP
connections to other connected network segments. Finally, you can set a loadhost (if not done already) so
that TCP/IP boots will be attempted.
Figure 4-11: Setting TCP/IP Parameters
Local> DEFINE SERVER IPADDRESS 192.0.1.228
Local> DEFINE SERVER NAMESERVER 192.0.1.29
Local> DEFINE SERVER DOMAIN “weasel.ctcorp.com”
Local> DEFINE SERVER GATEWAY 192.0.1.188
Local> DEFINE SERVER LOADHOST 192.0.1.33