Hi,

We are running a MS SBS 2003 server with both 2k and xp pro clients, everything runs normal, but we are wondering why the w2k logins are always fast and the xp logins always slow (1min or more).

Someone an idea?
(Heard something about win2k logging only the user in the domain and xp both user and computer?...)

Tnx!

Typically a domain login is slower than logging into a PC locally. This is because it has to load domain info and often enough, run scripts and software that a standalone PC doesn't.

Check the msconfig on the XP clients. You could very easily have software loading on them that isn't on the 2000 PC's which would cause them to load slower.

If you want to check what's all loading on the 2000 PC's for comparison purposes you'll need to download/install software to do so as it didn't come with msconfig. I prefer Startup Control for this. It's a nice little freeware app that does the same job as msconfig, only better.

Thank you for your reply Curt,

However, the problem is not what the computers have to load, if I use a fresh installed XP or 2K, the xp login is still slow (+1min), while the 2K login is always fast (5sec).
They both run the same scripts, are on the same network etc. Even with no scripts and nothing extra it's like this.
I've tested this in a situation where there is really no difference but the OS.

Thus I'm convinced XP logs in differently then 2K.

Ps: Older versions like Win9x/ME (Wins) login just as fast the 2K's.

Nobody with the same experience??

Server is quite simple:
Amd3200/1024/raid1
DC / dhcp / fileserver

I've got the same problem, but I'm using Windows 2000 Server. It only happens when the PC is connected to de LAN, for example, if you disconnect the XP computer from the LAN it would log into the domain very fast. But if it IS connected, it would take over 2 minutes to log in.

Another post suggested inserting the server's IP address into the DNS settings of the XP machine. I'm having the same slow login issues so will try this and see if it helps.

I found a lengthy post on another site that seems to quote MS KB text and offers an explaination and solution... we'll see if this helps:
Lenthy logins to a domain are usually caused by incorrectly setting up
DNS. Here is information about that from MVP Ron Lowe:

"XP differs from previous versions of windows in that it uses DNS as
it's primary name resolution method for finding domain controllers:

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

"3) Ensure the Win2k server points to itself as a DNS server.

"4) 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 (".") 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 lookup zones if it asks."

How Domain Controllers Are Located in Windows XP -
http://support.microsoft.com/default.aspx?scid=kb;en-us;314861
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
DNS and AD FAQs - http://support.microsoft.com/?id=291382

I have finally cracked the strange XP to windows 2000 server issue... many people suggested it to be a DNS problem, which is true, however I have not seen anyone post the exact details of how to fix it.

Apparently I missed a step in setting up DNS. Here is the full set of how-to-fix instructions:
1. Install DNS on the DC (Windows 2000 Server)
2. *** KEY MISSING STEP *** Create a forward zone on the DNS that will include the domain systems (basically default settings for zone). Without this part, the DC DNS will only cache IP/names and therefore won't even include itself in lookups.
3. Change the primary DNS on all domain systems to the DC IP address. A secondary DNS can still be there, but primary should be the DC.
4 (optional) Just for fun, make sure WINS is running on the DC and the systems are also pointed to the DC IP

Just a side note, you can still use DHCP for the workstation IP and force the DNS setting. This is the configuration of one of the workstations that I have. Others are running static IP with static DNS and also seem to be working fine now.

Once I had this fixed, logins were back to the expected 3-5 seconds instead of the 1.5-5 minutes. Roaming profiles also seem to be working fine now that all of this is configured properly.

Good luck!!