Author Topic: Unable to complete TLS handshake inside public network (OpenVPN)  (Read 916 times)

0 Members and 1 Guest are viewing this topic.

Offline DMiller657

  • NULL
  • Posts: 4
  • Cookies: 0
    • View Profile
Unable to complete TLS handshake inside public network (OpenVPN)
« on: December 03, 2015, 11:14:19 pm »
To give you guys a little bit of background as to why I am asking this question...

I am trying to create a VPN tunnel between my system and an external VPN Server. This this case I am using OpenVPN. I am sitting on a public network in a public building. The connection always fails with the error that it cannot complete the TLS handshake. As I'm sure some people will have figured out just by reading what I have put so far, the packets from the client are being blocked somewhere along the network and I'm therefore it cannot complete the authentication process. I am able to connect to this external server via putty (from within this network) and so I can change the configuration of the external server if necessary. The sever is currently accepting connections of port 443.

My question to you guys is, how can I find out where in the network the packets are being either dropped, filtered out, rejected or blocked?

 I know that this network has multiple switches and firewalls, and so to try and find a way around the problem it would help me a lot to know which device is blocking the connection. I've tried connecting using both UDP and TCP and both fail.

Thanks,
Dan

Offline _Enigma

  • Serf
  • *
  • Posts: 27
  • Cookies: 3
    • View Profile
Re: Unable to complete TLS handshake inside public network (OpenVPN)
« Reply #1 on: December 03, 2015, 11:45:13 pm »
Have you tried running wireshark to see if thatll shed some light in how the conversation goes specifically? Also when you connect with putty what port are you using (assuming 22)?

Offline 0E 800

  • Not a VIP
  • VIP
  • Baron
  • *
  • Posts: 895
  • Cookies: 131
  • • тнε ιηтεяηεт ιs мү яεcүcℓε-вιη •
    • View Profile
Re: Unable to complete TLS handshake inside public network (OpenVPN)
« Reply #2 on: December 03, 2015, 11:55:27 pm »
Pretty sure server side needs have the openvpn default port of 1194 UDP open.

Do a port scan on your remote server to see what ports are open. You used putty so we know 22 is probably open.

Server side might also have hardware firewall or local OS firewall blocking too.
The invariable mark of wisdom is to see the miraculous in the common.

Offline _Enigma

  • Serf
  • *
  • Posts: 27
  • Cookies: 3
    • View Profile
Re: Unable to complete TLS handshake inside public network (OpenVPN)
« Reply #3 on: December 03, 2015, 11:59:50 pm »
Pretty sure server side needs have the openvpn default port of 1194 UDP open.

Do a port scan on your remote server to see what ports are open. You used putty so we know 22 is probably open.

This might sound silly, but I remember using an ssh tunnel to pivot a remote desktop connection through another machine. Could he tunnel his openvpn connection through port 22 if its not getting blocked, and the firewall on the remote server can redirect traffic from 22 to whatever port openvpn intended to use?

Offline 0E 800

  • Not a VIP
  • VIP
  • Baron
  • *
  • Posts: 895
  • Cookies: 131
  • • тнε ιηтεяηεт ιs мү яεcүcℓε-вιη •
    • View Profile
Re: Unable to complete TLS handshake inside public network (OpenVPN)
« Reply #4 on: December 04, 2015, 12:29:20 am »
Review: http://superuser.com/questions/822161/openvpn-wont-connect-from-remote-location

Think its the same issue OP has.

If u use a different port on the server side, then you'll
need to force it by adding these two lines to your client/server
config files:

Code: [Select]
proto udp
port 1194

Change them to what u want them to be.
« Last Edit: December 04, 2015, 12:32:04 am by 0E 800 »
The invariable mark of wisdom is to see the miraculous in the common.

Offline DMiller657

  • NULL
  • Posts: 4
  • Cookies: 0
    • View Profile
Re: Unable to complete TLS handshake inside public network (OpenVPN)
« Reply #5 on: December 04, 2015, 07:40:26 am »
Sorry, I probably should have mentioned this at the start. When I connect to the VPN server from a private network (eg: my home) then it connects and works perfectly, it's only when connected to this public network that it doesn't work - hence how I know that the issue is not server side (connects fine on 443).

This might sound silly, but I remember using an ssh tunnel to pivot a remote desktop connection through another machine. Could he tunnel his openvpn connection through port 22 if its not getting blocked, and the firewall on the remote server can redirect traffic from 22 to whatever port openvpn intended to use?

I will look into pivoting through ssh...
« Last Edit: December 04, 2015, 07:41:29 am by DMiller657 »