![]() ![]() How quickly does any problem computer log in if the network cable is disconnected prior to entering the password? I think it should try to get IP information from the previous DHCP server. You may be able to disconnect the network cable and have it finish its login quickly, then reconnect the cable. I guess my next question would be how do I do an ipconfig if the computer's stuck trying to log in?Ye old chicken and egg problem! I guess my next question would be how do I do an ipconfig if the computer's stuck trying to log in? Are the DNS addresses shown you domain controllers and -nothing- else? Is the address showing for DHCP Server correct? You need to look at the information "ipconfig /all" displays -while- it's broken. If you have a rogue or multiple DHCP servers on your network, the workstation will use the information provided by the first one that responds so in a situation like this, a reboot might cause it to get the proper info. If it was incorrect, could this have been corrected with a reboot? ![]() I checked the DNS Servers and DHCP Server for all the PCs to see if they matched with my own, and all of them seem to have the right IP address. While looking at the results, you can also check that the DHCP server is the one expected. In the results, check that all DNS servers are your domain controllers. It may or may not solve your issue, but until answered, you could be wasting a lot of time and effort.Īt a command prompt on a troubled workstation, type, "ipconfig /all". Sounds like DNS issue to me, but not sure what to do about it.ĭa_Schmoo has asked probably the single most important question. ![]() The current RPC call from Netlogon on \\COMPUTERNAME to \\DOMAINCONTROLLER has been cancelled. Master reboot profile background windows#The session setup to the Windows Domain Controller \\DOMAINCONTROLLER for the domain DOMAINNAME is not responsive. I found this event on all the PC's around the times that they reported it. For security I've replaced the names. If you don't feel like digging into logs and would rather try excluding variables then try the recommendation from chris-fr, rule out an issue with the computer by trying a known working user account on the problem computer or have the problem user login to a known working workstation. GPO events in eventviewer will typically show processing time. You may see that windows is configuring software, processing GPO, having trouble with DNS, or struggling to load the profile. I would take note of the time when beginning the login process and review eventviewer logs with the timestamps matching the time it took for the logon process to complete. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |