STEPHANK Hi, a long time ago I set up two VPN "servers" on Windows machines that I can reach from my notebooks OpenVPN client. Both worked fine and I used them to route traffic through them. One of them I use every day. The other I have not been using in a very long time. Now I need that one urgently. I can connect and reach the server itself via OpenVPN without a problem. But I cannot route traffic through the server. Connection times out. I have been comparing the two setups, but I can not find the difference. Both "servers" have been upgraded to Windows 10 in the meantime. It could be that this stopped the routing on one of them. I vaguely remember that I had to execute something on the command line to make the routing work. I searched around, but I could not find it. The is the config file, but it is almost identical to the one that works: port 1194 #change to any port you see fit. The client needs to use the same port proto udp #switch to tcp if you wish to use a tcp connection, the client needs to use the same protocol. udp gives better performance dev tun dev-node "OpenVPN" #name of your TAP interface. #server 192.168.1.105 255.255.255.0 #This may need server 10.8.0.0 255.255.255.0 push "route 192.168.1.0 255.255.255.0" ca ca.crt cert server.crt key server.key # This file should be kept secret dh dh4096.pem #ifconfig-pool-persist ipp.txt push "redirect-gateway def1 bypass-dhcp" #tells all Internet traffic to go through the tunnel push "dhcp-option DNS 8.8.8.8" #OpenDNS servers, makes it easy to check if the tunnel is working properly push "dhcp-option DNS 8.8.4.4" keepalive 10 120 comp-lzo #compression for better network performance. Disable if your server isn't powerful enough. Needs to be included in both server and client configs if you use it. persist-key persist-tun status c:\\openvpn\\openvpn-status.log.txt verb 3 Thanks for your help!
STEPHANK Just to clarify: The "server" has the IP 192.168.1.105. I can ping that IP. (I am on a different net.) But I can not ping 192.168.1.1. If I log into the remote machine, I can ping 192.168.1.1.
STEPHANK STEPHANK wroteI vaguely remember that I had to execute something on the command line to make the routing work. HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\IPEnableRouter is set to 1. On both servers. Running out of ideas.
STEPHANK Solved. The router needed a route to the gateway server. For some unknown reason, the other router does not need it. I guess they handle NAT differently.
