Remote Agent Timeout

I have a remote agent on a satellite Internet conneciton. It has been working for the past year. Today it has stopped working. I can ping the remote agent but the 24x7 scheduler reports a WSAETIMEOUT error on the trace and fails to connect to the remote scheduler. Is there a way to increase the timeout value?

This is most likely is not a timeout issue.

This may be a case where the scheduler loads the winsock.dll, but the Winsock driver fails to load.
Make sure the winsock.dll is in the DOS path. You may also need to free more conventional memory.

Also please check that the agent is up and running and listening for incoming connections. If you have tracing enabled on the agent check master.log for errors like
Initializing Listener. LISTENER FAILED ....

: I have a remote agent on a satellite Internet conneciton. It has been working
: for the past year. Today it has stopped working. I can ping the remote
: agent but the 24x7 scheduler reports a WSAETIMEOUT error on the trace and
: fails to connect to the remote scheduler. Is there a way to increase the
: timeout value?

This is the dump from the Master.Log. How do I repair it?

SMI10 Listener (00FDE360): Start Listening: computerName(), serviceName(63107), driverName(WinSock). ... (00000000)
SMI Property: __DriverName='WinSock'
SMI Property: __ApplicationName='63107'
SMI AddRef SMI_TRACE(00FDE228) refCount(2)
WSD11 AddRef: RefCount for listener object = 1
SMI10 Listener (00FDE360): Start Listening: computerName(), serviceName(63107), driverName(WinSock). SUCCEEDED (00000000)
WSD11 AddRef: RefCount for listener object = 2
WSD11 AddRef: RefCount for listener object = 3
WSD11 AddRef: RefCount for listener object = 4
WSD11 AddRef: RefCount for listener object = 5
DPB30 Listener (00FDE028): Start Listening : application(63107), location(), driver(WinSock). FAILED (80004005)
DPB55 Memory Session : (00000000) count(3366), total(606208), alloc(369685), free(219902)
DPB56 Memory Proc Common : count(1103), total(86016), alloc(62248), free(18464)

: This is most likely is not a timeout issue.

: This may be a case where the scheduler loads the winsock.dll, but the Winsock
: driver fails to load.
: Make sure the winsock.dll is in the DOS path. You may also need to free more
: conventional memory.

: Also please check that the agent is up and running and listening for incoming
: connections. If you have tracing enabled on the agent check master.log for
: errors like
: Initializing Listener. LISTENER FAILED ....

Why is the computerName() empty. Did network services start on that computer?
Dynamic/static IP conflicts? Name conflict?

Try the following check: on the scheduler create a script job
like

Dim result, boolean
PingPort "your agent computer name or IP here", 63107
MessageBox result

: This is the dump from the Master.Log. How do I repair it?

: SMI10 Listener (00FDE360): Start Listening: computerName(),
: serviceName(63107), driverName(WinSock). ... (00000000)
: SMI Property: __DriverName='WinSock'
: SMI Property: __ApplicationName='63107'
: SMI AddRef SMI_TRACE(00FDE228) refCount(2)
: WSD11 AddRef: RefCount for listener object = 1
: SMI10 Listener (00FDE360): Start Listening: computerName(),
: serviceName(63107), driverName(WinSock). SUCCEEDED (00000000)
: WSD11 AddRef: RefCount for listener object = 2
: WSD11 AddRef: RefCount for listener object = 3
: WSD11 AddRef: RefCount for listener object = 4
: WSD11 AddRef: RefCount for listener object = 5
: DPB30 Listener (00FDE028): Start Listening : application(63107), location(),
: driver(WinSock). FAILED (80004005)
: DPB55 Memory Session : (00000000) count(3366), total(606208), alloc(369685),
: free(219902)
: DPB56 Memory Proc Common : count(1103), total(86016), alloc(62248),
: free(18464)