Discussion Locked

W2K Pro delay accessing NTS4 mapped driv

0 helpful
11 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a W2K Pro machine and connect to home folder on NTS4. If I open Windows Explorer and double-click to open any office 2000 doc on my mapped home drive, explorer freezes for 45-60 seconds and then I can open the file. I check Task Manager andit shows Explorer as "not responding". I can move the same file to a W2K server and have no delay. Also, moving the file to my local drive works fine. Installed SP1 for W2K and no change. Any ideas?

11 replies

by gregory w. smith

I'm going to bet it's name resolution. If you try to "run" a serverneame in NT or 95, you need to map the NetBIOS name to the machine's IP address. IN 2000, you *may* also need a Win2000 DDNS Server and static mappings on it to WinNT boxes.

Also,you could create a local LMHOSTS file with the name to IP mapping in it.

If LMHOSTS fixes it, then you know the delay is name resolution.

by tneese

I have already tried all of these things and no success. Some things work and some do not. Seems to be related to file associations.

by syscokid

WIndows 2000 NTFS and native NT NTFS aren't compatible unless you've applied at least SP4. The delay may be 2000 opening and converting from an incompatible format. Make sure server has at least sp4.

by chris

I read a discription of this problem last week, that discribed this problem.
What the article said was:
When a Windows 2K machine tries to connect to another machine (through browsing, or start/run - \\machine name), it queries the scheduled taskson that server. What happens if the server isn't running the scheduler? You time out - and this could take 40 or so seconds.
There was a registry hack that disabled this feature in Windows 2000 -- but I can't for the life of me remember what it was.

by michael roark - ccna/da mcp 3csa

what sped my 2kpro machines up is this..
netbeui isn't installed by default on win2k machines..
install it and make it the default protocol,,
it doesn't have overhead like TCP/IP does..
you'll be back to zooming...
Good Luck,,,

This discussion is closed to new replies.