Drive Mapping Sluggish

  • Thread starter Thread starter Stewart
  • Start date Start date
S

Stewart

When W2K clients are started the system hangs for about 15
seconds while re-mapping the mapped drives. On the prior
server they mapped so fast you couldn't hardly notice it
was happening. Any ideas as to why it's taking so long?

Thanks
 
Stewart said:
When W2K clients are started the system hangs for about 15
seconds while re-mapping the mapped drives. On the prior
server they mapped so fast you couldn't hardly notice it
was happening. Any ideas as to why it's taking so long?

Thanks
Click to expand...

What method of name resolution are you relying on? DNS? WINS? netbios
broadcasting?
 
I'm using Netbios.
Click to expand...

I'm not surprised that the remap is slow, W2K first checks for a DNS server,
then attempts broadcasting unless you specify the ip_address in the lmhost
file. Also, since you aren't relying on DNS, you might consider controlling
which systems get the master browser and backup browser roles. This might
reduce the incident of browser elections every time a client boots. Dns is
the better solution, otherwise, modify the lmhost file.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Sluggish Alexa Response 6
Mapped Drive Empty 1
Force mapped drive not to connect at startup on Windows XP 4
Mapped drives disconnecting 1
Trouble with MAP DRIVES 2
Printer as mapped drive 3
mapped network drive keeps disconnecting?? 2
network drive mapping problem 1

Back
Top