Zenoss News
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 | |
| 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 netsh firewall add portopening protocol=udp port=161 name=SNMP_UDP |
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 net stop w32time net start w32time |
|
| 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 |