General discussion

Locked

W2K Pro delay accessing NTS4 mapped driv

By tneese ·
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?

This conversation is currently closed to new comments.

11 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

W2K Pro delay accessing NTS4 mapped driv

by Gregory W. Smith In reply to W2K Pro delay accessing N ...

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.

Collapse -

W2K Pro delay accessing NTS4 mapped driv

by tneese In reply to W2K Pro delay accessing N ...

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.

Collapse -

W2K Pro delay accessing NTS4 mapped driv

by SyscoKid In reply to W2K Pro delay accessing N ...

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.

Collapse -

W2K Pro delay accessing NTS4 mapped driv

by tneese In reply to W2K Pro delay accessing N ...

Already at SP5

Collapse -

W2K Pro delay accessing NTS4 mapped driv

by chris In reply to W2K Pro delay accessing N ...

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.

Collapse -

W2K Pro delay accessing NTS4 mapped driv

by tneese In reply to W2K Pro delay accessing N ...

The question was auto-closed by TechRepublic

Collapse -

W2K Pro delay accessing NTS4 mapped driv

by PrinterManager In reply to W2K Pro delay accessing N ...
Collapse -

W2K Pro delay accessing NTS4 mapped driv

by tneese In reply to W2K Pro delay accessing N ...

The question was auto-closed by TechRepublic

Collapse -

W2K Pro delay accessing NTS4 mapped driv

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,,,

Collapse -

W2K Pro delay accessing NTS4 mapped driv

by tneese In reply to W2K Pro delay accessing N ...

The question was auto-closed by TechRepublic

Back to Windows Forum
11 total posts (Page 1 of 2)   01 | 02   Next

Related Discussions

Related Forums