11 replies
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
by syscokid
by tneese
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 tneese
by tneese
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,,,
by tneese
by tneese
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending