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