Rayza Posted July 25, 2005 Posted July 25, 2005 I've recently added a win2k(new installation) with SP4 onto a domain. After restarting and completing the username and password it takes the pc ages (like 20mins) to login. If you unplug the network cable it will login to windows straight away. I've had this problem on an XP pc once before but after about a week it returned to normal. Anyone got any bright ideas??
Martin Zugec Posted July 25, 2005 Posted July 25, 2005 Anything in event log?Any problems with DNS? Try to disable dynamic DNS registration, just to see effect...
Rayza Posted July 25, 2005 Author Posted July 25, 2005 I wondered if it had anything to do with DNS settings. I disabled the DNS registration, but that didn't change anything. Going to try a few other changes in the DNS settings window...
RogueSpear Posted July 25, 2005 Posted July 25, 2005 I've had this happen a few different times to me and it almost always boils down to a failure to authenticate to the domain which will make something wait for a timeout.The one that gave me the most grief ever involved laptops using a RealTek NIC. The short story is that drivers from RealTek for their NICs do not initialize in time for the machine to authenticate itself to the domain. So in my case the delay was the computer trying to find and run a machine startup script as defined in a GPO. Actually the entire process of attempting to process the GPO is riddled with timeouts. If your machine properly gets a DHCP lease and is otherwise on the network, just not authenticating, it will have to go through all of these different timeouts because the OS sees that it's network connected. If you pull the CAT5 cable, it knows that it's offline and will behave as such.BTW if you are having difficulties with a RealTek NIC like I described, the solution is to use the MS supplied drivers. Never could understand that one... good luck.
Rayza Posted July 25, 2005 Author Posted July 25, 2005 The NIC is an Intel Pro100 VE, so i dont think it should the NIC. I looked at the name of the server which is "server1a.local.*.com" *=name of company. I was wondering if that was causing the DNS lookup to search the net first when its trying to logon to the domain?? It looks like i'm going to have to wait a week until it sorts itself out....
RogueSpear Posted July 25, 2005 Posted July 25, 2005 It sounds as though you have other clients logging into the domain without any problems? If so, consider the following:- Are the successful computers in the same OU and using the same GPOs?- Are they all hitting the same DHCP server and getting the same settings? Same DHCP scope?- Are you using the latest Intel NIC drivers? Some of the newer Pro100/1000 NICs really seem to benefit and sometimes require the latest drivers.- Check the domain controller's event log to see if there are any events describing a failed login attempt.
chilifrei64 Posted July 25, 2005 Posted July 25, 2005 Make sure your primary DNS Server is an Active Directory DNS Server for your network.. If it isn't It will spend a lot of time looking for your domain name and will be unsuccessful
Rayza Posted July 26, 2005 Author Posted July 26, 2005 The server has 2 NIC's - 1 conected to the ISP with the DNS settings pointing to the ISP's DNS servers. The other NIC is joined to the network but has the same DNS settings as the ISP NIC. Is this where the problem is starting? Should i change the DNS settings on the LAN NIC?
jcarle Posted July 26, 2005 Posted July 26, 2005 If the problem fixes itself over time, I'm convinced you have a DNS issue. If you do have a DNS conflict or misconfiguration, then the problem may appear to seem to fix itself over time as DNS entries become cached.Try setting the DNS entry on your machine to the local Active Directory server. Also make sure that the server's DNS is properly setup to forward requests outside of the domain to your ISP.On your server, the NIC that is connected to your ISP should have your ISP's DNS. However, the NIC that is connected to your LAN should have your LAN's DNS entry.
Rayza Posted July 26, 2005 Author Posted July 26, 2005 On your server, the NIC that is connected to your ISP should have your ISP's DNS. However, the NIC that is connected to your LAN should have your LAN's DNS entry.<{POST_SNAPBACK}>So are you saying the LAN nic should point to itself in the DNS entry?I tried using updated drivers which didn't change anything, so i too am convinced its DNS problems...
Rayza Posted July 26, 2005 Author Posted July 26, 2005 FINALLY!!!!!I added the server's IP address as the primary DNS address on the PC and it now logs on straight away. Thanks for all your help guys...
jcarle Posted July 26, 2005 Posted July 26, 2005 On your server, the NIC that is connected to your ISP should have your ISP's DNS. However, the NIC that is connected to your LAN should have your LAN's DNS entry.So are you saying the LAN nic should point to itself in the DNS entry?I tried using updated drivers which didn't change anything, so i too am convinced its DNS problems...Yes because the LAN NIC cannot access outside of the LAN directly, so it has to resolve using the DNS of your Active Domain. If you leave the DNS to your ISP's DNS, then when you resolve a local host, you will be sent to your ISP's DNS which will send you back to your local Active Domain instead of going there right off the bat.
chilifrei64 Posted July 26, 2005 Posted July 26, 2005 (edited) Yes.. ISP NIC.. ISP DNS ServerLAN NIC.. LAN DNS ServerEDIT: Scratch me.. i should of read the last page.. But yeah.. what jcarle said is 100% true.. that was the problem Edited July 26, 2005 by chilifrei64
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now