winxp client + winnt4 domain server = slow initial access too mapped drives
I have just added 2 new XP clients to our winnt4 domain server (with both winnt4 and win2000 servers on network). All previous clients are win2000. The 2 new XP clients seem to take 15-20 seconds when accessing mapped drives (to winnt4 and win2000 server drives) for the first time after logon.
I have just added 2 new XP clients to our winnt4 domain server (with both winnt4 and win2000 servers on network). All previous clients are win2000. The 2 new XP clients seem to take 15-20 seconds when accessing mapped drives (to winnt4 and win2000 server drives) for the first time after logon. I noticed if I tried to activate Windows Explorer right after logging in and accessing one of those mapped drives, I can get in relatively quick, but hitting the "back" button will freeze that window (have to Task Manager out of it), then all other mapped drives are still slow to get into the first time. After getting into them the first time, however, subsequent access is fine.
I've already tried (without success):
- GPEDIT.MSC Local Computer Policy-> Computer Configuration-> Administrative Templates-> System-> Logon -> "Always wait for the network @ computer startup and logon" (enable)
- GPEDIT.MSC Local Computer Policy-> Computer Configuration-> Administrative Templates-> System-> Scripts-> "Run logon scripts sychronously" (enable)
- Run NetBIOS over TCP/IP
...any other suggestions would be appreciated.
I've already tried (without success):
- GPEDIT.MSC Local Computer Policy-> Computer Configuration-> Administrative Templates-> System-> Logon -> "Always wait for the network @ computer startup and logon" (enable)
- GPEDIT.MSC Local Computer Policy-> Computer Configuration-> Administrative Templates-> System-> Scripts-> "Run logon scripts sychronously" (enable)
- Run NetBIOS over TCP/IP
...any other suggestions would be appreciated.
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
I experience similar problems with our network. One of our vendors mentioned a TCP timing setting on the WinNT server that gives a 50ms delay on any communication. Thus if you have that delay on every transmission (it has to scan the mapped drives when you connect) you could see this kind of delay.
Sadly I didn't write down the setting as I was thinking about other things at the time, but at least you've got somewhere to start.
Sadly I didn't write down the setting as I was thinking about other things at the time, but at least you've got somewhere to start.
...ok, so now I am told that the problem is most likely caused by our network not conforming to standard IP addressing. Our range of IPs are 205.133... which is a public range while our subnet is 255.255.0.0 which is private (don't blame me, some consultants set it up that way back in 1997ish). In any case, I tested it by setting 2 computers (1=xp 1=win2000) where the xp had the problem of slow initial connection to the win2000; changed the IPs on both machine to a 172.16... range and the XP connnected just fine (probably can still use more testing). Aparently winXP is alot more strict on IP usage and what seems to happen is that the XP tends to check public IPs on the internet for the machines first before going to our internal network and therein lies the delay (theoretically).
Anyhow, short of redefining all our systems IP numbers (alot of static ip's), does anyone have any suggestions on a workaround to force the XPs to look only in our internal network and not try to go to the internet? I've already tried the following without any success:
- map drives using IP numbers (ie. \\205.133.xxx.xxx\shared)
- set IP in HOSTS file
Anyhow, short of redefining all our systems IP numbers (alot of static ip's), does anyone have any suggestions on a workaround to force the XPs to look only in our internal network and not try to go to the internet? I've already tried the following without any success:
- map drives using IP numbers (ie. \\205.133.xxx.xxx\shared)
- set IP in HOSTS file
