F
Frank
problem is that some of the machines can do drive letter
mapping very quick while others take about 20 seconds to
do the first mapping for each new server. subsequent
mappings to the server are then quick. however, after a
bit of quiet time, the slow clients are slow again to
connect to the server for the first time.
smells like a name resolution problem.
the enviornment...
running win2k server with integrated dns on the Domain
controller.
also running wins (to replicate with another domain over
a wan link) on one of the win2k servers (not the same as
the one running dns. but it is a DC).
all clients set to use the WINS server on the network and
user the win2k dns server as the primary dns server.
no lmhosts or hosts files... as far as i know.
is there any kind of logging/debugging tool to put on a
client to see what/how it is trying to do name
resolutions?
mapping very quick while others take about 20 seconds to
do the first mapping for each new server. subsequent
mappings to the server are then quick. however, after a
bit of quiet time, the slow clients are slow again to
connect to the server for the first time.
smells like a name resolution problem.
the enviornment...
running win2k server with integrated dns on the Domain
controller.
also running wins (to replicate with another domain over
a wan link) on one of the win2k servers (not the same as
the one running dns. but it is a DC).
all clients set to use the WINS server on the network and
user the win2k dns server as the primary dns server.
no lmhosts or hosts files... as far as i know.
is there any kind of logging/debugging tool to put on a
client to see what/how it is trying to do name
resolutions?