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

From: wingtong (wingtong.1bmc0y_at_pcbanter.net)
Date: 08/26/04 

Date: Thu, 26 Aug 2004 19:28:57 +0100

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 20-30 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. But if the xp's are
left on (like all night) without accessing those mapped drives, their
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 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

- regedit delete key that scans for scheduled tasks

..any other suggestions would be appreciated. 

-- 
wingtong