RDP with Open VPN Gui works. Open VPN Connect doesn't.

JMollema

I have these installed.

I'm using an Untangle Firewall with Open VPN built in.

I'd like to migrate my users to OpenVPN Connect client from the older OpenVPN GUI client.

Everything works fine with OpenVPN GUI, including RDP.

If I close that connection and try OpenVPN Connect, it connects just fine, but when I Open RDP using a computer name, it fails immediately.
If I open it with a computers IP address, the RDP window finds the computer and asks for credentials. When credentials are added, the connection just tries to connect forever. No timeout, but no connection.

What is the difference between these two clients that might be causing this?

TinCanTech

Sounds like gremlins

JMollema

TinCanTech wrote Sounds like gremlins

That's... helpful? Is there a gremlin removal command?

TinCanTech

Yes, use Openvpn-GUI

JMollema

TinCanTech wrote Yes, use Openvpn-GUI

This is not a solution, and I'm still having this issue. Up till now, I've been able to simply keep my users on their OpenVPN Client. Now I have a new user that needs OpenVPN set up.

My Firewall ONLY builds an OpenVPN Connect file for configuration, so I'm forced to resolve this issue.

Is there any hope of finding good advice on this board? I literally have OpenVPN Client and Open VPN Connect on this computer as a test. OpenVPN Client works flawlessly, OpenVPNConnect, connects flawlessly but won't allow any RDP or network mapping.

This has become critical.

Peregrino69

From the sound of it there's at least a name service issue. The client very obviously can't map the DNS name to the IP address. Have you checked out the Untangle site?

https://support.untangle.com/nc/en-us/213527848-OpenVPN-FAQ-

-hth-
PG

Peregrino69

I only now noticed that this forum is "OpenVPN Inc. Enterprise business solutions". To me that reads "customers who pay a ton", which I'm not, and if I'm not mistaken neither are you. I think for us mere mortals the OpenVPN Community client https://openvpn.net/community-downloads/ is the only available solution. I can't say that'd be extremely clear when you click "OpenVPN Client" on the frontpage - didn't occur to me to even check if there are other downloads under Community-tab. I've wasted 2 days myself trying to resolve my issue.

If this is the case, it'd be a very nice gesture from OpenVPN Inc. to clarify the difference. "OpenVPN Connect for Enterprise customers, other users please download the Community client" or something along these lines.