I have a client who has OpenVPN installed on a windows server. I didn't install it and the person who did is no longer available. The server runs a special App and the client machines talk to it - and it alone, no routing to other machines.
I have a problem where some internal subnets can access the OpenVpn server and others cannot.
The setup:
- Openvpn uses 10.8.0.0 - the default setup.
- The server is on 192.168.2.10
- Internal subnets 192.168.1.0 and 192.168.40.0 are connected by routers.
- Pc's which are on 192.168.2.0 and 192.168.1.0 can access the server running openvpn without problems (remember, they're internal and they don't connect via openVPN).
- PC's which are on the 192.168.40.0 subnet CANNOT ACCESS (they're internal and also don't connect via openVPN).
- Win 2003 R2 + OpenVPN 2.1.3
If I shut down OpenVPN on the server I can access the server from 192.168.40.0
So, my problem is that OpenVPN is rejecting connections from 192.168.40.0 to 192.168.2.10 but I can't see why. By access I mean I can't open remote desktop to manage the box... or any other socket.
Adding routes in the OpenVPN config doesn't see to make ay difference ... and I didn't expect it to.
What really mystifies me is why 192.168.1.0 can get to the server... but there is no mention of it in the OpenVpn config file.
Anyone got any suggestions?
This is the server.ovpn file, edited to remove comments. As you can see its almost the default config.
port 1194
proto udp
dev tap
ca ca.crt
cert Server.crt
key Server.key # This file should be kept secret
dh dh1024.pem
server 10.8.0.0 255.255.255.0
ifconfig-pool-persist ipp.txt
push "route 192.168.2.0 255.255.255.0"
# this was added by me but had no effect on my problem.
push "route 192.168.40.0 255.255.255.0"
client-config-dir ccd
# this was added by me but had no effect on my problem.
route 192.168.40.0 255.255.255.0
client-to-client
keepalive 10 120
comp-lzo
max-clients 100
persist-key
persist-tun
status openvpn-status.log
verb 4
