Has anyone else found that logins get slower and slower with time for domain logins to stand alone computers with MassHunter 4.6 or WinUV 5.1.3?

Question

After serval months or several different scientists logging in, the login takes up to two minutes. The way we've worked around this is by removing the workstations from the domain and then returning them back to the domain and this shortens the login wait from a quarter to and eighth the login time. Does anyone have a better, more automated solution?

nbauer · Answer

Hi Sabbas, 
 Domain-connected issues can be hard to troubleshoot without a lot of Active Directory information that specific to your company. It sounds like the workstation is attempting to communicate with a Domain Controller that is not responding and the extended login could be the result of the system waiting for the request to timeout. When you removing the workstation from the domain and then rejoin it you force the workstation to start with a fresh set of information. The next time you have the issues I would suggest trying the following: 
 
 Open and Administrative CMD prompt 
 Run the command ipconfig /flushdns 
 Run the command ipconfig /registerdns 
 Seach for "Services" from the Start Menu and launch the program 
 Find the "Netlogon" service and right-click, restart

Has anyone else found that logins get slower and slower with time for domain logins to stand alone computers with MassHunter 4.6 or WinUV 5.1.3?

Top Replies