4 Replies Latest reply on Feb 17, 2014 3:36 AM by Pierre Nicoletta Branched from an earlier discussion.

    Re: NSH Here failing to connect to servers behind Socks Proxy

      Hi Joshua & Bill,

       

      I have issues with Socks Proxy. The goal is to use the /etc/hosts of the proxy to resolve the target name.

       

      The sockd.conf is good, the proxy and associated rules are added on Bladelogic and I can see traffic incoming on the proxy port when I do "agentinfo" from the APPserv, or even if I connect by nsh.

       

      Still, when I try to add a server known only by the Socks Proxy, I've got the following error in my sockd.log file :

       

      Feb  6 11:56:38 (1391684198.825991) sockd[14190]: info: pass(1): tcp/accept [: appservIP.port proxyIP.proxy_port

      Feb  6 11:56:59 (1391684219.934389) sockd[14185]: info: pass(1): tcp/connect ]: 0 -> username%xxxxx@appservIP.port proxyIP.proxy_port-> 0, 0 -> proxyIP.proxy_port targetIP.4750-> 0: remote peer error (Connection timed out).  Session duration: 21s

      Feb  6 11:56:59 (1391684219.934460) sockd[14185]: info: pass(1): tcp/accept ]: 0 -> appservIP.port proxyIP.proxy_port -> 0: remote peer error (Connection timed out).  Session duration: 21s

       

      Note : I replaced real IP addresses and port numbers by "appservIP/proxyIP/targetIP" and  "port/proxy_port" because of security reasons.

       

      It seems the socks proxy does not access to the target agent, even if the rscd agent is running on the target and is listening on rscd port :

      [root@proxy_name~]# telnet target_name 4750

      Trying target_IP...

      Connected to target_name.

      Escape character is '^]'.

       

      Any idea to resolve that issue would be great.

       

      Thanks, and best regards,