• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1937
  • Last Modified:

handshake failed due to an unexpected packet format

Hi,

I have a thick client deployed on a bunch of remote sites, and they all use a central web service (https - the client just default accepts the cert). One site has a proxy and works fine (the software has a proxy config area). Another site has a proxy as well, however on the test machine when they try and login after entering their proxy details, they receive this error;

"The handshake failed due to an unexpected packet format."

Does anyone have any idea? The web service still works for the other remote clients so i think it might be coming from the proxy? Or the proxy is doing something to my traffic before it sends it out? I cannot replicate this error and cannot visit or get a remote login to this particular external site, so its very hard to troubleshoot!!

Any info anyone could give on this would be great!!
0
tsgjsy
Asked:
tsgjsy
  • 2
1 Solution
 
aaronblumCommented:
Not sure if I'll be able to help but listing the proxy server details (like proxy engine and protocol types) might help experts help you.
0
 
tsgjsyAuthor Commented:
Their firewall was blocking HTTPS. thanks for the reply.
0
 
tsgjsyAuthor Commented:
put me in the right direction
0

Featured Post

The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now