winxp client + winnt4 domain server = slow initial access too mapped drives

[wingtong]

I have just added 2 new XP clients to our winnt4 domain server (wit
both winnt4 and win2000 servers on network). All previous clients ar
win2000. The 2 new XP clients seem to take 20-30 seconds when accessin
mapped drives (to winnt4 and win2000 server drives) for the first tim
after logon. I noticed if I tried to activate Windows Explorer righ
after logging in and accessing one of those mapped drives, I can get i
relatively quick, but hitting the "back" button will freeze that windo
(have to Task Manager out of it), then all other mapped drives ar
still slow to get into the first time. After getting into them th
first time, however, subsequent access is fine. But if the xp's ar
left on (like all night) without accessing those mapped drives, thei
initial access is slow again.

I've already tried (without success):

- GPEDIT.MSC Local Computer Policy-> Computer Configuration-
Administrative Templates-> System-> Logon -> "Always wait for th
network @ computer startup and logon" (enable)

- GPEDIT.MSC Local Computer Policy-> Computer Configuration-
Administrative Templates-> System-> Scripts-> "Run logon script
sychronously" (enable)

- Run NetBIOS over TCP/IP

- regedit delete key that scans for scheduled tasks

...any other suggestions would be appreciated

 

[Guest]

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

 

[Richard G. Harper]

Bite the bullet and fix the network. This is probably only the first of
many problems you'll experience while you keep it in this configuration.