Book B-39Chapter 1 Network AdministrationRemote Annex Administrator’s Guide for UNIXBook BConnection Delays When Using Name ServersAnnex users may notice connection delays under certain circumstances.If name_server_1 and name_server_2 are defined, and name_server_1is down or does not exist, there will be a 15–30 second delay untilname_server_2 resolves the name during a connect to a host using rloginor telnet. If both name servers are down or they do not exist, there willbe up to a 45 second delay. If the host to which the user ID is trying toconnect is in not in the RWHO host table, an error occurs; the terminaldisplays a message informing the user that the name server is unreachable.Hosts not Appearing in Hosts DisplayThe Annex hosts command should list any hosts that broadcast RWHOpackets if the configuration parameter rwhod is set to Y. If you expectto see a host in the hosts display and it does not appear, wait severalminutes and then re-issue the hosts command before assuming there is aproblem; the time between broadcasts can vary. Before proceeding, verifythat the host not appearing in the hosts display is sending RWHO packetscorrectly by entering ruptime on another host on the network, or bychecking that the host in question is running rwhod.If the host is sending RWHO packets correctly, incompatible broadcastaddresses may be causing the problem. Originally, a broadcast packetused a host address of all zeros (network.0). Later refinements requireda change to the broadcast address, specifying a host address of all ones(network.255). A host configured with a network.255 address will acceptnetwork.0 broadcasts. Hosts configured with network.0 addressing willnot see network.255 broadcasts. You can configure the Annex for eithermethod of addressing by setting the broadcast_addr parameter.