GetHostByName / The socket could not be constructed / WSAError / Name resolution

GetHostByName / The socket could not be constructed / WSAError / Name resolution

If you find Diagnosis Log messages like
WINSOCK ERROR--GetHostByName Failed Server
or Windows Event Log messages like
The socket could not be constructed! Host/IP/Adapter: WSAError:
make sure the computer name is not longer than 15 characters.
Verify if the characters qualify for ALL Windows name resolution methods:

WSAError numbers are listed in the Winsock documentation:

Adding the hostname in it's short and it's FQDN form to the hosts file (C:\Windows\System32\drivers\etc\hosts) eventually solves name resolution issues.
Depending on the name resolution system, try using the hostname in it's short or in it's FQDN form as zenon server name.
In Smart (Web) Client configurations, write names in UPPERCASE.

Use PowerShell to test the name based reachability of zenon services.
The following example probes if the host computer TESTPC listens on Port 1102 (Smart Server):
Test-NetConnection -ComputerName TESTPC -Port 1102

    • Related Articles

    • IEC61850 Server opens TCP socket without activating KEEPALIVE

      Summary On some devices, e.g. Windows CE, the IEC61850 Server I/O driver in zenon Logic does not activate KeepAlive by opening the TCP-socket. Thus after connection loss the socket stays open. Description On some devices, e.g. Windows CE, the ...

    • "fetch lot name from the variable at start" sometimes does not work

      Description In Batch Control, when configured to fetch the lot name from a variable at start, the lot name is to be taken from the variable that triggered the start. In some cases the lot name is not taken over. This can happen with "Start archive" ...

    • zenLogSrv: no TCP keep alive for listening socket

      Description The TCP server of zenLogSrv.exe did not send TCP keep alive messages to check if the TCP connection is still available. The issue has been addressed by automatically enabling TCP server now automatically enables the TCP keep alive for the ...

    • Remote-Transport: no TCP keep alive for listening socket

      Description The TCP server of process zensysSrv (used for remote transport) did not send TCP keep alive messages to check if the TCP connection is still available. The issue has been addressed by automatically enabling TCP keep alive for the ...

    • S7TIA: Variables cannot be imported from TIA project when CPU name contains dots (.)

      Summary All Version do not resolve dots (.) as part of CPU-name properly. This leads to problem with importing variables from TIA-projects or pre-compiled projects. With the current bugfix CPU-names containing dots are quoted to recognise it and to ...