Hi dude!
The described error message WSAEWOULDBLOCK (return code 10035) is returned from operations on nonblocking sockets that cannot be completed immediately, for example recv when no data is queue to be read from the socket. It is a nonfatal error, and the operation should be retried later.
It is normal that a WSAEWOULDBLOCK is reported as the result from calling connect on a nonblocking SOCK_STREAM socket, since some time must elapse for the connection to be established.
It might be caused by the configuration of your network, be the root cause a failure on the DNS server, a misconfiguration of the 'hosts' files at your workstations that are connecting to the server, etc.
You should first check that the error is not caused because of a hostname problem as per [note 124562|https://service.sap.com/sap/support/notes/124562].
Also, [note 500235|https://service.sap.com/sap/support/notes/500235] shows how to run NIPING:
...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> ]
This would let you know not just if you can solve the address, but if there are stability problems later on.
Cheers!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.