Resolve Some Common Windows Server Errors
| Error | Caused by & Resolution suggestions |
|---|---|
| ERROR_LOGON_FAILURE: Logon failure: unknown user name or bad password. (1326) | Make sure password is correct |
| Make sure the username is in "<domain>\<username>" form. Use ".\username" for a local account | |
| Failed to bind to uuid 4d9f4ab8-7d1c-11cf-861e-0020af6e7c57 - NT_STATUS_NET_WRITE_FAULT ERROR: dcom_create_object. ERROR: Login to remote object. NTSTATUS: NT_STATUS_LOGON_FAILURE - Logon failure |
Passwords are not interpreted properly if they contain “$” or “@” symbol. Try changing the password for the account you are connecting with. |
| Failed to bind to uuid 4d9f4ab8-7d1c-11cf-861e-0020af6e7c57 - NT_STATUS_NET_WRITE_FAULT ERROR: Login to remote object. NTSTATUS: NT_STATUS_ACCESS_DENIED - Access denied |
When you get this error it is generally because you are creating a limited permission user to access WMI datasources. This particular error is caused because your service user did not have access to the server due to the local users group that had been removed from "acces this computer from the network" in User Rights Assignment of the Local Group Policy. Re-Add that permission to the account to fix this. |
| ERROR_NET_WRITE_FAULT: A write fault occurred on the network. (88) | Make sure the username is in "<domain>\<username>" form This message can also appear if the Windows firewall is blocking traffic on the target server, see the entry "Wmi communication failure during connect" |
| Wmi communication failure during connect | Windows firewall is likely blocking traffic on the target server. On the target server, at a command prompt, as an administrator, do this:netsh firewall set service RemoteAdmin enable |
| To Test WMI connectivity | Type this on a different windows machine, at the command prompt:wbemtestClick the "connect" button, replace the text "root\default" with \\servername\root\cimv2fill in the username & password if needed, then click connect If the connection succeeds you'll be taken back to initial window with the buttons now enabled, otherwise an error dialog will popup |
| snmp agent down | Is SNMP installed on the target server? |
| Is the SNMP service started? | |
Windows firewall is likely blocking traffic. On the target server, at a command prompt, as an administrator, do this:netsh firewall add portopening protocol=tcp port=161 name=SNMP_TCP | |
| Failed to connect host {ip} on port 135 - NT_STATUS_CONNECTION_REFUSED | Port 135 being refused by the Windows server means that either a) DCOM has been disabled completely on the box b) a security toolkit (anti-virus, etc.) has shut it down to disable propagation of various worms that exploited old security holes on this port. Double check your DCOM configuration by running dcomcfg.exe on the Windows server in question. See this for more information. |
| Error NT_STATUS_ACCESS_DENIED | A NT_STATUS_ACCESS_DENIED error will be used in case any failure occurs in the final stages of the connection authentication request to a Windows device. This error is usually caused by one of three things: 1. Bad Username 2. Bad Password 3. The account you are using doesn't have permissions to access the WMI section you are trying to access. For more information on WMI Permissions that Zenoss needs, there is a forum thread here. That post, and the following one provide some help with setting up Windows permissions. |
Resolve a Few Less Common Windows Server Errors
| Error | Caused by & Resolution suggestions |
|---|---|
| The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. | Check SNTP config. At the command prompt type:net time /querysntp |
To fix it, at the command prompt type something like this:net time /setsntp:0.pool.ntp.org,1.pool.ntp.org | |
| Windows cannot determine the user or computer name. | DNS on target server likely points to the wrong DNS servers, it must point to the correct domain's DNS servers. A target reboot may be needed |
| This computer was not able to set up a secure session with a domain controller due to the following: There are currently no logon servers available to service the logon request. | DNS on target server likely points to the wrong DNS servers, it must point to the correct domain's DNS servers. A target reboot may be needed |
