Computer with Domain?

Question

Hii,

I have setup the windows 2003 Server with Window XP Prof. The server is just File Server (Active Directory).

Problem is that Node takes approx 10 mins to logon (to display the desktop). Is there anyway to reduce the time of logon.

Answer 1

shouldn't you just be leaving it on all the time if its a server??

Answer 2

"lwcomputing" has nailed it. It's virtually always a DNS issue. Make sure that the DNS server points to itself and the clients point to the DNS server. If you need external resolution for DNS for internet access, set up forwarders on the DNS server.

Overly large Group Policy setups CAN slow down logins but that is not normally an issue on a LAN. It's only when the client and DC are separated by a slow WAN link that GPOs will make a noticeable difference in login times unless you've REALLY gone nutso with GPOs.

The other answers are simply wrong.

Answer 3

It's not a network issue, so dcdiag won't do you any good.

Your XP box is processing all kinds of unnecessary data. Out of the box, 2003 server with Active Directory is going to have default login scripts, group policy, etc. If you've got folder redirection... well, heck... there are a hundred things that can slow down logon. Go through your domain policies and eliminate any routines you don't really need.

Truth is, the #1 culprit is not the server/domain. It's the XP box itself. Go through the services one by one, and disable all the ones that are not essential to your work. Use msconfig to identify all startup programs, etc. that you really don't need to run automatically on startup. (Adobe, HP, your computer manufacturer's "help" files, etc. are notorious for autoloading. Not only do they take their own slice of RAM, they also slow bootup dramatically. It's a built-in "inconvenience".) Disable all the crap from autoloading on startup.
Check your antivirus. Some, such as Norton, are huge hogs of processor power for the first few minutes. Consider something much less intrusive, but just as effective, such as AVG.

Answer 4

There are a number of POSSIBLE causes for the problem but the most frequent cause is incorrect DNS settings. DNS is vital in an Active Directory domain. It is used to locate the Domain Controllers and other domain services. The server needs to run it's own DNS Server and point ONLY to itself for DNS resolution. (You can configure the DNS Server component to forward DNS queries to your ISP, but other than that, NO SYSTEM ON YOUR NETWORK SHOULD KNOW ABOUT ANY OTHER DNS SERVER!)

Then, make sure your workstations have ONLY the Windows DNS server listed as a DNS server. NO SECONDARY DNS SERVERS! (Unless you have other domain controllers running Windows DNS - then the secondary DNS servers can be the other Windows DNS servers).

For more information on DNS, how it should be setup and how it can cause problems when it's not configured properly, you can reference my web site:
http://www.lwcomputing.com/tips/static/dns.asp

Now, as I said, there could be other causes - problems such as large roaming profiles, corruption on the disk, registry issues, and other problems.

Answer 5

Computer with Domain logon within 2-5 minutes, because after select particular domain it request for service to logon. and server check permissions of particular accounts this process takes around 3-5 minutes.
Please check server configuration .i.e Domain.
It should be compatible not with server but with Domain,

Answer 6

Check for any error in the event viewer of the XP machine.
Check the time consumed for a local user (Create a local user in Xp machine and try)
If the local user login works fine, download dcdiag.exe (its in winddows support tools)
Run DCDIAG from xp machine.
Check for any errors.

Cheers!

S

Answer 7

install netbios in ur nodes.

and check ur switch.....i thing there is ARP flood in ur switch.

ur domain is perfect but check for ur DNS logs...............