| |
When there is a long delay before the expected result:
-
DNS:
Test the same name with the
nslookup command on the machine (client or server) that is slow. If
nslookup is also slow, you have a DNS problem. If it's slower on a client, you have too many protocols bound to the Ethernet card. Eliminate NetBEUI, which is infamously slow, and optionally, Novel, assuming you don't need them. This is especially important on Windows 95, which is particularly sensitive to excess protocols. -
Broadcast/ WINS:
Test the client using
nmblookup, and if it's faster, you probably have the protocols problem as mentioned in the previous item. -
NIS:
Try
ypmatch, and if it's slow, report the problem to your network manager. -
NIS+:
Try
nismatch, similarly. -
hosts:
hosts files, if of reasonable size, are always fast. You probably have the protocols problem mentioned under DNS, above. -
LMHOSTS:
This is not a name lookup problem;
LMHOSTS files are as fast as
hosts files.
|
|
