Solved

Windows 7 taking forever to logon to domain

Posted on 2011-03-13
10
589 Views
Last Modified: 2012-05-11
Hello, I recently upgraded to a new network router and switch, and since then my computers have been taking at least 5 minutes to Log On to the domain after entering the password. It sits there and says "Please Wait..." and is very annoying. Any suggestions? The computers are on a Win 2003 domain. Thanks!
0
Comment
Question by:ls2gto
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 4
10 Comments
 
LVL 96

Expert Comment

by:Lee W, MVP
ID: 35125632
Check your DNS Settings - especially if you forgot to disable DHCP on the new router.
0
 
LVL 16

Expert Comment

by:Shaik M. Sajid
ID: 35125652
check the proper network settings and re join the domain it may be help ful... ene not re create user and rejoin the domain...

all the best
0
 
LVL 96

Expert Comment

by:Lee W, MVP
ID: 35125684
Misconfigured DNS often results in login delays.  DNS should point ONLY to the Domain Controller's DNS server.  DHCP, if it was switched to your router (especially if it was accidental) would not contain the correct DNS servers)
0
Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

 

Author Comment

by:ls2gto
ID: 35125699
I forgot to mention that all network settings are thru the router. Nothing on the server is configured for DHCP or DNS.
0
 
LVL 96

Expert Comment

by:Lee W, MVP
ID: 35125718
Then that's probably your issue.  Your ISP has NO IDEA where to find the authenticating server, but your clients are asking your ISP where to go.  Proper DNS configuration is ESSENTIAL to a working environment.  

Your Server should point ONLY to itself for DNS; your workstations should point ONLY to the server for DNS - no "additional" DNS servers from your ISP (yes, if your server is down, you can't browse the internet - but if your server is down, you have bigger problems).
0
 

Author Comment

by:ls2gto
ID: 35125763
Thanks, but I am a bit confused. I have attached a screenshot of my server's ethernet card network settings if that helps. Currently, I have all of the workstation computer's ethernet adapter DNS settings pointed to the server's IP address of 192.168.1.5, along with a manually assigned IP address that I just setup (it was automatic before).  Am I doing something wrong?  I wasn't sure if I should change the DNS Server settings on the server to 192.168.1.5 as well since that is the IP of the server?



 network settings on server
0
 
LVL 96

Accepted Solution

by:
Lee W, MVP earned 500 total points
ID: 35125791
What you have right now is incorrect and likely the cause of your problems.  Change the DNS Server setting on the TCIP/IP properties of the Network card so that it is 192.168.1.5.  Then set all workstations to ALSO use 192.168.1.5 ONLY

(Frankly, it's not advised to use 192.168.1.x as that can create problems if you try connecting with VPN.  You should be using a number other than 1 or 0 - I typically pick an easy number like part of the address - if my business were at 42 Main Street, then I'd use 192.168.42.x - so long as that third number is greater than 9 and less than 255.  (Otherwise, use the first two digits of your phone number or something)).

0
 

Author Comment

by:ls2gto
ID: 35153294
That did not work, any other suggestions?
0
 
LVL 96

Expert Comment

by:Lee W, MVP
ID: 35153431
Post a screen shot with your current settings from BOTH the server and the workstation.
0
 

Author Comment

by:ls2gto
ID: 35153568
Actually, that did it. I forgot to restart Win2003, and its now all good. Thanks!
0

Featured Post

Resolve Critical IT Incidents Fast

If your data, services or processes become compromised, your organization can suffer damage in just minutes and how fast you communicate during a major IT incident is everything. Learn how to immediately identify incidents & best practices to resolve them quickly and effectively.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Unable to access folder shares on Netapp 1 23
Which Windows settings change when I join a domain? 12 35
GPO denied - but why ? 6 55
Setting up two DCs 4 45
While rebooting windows server 2003 server , it's showing "active directory rebuilding indices please wait" at startup. It took a little while for this process to complete and once we logged on not all the services were started so another reboot is …
Recently, Microsoft released a best-practice guide for securing Active Directory. It's a whopping 300+ pages long. Those of us tasked with securing our company’s databases and systems would, ideally, have time to devote to learning the ins and outs…
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question