Question Locked

LOGIN VERY SLOW IN DOMAIN

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I HVE A PROBLEM WINXP LOGGING IN DOMAIN, I ADDED ACTIVE DIRECTORY,DNS,DHCP IN MY WINDOWS2003 SERVER. PROBLEM WHEN I TRY TO LOGIN DOMAIN FROM WINXP CLIENT ,IT IS TAKING TOO MUCH TIME, AT LEAST 15MIN. PLEASE any one help me to solve problem

5 replies

by jamesmondtan

How many users are there?
Are you refer using vpn? if not how far is the distend between your client and server?
Is there a lots of scripts running, patching update, or windows update, or software update?
Try unplug the cable and see how is the login speed. If it login fine when you unplug the cable, it means there is something to do with server that makes it slow. Especially policy or script.

by julian.bennett

In my experience, this is usually because the clients DNS is not correctly configured!

Ensure that your client has a DHCP address then on the client from a command prompt enter ipconfig /all and review the results. Are the DNS server IP's correct!? If so, is your DNS working correctly (you can check the DNS event logs for this).

Can you ping the server name from the client in both its hostname and FQDN?? (eg. server01 and server01.domain.com)

Also, ensure that the clients hosts file does not have conflicting entries! (you could also check lmhosts)

Confirm these 1st...

After that.. could it be group policy, or logon scripts...

and finally, the one that always gets missed!!!

Do you have any mapped drives set for reconnect at logon, that your pc, just can't get to!!! These really will slow things down... once you've logged in, open windows explorer and check your mapped drives especially those that are disconnected, can you get to these network destinations??

hope this helps!

by dayron

Hello. Make sure your domain controller's DNS is set to it's own IP address. MAke sure your XP workstation's DNS is set to your domain controllers IP address. Also check event viewer in XP And Win2k3 for clues as to what the problem may be.

This discussion is closed to new replies.