4 replies
by dc1
by ewgny
Are the workstations DNS set to the IP address of your Domain Controller. - They must be if not.
Your Domain Controller's DNS should be configured to forward requests it can't resolve (for internet access)
Post any associated Event ID's back
by parbo
Is all well with dns on the server? Check the event log for any entries.
Make sure that pc's and server can resolve each other correctly - try ping by ip and by name at a command prompt. Also ensure that in dns the server is pointing to itself, and that you haven't got your isp's dns server address listed as a dns server in dns - only dns servers at the local level should be listed - isp's dns servers should be listed in dns forwarding.
The W2k Pro systems should have your server listed as a DNS server and not your ISP.
Also make sure that it isn't related to roaming profiles - these can also cause a lengthy log-on if they are transferring stacks of data.
by parvez2k
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending