Connection Delays When Using Name Servers; Hosts Not Appearing In Hosts Display - Nortel 2000 User Manual

Book B Chapter 1 Network Administration

Connection Delays When Using Name Servers

Annex users may notice connection delays under certain circumstances.
If name_server_1 and name_server_2 are defined, and name_server_1
is down or does not exist, there will be a 15–30 second delay until
name_server_2 resolves the name during a connect to a host using rlogin
or telnet. If both name servers are down or they do not exist, there will
be up to a 45 second delay. If the host to which the user ID is trying to
connect is in not in the RWHO host table, an error occurs; the terminal
displays a message informing the user that the name server is unreachable.

Hosts not Appearing in Hosts Display

The Annex hosts command should list any hosts that broadcast RWHO
packets if the configuration parameter rwhod is set to Y. If you expect
to see a host in the hosts display and it does not appear, wait several
minutes and then re-issue the hosts command before assuming there is a
problem; the time between broadcasts can vary. Before proceeding, verify
that the host not appearing in the hosts display is sending RWHO packets
correctly by entering ruptime on another host on the network, or by
checking that the host in question is running rwhod.
If the host is sending RWHO packets correctly, incompatible broadcast
addresses may be causing the problem. Originally, a broadcast packet
used a host address of all zeros (network.0). Later refinements required
a change to the broadcast address, specifying a host address of all ones
(network.255). A host configured with a network.255 address will accept
network.0 broadcasts. Hosts configured with network.0 addressing will
not see network.255 broadcasts. You can configure the Annex for either
method of addressing by setting the broadcast_addr parameter.
Remote Annex Administrator's Guide for UNIX
Book B-39