I'm onsite at a client and I've got a really odd situation on one workstation. I came to ES with hope that one of your gurus will once again give me the solution to this quirk.
Scenario:
-Windows XP Pro sp2 workstation with 2 Gig's RAM on a Win2003 Server Domain
-The 2003Server is the DNS server and DHCP server
-When logging in this workstation pauses a bit longer (15 sec) than normal at the Verifying User Name prompt.
-Once past that it hangs for a long time (hours) at the Applying Computer Settings screen.
-When that hang finally completes it gives the Windows Login sound and loads a normal desktop that performs with no noticeable problems. SQL database programs run fine, the internet works fine, I can ping the servers and various internet sites. All seems fine.
-After some troubleshooting I found that when the system is "hanging" at the Applying Computer Settings screen, if I unplug the network cable after about 10 seconds it will complete the login and give me the desktop. I then plug the network cable back in and all works fine.
-Other workstations have no unexpected pauses at login, even when using the same user credentials.
Questions:
-What "network" related process would cause an hours-long pause when applying local computer settings?
-Is DNS the culprit, even though my DNS server is point to the 2003Server exclusively?
Waiting in anticipation,
-Zerm
Heya ES! I have a tech question...
Moderator: Moderators
-
- Posts: 616
- https://www.behance.net/kuchnie-warszawa
- Joined: Fri Jun 07, 2002 4:02 pm
- Location: Arkansas
Using roaming profiles or no? Potential bad profile be it roamed or local. May want to rename the local profile to USERNAME_OLD and let it rebuild with logging back in. Then can copy the necessary stuff over if they have something critical locally. (This would definitly be worth looking at if other users can log into the box no problem and it's just that one person.)
Check the cross connect cables and switch them with a known "good" one. (Both ends, but one at a time.) Pinched wire can cause a collision issue that takes longer than normal to resolve depending on the switch/router.
Can do the classic NIC card switch to eliminate that.
Could also be the DNS setting up in TCP/IP so just do a quick check to make sure all the info is entered correctly and that the domain wasn't mistyped or something.
If you still have issue maybe check the switch/router. Could be an issue and that port may be colliding abnormally. (Only seen this a couple of times on dieing switches, but if you get that far along the line it's worth looking at.)
Check the cross connect cables and switch them with a known "good" one. (Both ends, but one at a time.) Pinched wire can cause a collision issue that takes longer than normal to resolve depending on the switch/router.
Can do the classic NIC card switch to eliminate that.
Could also be the DNS setting up in TCP/IP so just do a quick check to make sure all the info is entered correctly and that the domain wasn't mistyped or something.
If you still have issue maybe check the switch/router. Could be an issue and that port may be colliding abnormally. (Only seen this a couple of times on dieing switches, but if you get that far along the line it's worth looking at.)
- oknagicsar
- Member
- Posts: 490
- Joined: Wed Jul 14, 2004 2:56 am
- Location: Blairsville, PA
When and where is the reunion?
<a href="http://www.magelo.com/eq_view_profile.h ... 0338"><img src="http://www.sdawood.com/Zeremi/zeremiText1.jpg" border="0"></a>