Clients cannot connect to local LAN
Posted: Thu Oct 12, 2017 9:28 am
Hi all
It's the first time that I want to setup an OpenVPN server on a Windows machine. In the past, I had one running on a RaspPi, which worked, but was lacking performance.
The problem I'm facing at the moment is clients not being able to connect to the local LAN. However, they can connect to the VPN server itself.
I checked the logs, and find some strange behavior: my VPN server has 192.168.1.10 as internal IP address. The next IP, being .11 is my NAS running in the network (which has nothing to do with OpenVPN or any other VPN software). The logs however state the following:
TCP/UDP: Preserving recently used remote address: [AF_INET]192.168.1.11:1294
and a bit below:
UDP link remote: [AF_INET]192.168.1.11:1294
Why is it using my NAS's IP address? I think this might be the cause of the issue.
PS: yes, I've disabled my Windows Firewall
PS2: the external port is 1294, which is "port forwarded" on my router to internal port 192.168.1.10:1194.
It's the first time that I want to setup an OpenVPN server on a Windows machine. In the past, I had one running on a RaspPi, which worked, but was lacking performance.
The problem I'm facing at the moment is clients not being able to connect to the local LAN. However, they can connect to the VPN server itself.
I checked the logs, and find some strange behavior: my VPN server has 192.168.1.10 as internal IP address. The next IP, being .11 is my NAS running in the network (which has nothing to do with OpenVPN or any other VPN software). The logs however state the following:
TCP/UDP: Preserving recently used remote address: [AF_INET]192.168.1.11:1294
and a bit below:
UDP link remote: [AF_INET]192.168.1.11:1294
Why is it using my NAS's IP address? I think this might be the cause of the issue.
PS: yes, I've disabled my Windows Firewall
PS2: the external port is 1294, which is "port forwarded" on my router to internal port 192.168.1.10:1194.