Hello Andrea,
The "WSAEWOULDBLOCK Return code 10035: Resource temporarily
unavailable" error is returned from operations on nonblocking sockets that
cannot be completed immediately, for example recv when no data is queued
to be read from the socket.
It is a nonfatal error, and the operation should be retried later. It is normal for WSAEWOULDBLOCK to be reported as the result from calling connect on a nonblocking SOCK_STREAM socket,
since some time must elapse for the connection to be established.
In any case, seems to be caused by the configuration of your network,
be it a failure on the DNS server, or a misconfiguration of the 'hosts'
files at your workstations that are connecting to the server, etc.
Can you check if the error is not caused because of a hostname
problem:
124562 Hostname resolution problems (DNS timeouts).
Note 500235 shows how to run NIPING:
"First start the NIPING server on computer A (e.g., the Application
Server) with the command line:
niping -s -I 0 (the last character is zero, not the letter O)
Then start the client (e.g. on the front-end machine) with the command:
niping -c -H <nipingsvr> [ -B <buffersize> -L <loops> -D <delay> ]"
I hope this clarifies the issue for you
http://service.sap.com.sap/support/notes/124562
http://service.sap.com.sap/support/notes/500235
Best Regards,
Jude