The server where you installed the remote probe does not establish communication with the Server Core, which has an IP address obtained through Dyndns "solutiongate.dyndns-server.com. Firewall ports are enabled and NAT is configured, but the connection is not established, what can I do? I'm trying to send the log of the Remote Probe to your site.
What does error 11004 (socket error) when the remote probe server tries to connect to the Core?
Modified on 2025-06-10 12:03:06 +0200
Disclaimer:
The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.
The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.
The Windows Socket Errors are documented here: http://msdn.microsoft.com/en-us/library/ms740668(v=vs.85).aspx
Your error code, 11004 stands for:
WSANO_DATA
Valid name, no data record of requested type.
The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for. The usual example for this is a host name-to-address translation attempt (using gethostbyname or WSAAsyncGetHostByName) which uses the DNS (Domain Name Server). An MX record is returned but no A record—indicating the host itself exists, but is not directly reachable.
It looks like the dns name for the core server that you entered in the remote probe is not valid.
Jan, 2011 - Permalink