NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
ORBI OpenVPN not working with Windows 10 client
I have setup my Orbi for OpenVPN and followed the instructions closely on both the Orbi router side and client side. For Android and iOS devices, Orbi's OpenVPN is working such that a VPN session is established between Orbi and Android/iOS devices and traffic from internal LAN machines are tunneled successfully to Android/iOS devices. However, on Windows 10 client it does not work.
I followed the Orbi's OpenVPN setup instructions closely for Windows 10 where I used the "windows.zip" files downloaded from Orbi's OpenVPN page to setup the OpenVPN Windows client. All instructions are followed including renaming the TAP adapter to NETGEAR-VPN as stated in the instruction.
The problem is see is after after I do "Connect" on OpenVPN Windows app to begin establishing an VPN session, it says tunnel is established but there is no Assigned IP address given. Afterwards, I open a Windows command line session to do "ipconfig" and I see the IP address given by Orbi to "NETGEAR-VPN TAP adapter" is the wrong IP address such that the assigned IP address' subnet is the same subnet as the internal LAN side. This will not work. As a result, no traffic flows between the internal LAN and the Windows 10 client.
As a sanity test, with Android and iOS OpenVPN clients, I see Orbi assigns the correct IP address (which have different subnet as the LAN side) and internal traffic flows successfully between Android/iOS devices and internal LAN machines.
On Windows 10 client, it's running the latest OS with latest updates and I'm using OpenVPN 2.4.8 (the latest). On Orbi, it's running the latest firmware (V2.5.1.8).
Please advise.
- I worked with Netgear tech support a few weeks ago on this. The problem is solved. Apparently, the configuration file was bad on the particular revision of Orbi firmware I was using. I had updated the firmware but not the configuration file. Tech support suggested replacing the Open VPN configuration file. When I did that it started working.
24 Replies
I have Orbi OpenVPN configured on two Orbi's, and can access both from Windows 10. Are you able to observe the Orbi "Attached Devices" web page while performing a test of OpenVPN? If so, how does the Attached Devices describe the VPN client device? On my Orbi's, the default subnet is 192.168.1.1 (the most common), and VPN devices show up with (a) an IP address in 192.168.2.x and a connection type of "vpn".
My test methodology is somewhat tedious. I disconnect my smartphone from WiFi to use the LTE connection, and create a WiFi Hot Spot. Then, I disconnect my Windows 10 machine from Orbi WiFi and connect it to the Hot Spot. Then, open the VPN client. That way, I can get to the Orbi using a wired PC while testing OpenVPN on the laptop.
Hi CrimpOn,
Thanks for you reply. When using an Android/iOS device connect to Orbi OpenVPN via LTE network, I am able to see the connected device listed as "OPENVPN-TUN" (in "Attached Device" web page) and see Orbi assigns an IP address of 192.168.2.2 to device (note: the internal LAN subnet is 192.168.1.X). It works as expected and as you described.
However, with a Windows 10 client, Orbi assigns an IP address of 192.168.1.100 as seen in "Attached Device" web page and I can also see in "Logs" web page under "Administration" a line entry of DHCP IP address 192.168.1.100 assigned to the Windows 10 client . To be clear, the Windows 10 client is connected to LTE network. Made double sure the Windows 10 client is not connected to Orbi's LAN. It's a very basic test. No other OpenVPN client is connected.
As a test, on Windows 10 client I open a command shell to ping Orbi's IP (on LAN side, which is 192.168.1.1), the ping fails (because Orbi OpenVPN assigned the wrong IP address. It should be 192.168.2.2... just like the Android device).
(Note: In my LAN network, I configured Orbi's DHCP Server to have a start IP address of 192.168.1.100 and end IP address of 192.168.1.254. IP address range from 192.168.1.2 to 192.168.1.99 are IP address statically assigned (using the Address Reservation UI).
This issue appears on both Firmware Version 2.5.1.8 and Version 2.3.5.30. I believe this is a firmware bug in Orbi.
To Netgear Orbi team, please advise.
You may want to open a support ticket here and get some help on this:
https://www.netgear.com/support/#
SleeplessInPDX wrote:Hi CrimpOn,
Thanks for you reply. When using an Android/iOS device connect to Orbi OpenVPN via LTE network, I am able to see the connected device listed as "OPENVPN-TUN" (in "Attached Device" web page) and see Orbi assigns an IP address of 192.168.2.2 to device (note: the internal LAN subnet is 192.168.1.X). It works as expected and as you described.
However, with a Windows 10 client, Orbi assigns an IP address of 192.168.1.100 as seen in "Attached Device" web page and I can also see in "Logs" web page under "Administration" a line entry of DHCP IP address 192.168.1.100 assigned to the Windows 10 client . To be clear, the Windows 10 client is connected to LTE network. Made double sure the Windows 10 client is not connected to Orbi's LAN. It's a very basic test. No other OpenVPN client is connected.
As a test, on Windows 10 client I open a command shell to ping Orbi's IP (on LAN side, which is 192.168.1.1), the ping fails (because Orbi OpenVPN assigned the wrong IP address. It should be 192.168.2.2... just like the Android device).
(Note: In my LAN network, I configured Orbi's DHCP Server to have a start IP address of 192.168.1.100 and end IP address of 192.168.1.254. IP address range from 192.168.1.2 to 192.168.1.99 are IP address statically assigned (using the Address Reservation UI).
This issue appears on both Firmware Version 2.5.1.8 and Version 2.3.5.30. I believe this is a firmware bug in Orbi.
To Netgear Orbi team, please advise.
I had the same issue and fought with it for a few days. Turns out the path where I was saving my downloaded unzipped Windows config files per the instructions was not the path my OpenVPN installation defaulted to. Under the Advanced tab in OpenVPN GUI settings, make sure it is pointed to the folder where you dropped the config files. As soon as I fixed that, mine connected right up, I could print, remote desktop, ping, etc. as advertised.
- This is not an OpenVPN issue. I have the installation working fine from a Mac. I also have it work fine on a Windows 10 client going to another Netgear router. The config files are in the same location on the Win 10 computer. When you get ready to connect it gives the option of which location to use. I can see that the Win 10 computer is connected to the Orbi. But I get continuous routing errors.
- In addition, to give you the benefit of the doubt, I tried changing the paths. I tried moving the confit files to my home directory, which is where OpenVPN defaults. No dice.
This is a router issue. That Netgear needs to fix. As an aside, I think routing on the Orbis is broken. I tried setting a route and when I tried doing a tracert on a Windows system in the same subnet as the Orbi it just times out. It doesn’t even make it to the first hop which is in the same subnet. I can do this on a system located in the same subnet as my other Netgear router and it works just fine.Im having the exact same issue, works fine from android but dont get assigned an ip address on windows 10.
