S
___Sam___
Hi,
*** Please see updated issue description post from Tuesday, September 11, 2018 9:14 PM ****
Several of our windows 2012 R2 servers, virtual and physical servers have been having issues with network connectivity.
We get alerts that the sql service is unreachable.
RDP login screen is reached, but hangs on authentication (welcome).
Server was pingable by IP and could ping out.
NSLookup works.
Pinging a name doesn't work.
DNS entry for the server is removed from DNS server when we left one in this state overnight. One has been down for 3 hours and DNS record is still there.
Restarting the server fixes the issue. Logging on with local account and disabling/enabling NIC using netsh fixes the issues. Killing the DNS Client Service fixes the issue.
This is only happening on servers with SQL Server installed. Seems to have started August 9-12th on a couple test machines and has now happened on some clusters over the weekend.
Any ideas?
Here are some log entries of note.
Message
Event ID
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the CryptSvc service. (This is the first entry - nothing before this that seems relevant)
7011
The session setup to the Windows NT or Windows 2000 Domain Controller foo for the domain DOMAIN is not responsive. The current RPC call from Netlogon on SERVER TO DC has been cancelled.
5783
Netlogon has failed an authentication request of account Websense in domain DOMAIN. The request timed out before it could be sent to domain controller DC in domain DOMAIN. This is the first failure. If the problem continues, consolidated events will be logged about every 30 minutes. Please see http://support.microsoft.com/kb/2654097 for more information.
5816
Netlogon has failed an additional 23 authentication requests in the last 30 minutes. The requests timed out before they could be sent to domain controller DC in domain DOMAIN. Please see http://support.microsoft.com/kb/2654097 for more information.
5817
DCOM was unable to communicate with the computer COMPUTER using any of the configured protocols; requested by PID 2390 (C:\windows\system32\ServerManager.exe).
10028
Continue reading...
*** Please see updated issue description post from Tuesday, September 11, 2018 9:14 PM ****
Several of our windows 2012 R2 servers, virtual and physical servers have been having issues with network connectivity.
We get alerts that the sql service is unreachable.
RDP login screen is reached, but hangs on authentication (welcome).
Server was pingable by IP and could ping out.
NSLookup works.
Pinging a name doesn't work.
DNS entry for the server is removed from DNS server when we left one in this state overnight. One has been down for 3 hours and DNS record is still there.
Restarting the server fixes the issue. Logging on with local account and disabling/enabling NIC using netsh fixes the issues. Killing the DNS Client Service fixes the issue.
This is only happening on servers with SQL Server installed. Seems to have started August 9-12th on a couple test machines and has now happened on some clusters over the weekend.
Any ideas?
Here are some log entries of note.
Message
Event ID
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the CryptSvc service. (This is the first entry - nothing before this that seems relevant)
7011
The session setup to the Windows NT or Windows 2000 Domain Controller foo for the domain DOMAIN is not responsive. The current RPC call from Netlogon on SERVER TO DC has been cancelled.
5783
Netlogon has failed an authentication request of account Websense in domain DOMAIN. The request timed out before it could be sent to domain controller DC in domain DOMAIN. This is the first failure. If the problem continues, consolidated events will be logged about every 30 minutes. Please see http://support.microsoft.com/kb/2654097 for more information.
5816
Netlogon has failed an additional 23 authentication requests in the last 30 minutes. The requests timed out before they could be sent to domain controller DC in domain DOMAIN. Please see http://support.microsoft.com/kb/2654097 for more information.
5817
DCOM was unable to communicate with the computer COMPUTER using any of the configured protocols; requested by PID 2390 (C:\windows\system32\ServerManager.exe).
10028
Continue reading...