-
1. Re: agentinfo returns cannot access host Connection timed out
Bill RobinsonOct 27, 2016 6:45 AM (in response to Vasileios Michos)
"If we manually restart the Agent there will be no problem but I need to know why this is happening."
->which means the USP works ?
"I am able to ping server as well as telnet to 4750 without any error."
-> you are running these from the appserver? or where?
"I reach my target server from my appserver through SOCKS."
what's in the socks log when you get the timeout ?
what os is the agent? what bsa version ? does this happen on a lot of targets, just one ?
-
2. Re: agentinfo returns cannot access host Connection timed out
Vasileios Michos Oct 27, 2016 7:58 AM (in response to Bill Robinson)yes, the usp works now after we restarted the agent
I ping the target server from my socks.
the socks.log was reset.
the agentinfo is not running for all my servers even these which I can verify, this server is windows
-
3. Re: agentinfo returns cannot access host Connection timed out
Bill RobinsonOct 27, 2016 8:50 AM (in response to Vasileios Michos)
And the version of the rscd ?
-
4. Re: agentinfo returns cannot access host Connection timed out
Vasileios Michos Oct 31, 2016 6:54 AM (in response to Bill Robinson)8.7
-
5. Re: agentinfo returns cannot access host Connection timed out
Bill RobinsonNov 17, 2016 5:51 PM (in response to Vasileios Michos)
so agent info is running from your console or from the appserver itself? if from the console is the nsh client configured to use a nsh proxy ?