Proxy Handshake error.
Post any question you may have in regards to GoAnywhere Director and let our talented support staff and other users assist you.
2 posts
Page 1 of 1
Hi,
When running a SFTP server test in Director we're getting the following error on some but not all of the sites -
Session.connect: java.io.IOException: Proxy handshake failed with the error: [version=1;type=CONNECT_REPLY;status=CONNECTION_TIMEDOUT;remoteAddress=??.??.??.??:????;localAddress=0.0.0.0:0]
Where ??? is the remote address and port.
This isn't for all SFTP servers as some do work, but the ones that don't have this error.
We're not sure if the problem is with us or the external companies we're trying to connect to so was wondering if anyone has had this issue before and what the resolution was.
Thanks
When running a SFTP server test in Director we're getting the following error on some but not all of the sites -
Session.connect: java.io.IOException: Proxy handshake failed with the error: [version=1;type=CONNECT_REPLY;status=CONNECTION_TIMEDOUT;remoteAddress=??.??.??.??:????;localAddress=0.0.0.0:0]
Where ??? is the remote address and port.
This isn't for all SFTP servers as some do work, but the ones that don't have this error.
We're not sure if the problem is with us or the external companies we're trying to connect to so was wondering if anyone has had this issue before and what the resolution was.
Thanks
- Support Specialist
- Posts: 590
- Joined: Tue Jul 17, 2012 2:12 pm
- Location: Phoenix, AZ
-
Since you are making connections to "some" companies, this usually indicates that there are some routing/connection issues with the ones that aren't.
Have your Trading Partners check firewall rules and/or routing back to your system. Also, make sure your firewall rules are not eliminating the return communication back into your network.
The basic theory is (generally), final handshaking is not taking place for establishing the communication link. The request is being made but not receiving an "answer".
Have your Trading Partners check firewall rules and/or routing back to your system. Also, make sure your firewall rules are not eliminating the return communication back into your network.
The basic theory is (generally), final handshaking is not taking place for establishing the communication link. The request is being made but not receiving an "answer".
Rick Elliott
Lead Solutions Consultant
(402) 944.4242
(800) 949-4696
Lead Solutions Consultant
(402) 944.4242
(800) 949-4696
2 posts
Page 1 of 1