Submit a ticketCall us

WebinarFREE IT Monitoring Webcast

Don’t miss out on our webcast, Essential IT Monitoring with SolarWinds ipMonitor, where we will show you how to keep an eye on your IT environment from one centralized, affordable, and lightweight monitoring tool: SolarWinds® ipMonitor®.

Register now.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > NIC and Volumes go into an Unknown state

NIC and Volumes go into an Unknown state

Table of contents
No headers

Updated November 30th, 2016


Issue: On several servers interfaces and disks will go into an Unknown state temporarily.

Description: When the NIC and volumes are unknown, you may see an error similar to the following on the target server:

Log Name:       System
Source:           Microsoft-Windows-Security-Kerberos
Date:              17/05/2010 22:14:47
Event ID:         4
Task Category:  None
Level:             Error
Keywords:        Classic
User:              N/A
Computer:       (Computer Name)
The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server (NAME). The target name used was ldap/NAME. This indicates that the target server failed to decrypt the ticket provided by the client. This can occur when the target server principal name (SPN) is registered on an account other than the account the target service is using. Please ensure that the target SPN is registered on, and only registered on, the account used by the server. This error can also happen when the target service is using a different password for the target service account than what the Kerberos Key Distribution Center (KDC) has for the target service account. Please ensure that the service on the server and the KDC are both updated to use the current password. If the server name is not fully qualified, and the target domain is different from the client domain, check if there are identically named server accounts in these two domains, or use the fully-qualified name to identify the server.

You may also see the same KRB_AP_ERR_MODIFIED error in a wireshark trace.

Cause: This can be caused by incorrect DNS ordering in the TCP/IP properties on the target server. 

Resolution: Ensure the DNS is set up to query the correct server and then run ipconfig/flushdns followed by ipconfig/registerdns.


Last modified