XP Pro log onto 2000 domain VERY slow 1

[mquinn0908]

I have a few XP machines that are logging into a 2000 domain. These machines take at least 5 minutes or more to log onto the domain. There are no roaming profiles being used so does anyone have any ideas or suggestions as to what is causing this and how to resolve it? Thanks.

 

[Titleist]

You could try setting the NIC's on the XP machines to half or full duplex(depending on your switch) and not autosense.

 

[mquinn0908]

I tried this and had no luck. Is there any thing else that might be causing this long delay in being able to log onto the domain?

 

[GoldenEagle]

At home I use a PC with XP Home on it to log on to our Windows 200 network at work, via a 56K modem. This is very slow indeed. When I start up Outlook it can take up to an hour before I can open any emails.

I also have an old laptop running Windows 98. If I use this instead I can get to my emails in less than 5 minutes.

Is there a problem between XP and 2000 domains?

 

[GoldenEagle]

At home I use a PC with XP Home on it to log on to our Windows 2000 network at work, via a 56K modem. This is very slow indeed. When I start up Outlook it can take up to an hour before I can open any emails.

I also have an old laptop running Windows 98. If I use this instead I can get to my emails in less than 5 minutes.

Is there a problem between XP and 2000 domains?

 

[michaelfranks]

I had the same problems ie logging on to the XP workstation was fast but domain logons were very slow - then I sorted out my DNS settings on the 2000 server(sorry but I don't have the exact details of the DNS settings)Since doing this my logons are now virtually instantaneous.

 

[j3w3ll]

There has been many problems with xp and 2K domains, do you run SP1?

if so i found this information on the web, it solved the problems i was having, (ms office apps running v.slow and crashing). rather than me writing it all out again visit this url where i found the fix

http://www.brienposey.com/kb/XP_Network_Problems.asp

good hunting

 

[pyoungmwl]

I tried this ....

http://www.brienposey.com/kb/XP_Network_Problems.asp

and it worked on one network but not on others where the same problem existed. Any more ideas, anyone?

 

[j3w3ll]

The only thing i can think of is, do the networks which it didnt fix have some sort of OU' policies set that block/override the one from domain controllers. Apart from that im in the dark to why it didn't work. Service pack 2 is ment to solve this problem, when it is available I dont know.

Good luck

 

[Ali147gta]

I have posted this before as have others network logon issues can virtually always be traced back to incorrect DNS settings, This should be your first checkpoint


Hope you get it resolved

 

[Tezzie]

As mentioned before, its due to DNS, or to be exact, you have a . (full stop) in your forward lookup zone which you can safely delete.


Tez

Women are like computers, you have to press a button to turn them on.

 

[bcastner]

I made some comments in the thread "XP Logon Slowness" that addresses the issue in this thread.

 

[pyoungmwl]

This is NOT a DNS problem. Try this link ......

http://support.microsoft.com/default.aspx?scid=kb;en-us;329457

 

[bcastner]

pyoungmwl,

Your link simply says that SP1 provided a fix for this.
It is most likely a DNS issue, and an IPCONFIG /all at the workstation would should that the DNS entries are not pointing at the DC.

 

[bcastner]

If the XP workstation clients have SP1 installed, then on a Win2k domain this problem is almost always a combination of:

1. Autosensing failure between switch and workstation NIC; you can use this matrix for some hints as to how to force the workstation & switch settings:
[tt]
Workstation Switch Result

Forced Half Forced Half Works
Forced Full Forced Full Works
Auto Auto Maybe
Forced Full Auto NO
Auto Forced Full NO
Forced Half Forced Full NO
Forced Full Forced Half NO
[/tt]

2. DNS resolution issues.

Slow logons from XP to a win2000 domain usually indicate a DNS misconfiguration issue. While the following is not a fix-all for all AD-domain problems, it is an absolute requirement that DNS is set up correctly before it will work properly. If your DNS is not set up like this, then you will experience problems like you describe. XP differs from previous versions of windows in that it uses DNS as it's primary name resolution method for finding domain controllers: How Domain Controllers Are Located in Windows XP

http://support.microsoft.com/default.aspx?scid=kb;en-us;314861>

If DNS is misconfigured, XP will spend a lot of time waiting for it to timeout before it tries using legacy NT4 sytle NetBIOS. (Which may or may not work.)

1. Ensure that the XP clients are all configured to point to the local DNS server which hosts the AD domain. That will probably be the win2k server itself. They should NOT be pointing an an ISP's DNS server. An 'ipconfig /all' on the XP box should reveal ONLY the domain's DNS server. You should use the DHCP server to push out the local DNS server address.

2. Ensure DNS server on win2k is configured to permit dynamic updates. Ensure the win2k server points to itself as a DNS server.

3. For external (internet) name resolution, specify your ISP's DNS server not on the clients, but in the forwarders tab of the local win2k DNS server. On the DNS server, if you cannot access the 'Forwarders' and 'Root Hints' tabs because they are greyed out, that is because there is a root zone (".&quot present on the DNS server. You MUST delete this root zone to permit the server to forward unresolved queries to yout ISP or the root servers. Accept any nags etc, and let it delete any corresponding reverse lookuop zones if it asks.

The following articles may assist you in setting up DNS correctly: Setting Up the Domain Name System for Active Directory <

http://support.microsoft.com/default.aspx?scid=kb;en-us;237675>

HOW TO: Configure DNS for Internet Access in Windows 2000 <

http://support.microsoft.com/default.aspx?scid=kb;en-us;300202>