New XP machines intermittent delays on Domain

[Guest]

I administer a Win2k domain. 2 Domain controllers, 2 member servers, 1 exchange server, about 40 mixed clients 98 & XP Pro. Everything has been running fine until we purchased some new Dell machines. All of our other workstations are Dell of varying models. As a rule, I wipe the new systems we get from Dell and install XP clean to avoid all the garbage programs that get installed at the factory

I had 4 of these identical machines connected to the domain for a couple of weeks when I was told by the users about slowness. Generally these users experience a delay of about 15 seconds when choosing "open" within Excel and they switch folders on the network. After the first delay, everything moves quickly enough, but after 10 minutes or so the problem returns. I've duplicated the problem by using other applications as well as using explorer independent of any Office programs with the same result. First attempt takes 15 seconds...subsequent attempts are normal speed until no attempts are made for a while. All of this file access is taking place over a mapped drive to our primary Win2k file server/domain controller

I've disabled power management across the board, including the NIC itself
Updated drivers for the Broadcom 440 10/100 NIC
Disabled the enumeration of scheduled tasks and printers during network resolution
Verified that they are connecting at 100mbps. The 4 clients were initially connected to 2 different 10/100 switches...I've now grouped them on one switch
Added the domain specific DNS suffix for the connection, for good measure
Verified that my DNS servers are working correctly. I have no problems with resolving any names
Ping statistics always return <1m

We do have one Novell server and are running the Novell client 4.90...some machines are using the 4.83 client. My personal XP Pro machine has all of the same sofware and configurations...plus much more like WebJet Admin and I have no delays whatsoever. There are also several other XP Pro machines on the network who don't have this problem. So far, the only common denominator is the model of computer and it's integrated NIC

I've been Googling my brains out and coming up with all of the same solutions. Does anyone have anything different to look for

We just received 2 more of the same machines that were ordered before we realized there was a problem. I'll be working with one of those to continue troubleshooting

Thanks

 

[Robert L [MS-MVP]]

quoted from http://www.ChicagoTech.net
Why is XP running slower while logon 1

When I login into a Windows 2000 active directory from a new xp pro machine
the login in is extremely slow. After logged on, everything works fine. But
other windows versions don't have this problem.
A: This is almost like name resolution issue. Comparing with previous
versions, XP is heavily dependent on DNS to find DC. If the DNS is
configured incorrectly, XP will take longer time waiting for it to timeout
before it tries using NetBIOS. Make sure
1) The DNS setup correct and have the server information.
2) XP clients can find the DNS server.
3) XP machine's DNS server is pointed to your internal DNS server rather
than your ISP's DNS server.
4) Make sure no errors on logon scripts or GPO's that could be causing
the delay.
5) Check any errors on event viewer.
6) Disable NetBIOS on the interfaces that client will not use.

--
For more and other information, go to http://www.ChicagoTech.net

Don't send e-mail or reply to me except you need consulting services.
Posting on MS newsgroup will benefit all readers and you may get more help.

Robert Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.

 

[Guest]

Robert,

Not to be rude, but if you had read the post you would have learned that login delay is not the problem and DNS has already been eliminated

PTP

 

[Lanwench [MVP - Exchange]]

If you run net use from a command prompt, do you see any drives mapped to
unavailable shares/servers? This is the most common cause of this problem in
my experience. Are you using a login script? I usually delete old mappings
and remap using /persistent:no as a matter of course.

 

[Robert L [MS-MVP]]

sorry, how about this one. http://www.ChicagoTech.net

Why is XP running slower 2

If the resolution of "Why is XP running slower while logon 1" doesn't fix
the slower issue. and if other Operation Systems including w2k don't have
the same issue, you may check the hardware settings, for example, configure
all of the computers' network cards for half duplex. Most Hubs don't
support full duplex.


--
For more and other information, go to http://www.ChicagoTech.net

Don't send e-mail or reply to me except you need consulting services.
Posting on MS newsgroup will benefit all readers and you may get more help.

Robert Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.

 

[Guest]

Excellent thought Lanwench. (love the name btw

I didn't find any maps to unavailable shares, but I did see that the mapped drive in question listed itself as being disconnected. I browsed a folder in explorer and the lovely 15 second wait reared it's ugly head. I ran net use again and the drive showed as OK. I think I'm on to something, though our logon script has only one command
Net Use N: \\<server>\dat

Adding "Persistent" should only cause the drive to reconnect at logon, but viewing the connections through Net Use has given me hope

Thanks again

PTP

 

[Lanwench [MVP - Exchange]]

Excellent thought Lanwench. (love the name btw )

Thanks - Nerdgirl was already taken, alas.

I didn't find any maps to unavailable shares, but I did see that the
mapped drive in question listed itself as being disconnected. I
browsed a folder in explorer and the lovely 15 second wait reared
it's ugly head. I ran net use again and the drive showed as OK. I
think I'm on to something, though our logon script has only one
command: Net Use N: \\<server>\data

Adding "Persistent" should only cause the drive to reconnect at
logon,

Yes - and keep it from being cached....

but viewing the connections through Net Use has given me hope.

Have you looked at KB 297684 ?