Winsock Error 11001

Hi RotzlerIT,

I recommend setting this value in the registry:

HKEY_LOCAL_MACHINEsoftwareWow6432NodePowerAdminServerMonitor

Ping_DoDiagnosticPing = 1

With this set, any time a host fails ping.exe (same one you and I run) will get run to also try to ping the host and it's output will be logged. That will either refute or corroborate what the Ping Monitor is reporting. So far we're seeing the Ping Monitor is correct and detecting some DNS hiccups.

If you see this again please zip up and send the log files so we can review them. To send the files open the Console and go to Settings -> System Settings and click on the FTP logs to Support.

Thanks
Quinn

Please make sure to mark your questions accepted when you have your answer by clicking the gray check mark to the left of the answer.

Hi RotzlerIT,

It looks like this was indeed DNS related.

After you enabled the Ping_DoDiagnosticPing registry value the service would run Window's ping.exe and capture it's output when the Ping Monitor went into error and couldn't get a response. When the Ping Monitor went into alert at 1:25 am the service ran the ping.exe and this is what was returned:

04-11-2019, 01:25:13.207, TID:00304, PID:01624, [TID:03936] Output from ["C:Windowssystem32ping.exe" -n 3 -4 notessrv04]: Ping request could not find host "notessrv04". Check the name and try again.

(The text above was translated from the actual log file language of German to English.)

Between 1:25 and 1:40 am this happened for many different servers (you can search the log for "C:Windowssystem32ping.exe")

Thanks
Quinn

Please make sure to mark your questions accepted when you have your answer by clicking the gray check mark to the left of the answer.

Hi RotzlerIT/Quinn,

I experience the same issue. In the last few months i saw this error message a few time a week, but since upgrading to version 8 (actually 8.0.1.18) i see this error message a few times a day, making it irritating.

I have also set the Ping_DoDiagnosticPing = 1 registry key, and when PA Server Monitor was alerting i was able to reproduce the issue on the command prompt on the specific satelite/monitoring server. i noticed I only could reproduce the issue using ping -4 to a hostname, if I use the ping without -4 or iuse the FQN (fully qualified hostname) resolving works fine, for example :

C:\Users>"C:\Windows\system32\ping.exe" -n 3 -4 server04
Ping request could not find host server04. Please check the name and try again.

C:\Users>"C:\Windows\system32\ping.exe" -n 3 server04

Pinging server04.amsprod1.reeleezee.nl [10.194.32.160] with 32 bytes of data:
Reply from 10.194.32.160: bytes=32 time<1ms TTL=127
Reply from 10.194.32.160: bytes=32 time<1ms TTL=127
Reply from 10.194.32.160: bytes=32 time<1ms TTL=127
Reply from 10.194.32.160: bytes=32 time<1ms TTL=127

Ping statistics for 10.194.32.160:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Users>"C:\Windows\system32\ping.exe" -n 3 -4 server04.amsprod1.reeleezee.nl

Pinging server04.amsprod1.reeleezee.nl [10.194.32.160] with 32 bytes of data:
Reply from 10.194.32.160: bytes=32 time=4ms TTL=127
Reply from 10.194.32.160: bytes=32 time<1ms TTL=127
Reply from 10.194.32.160: bytes=32 time<1ms TTL=127

Ping statistics for 10.194.32.160:
    Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 4ms, Average = 1ms

What I learned until now - This issue only seems to occour on specific target hosts ( in my case 8 different hosts) - this seems occour with the -4 parameter in the ping commandline - I have only seen this on hosts using hostname only (not FQN)

any clue ho to fix this ? is there a easy way to teplace the hostname with the FQN for an existing target?

Kind Regards, Tom

Hi TomRLZ,

There is a registry value that will allow you to change the name of the server/device in your console. If you change the value for "AllowRenameServer" to 1 (DefaultVal = 0) then you will be able to change the name.

Location: HKEY_LOCAL_MACHINESOFTWAREPAServerMonitor

Thanks
Quinn

Please make sure to mark your questions accepted when you have your answer by clicking the gray check mark to the left of the answer.

Hi Quin, I have renamed all targets showing this errors to a FQN (Fully qualified hostname). For the previous 2 hour I have not seen any of these messages so for now it looks like using FQN is a good workaround.

the strange thing that a lot of other targets work fine with just using a hostname.

@Cedric: does using fully qualified hostnames work for you also?

Kind regards, Tom

Having the same problem.. Even when adding devices by IP. Version 8.0.0.434