Windows 10: How to use OpenVPN client on Windows?

I have an OpenVPN server running on my router and am trying to set up OpenVPN on a laptop so I can access computers and NAS drives on my LAN when traveling. I had very little trouble getting software installed and configured enough to get a VPN tunnel to my router. But I've had next to no luck figuring out how to actually use it.

When in it's "remote" configuration, my laptop is using a tethered mobile phone as a "modem". It appears as an Ethernet NDIS interface. OpenVPN provides and uses a TAP/TUN driver (tap-windows6 driver 9.24.2). And BTW, I really don't understand anything I said in that sentence. The important thing, I think, is that I've got 2 active network adapters - both virtual. One is supporting my internet connection and provides the IP default gateway 192.168.0.1. The other is the VPN tunnel endpoint and, in my configuration, uses IP subnet 10.8.0.0. The router at the other end of the tunnel uses subnet 192.168.1.0. The router itself is 192.168.1.1.

Fine so far. I can ping devices on my LAN (that don't have firewalls blocking pings). I can reach the HTTP servers on the NAS devices via their IP addresses.

I cannot access anything on the LAN by name; no DSN queries get forwarded to the router. Unfortunately, I access everything on my LAN by name. I don't know if this is a problem with the way I have OpenVPN configured, or is due to Windows' not knowing how to handle the 2 network interfaces.

I also cannot bring up Remote Desktop connections with the computers on the LAN. I've seen many web articles indicating RDP across VPN is possible so I know I'm not trying the impossible. Some articles mention firewalls getting in the way, but since my VPN tunnel is to my router rather than the remote Windows I don't think that is the problem ... at the server end. But I have no idea what the TAP/TUN adapter looks like on the client side. I don't see options for Public/Private settings, etc.

Anyone have any experience setting up a configuration like this?

I don't know if it matters, but I'm running Win10 1903.

:)

 

OpenVPN client change hostname resolving in Windows 2003 Server

I have OpenVPN client at Windows server 2003 and OpenVPN works right. Also I have 1C service there. Also I have stopped and have deleted Routing and Remote Access Role for Windows server 2003 (and Server was rebooted of course).

So here is a problem: When my OpenVPN client have started - my servername's name server.company.local resolved
10.8.8.105 instead of normal 192.168.34.10. As result the access to my 1C service stops. How to solve it?

 

Why Does Windows 10 Not Natively Support OpenVPN?

The OpenVPN license:

OpenVPN Access Server End User License Agreement | OpenVPN

seems to be for the server software (and it might just be for their specific implementation of it). I'm wondering about Windows natively supporting our communicating with our own (or commercial) OpenVPN servers. IOW, an OpenVPN client. Not a server.
Things like OpenVPN for Android (free software) surely can't be paying OpenVPN for every copy of that software.

 

OpenVPN Server / Internet Connection Sharing / Routing / IPV6


I'm trying to get an openvpn server running on windows 10 (pro), version 1607. It's working for ipv4, but not ipv6. I'm specifically trying to get it working with ipv4 and ipv6 to test for a problem with openvpn. I'm testing with ipv6-test.com and test-ipv6.com. The client and the server are connecting and both ipv4 and ipv6 are working between the client and the server (the client can ping server), but I can't get any ipv6 traffic to pass through the server.

I'm wondering about internet connection sharing. There don't appear to be any specific ICS settings that relate to this issue. Alternatively, it could be routing.

Any suggestions?