Read failed win socket error =10054
Article ID: 39402
Updated On:
Products
Issue/Introduction
Problem:
Running "autoping" from the event processor machine to a newly installed Windows remote agent fails stating "read failed win socket error =10054". Attempts to telnet from the EP machine to the Remote Agent machine also fail. How to fix this problem?
Environment:
Windows
Cause:
There is a communication configuration problem between scheduler and agent box.
Resolution:
In order to find the exact problem additional information is needed.
Try running "auto_remote -x" on the remote agent machine that was getting the read socket error when trying to reply to the autoping from the EP machine. This may help to troubleshoot the problem.
For example, the result of "auto_remote -x" may be that it reports an error stating ntwdblib.dll was missing. This would indicate the need to check for the file's existence or location and copy the file from a different working Windows remote agent if needed.
Also in some cases problem was resolved by installing the application with local administrator's rights.
Additional Information:
Please visit
Environment
Component:
Feedback
