Author Topic: VPN server for interconnecting networks Problem  (Read 1086 times)

renss78

  • Zen Apprentice
  • *
  • Posts: 10
  • Karma: +0/-0
    • View Profile
VPN server for interconnecting networks Problem
« on: January 18, 2016, 03:50:41 pm »
Hello,

I have setup a Zentyal-to-Zentyal Server to connect two networks, but i cannot ping a machine which is behind Site A (the zentyal server).

Site A (datacenter, zentyal 4.2)
Zentyal-to-Zentyal VPN Server --> VPN 192.168.160.1
WAN(eth0) --> External Address
LAN(eth1) --> 10.50.73.1
Windows Server --> 10.50.73.10
Advertised Routes -- > openVPN-eth1-10.50.73.0-24, VPN (192.168.160.x, added manually).

Site B (office, zentyal 4.2)
Is connected to the Zentyal-toZentyal VPN server (as client) which is at the datacenter --> VPN 192.168.160.2
WAN(eth0) -->192.168.1.178 (External Address, it is part of our LAN network, temporary).
LAN(eth1) --> 192.168.180.1
Windows 7 (laptop which is connected with the eth1) --> 192.168.180.12
Advertised Routes -- > openVPN-eth0-192.168.1.0, openVPN-eth0-192.168.180.0, VPN (192.168.160.x, added manually).

--------------------------------------------------------------------------------------------
From the Zentyal (Site B) i can ping 10.50.73.1 (Site A, eth1) and 10.50.73.10(Site A, Windows Server).
From the Laptop (Site B) i can ping 10.50.73.1 (Site A, eth1) but not 10.50.73.10 (Site A, Windows Server)

On the Windows 7 laptop(ip: 192.168.180.12, gw: 192.168.180.1):

When i run a tracert to 10.50.73.1 it goes via

1 --> 192.168.180.1
2 --> 10.50.73.1

When i run a tracert to 10.50.73.10 it goes via

1 --> 192.168.180.1
2 --> 192.168.160.1
3 --> Time-out

Why it goes via the 160.1 when i try to reach 10.50.73.10?? because it does not know the 10.50.73.10 ip but it does know the 10.50.73.x network.. so it just sends out via 160.1.

But why?, please help me out.

ronaldgoode

  • Zen Apprentice
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Re: VPN server for interconnecting networks Problem
« Reply #1 on: January 20, 2016, 10:36:50 am »
This may or may not help, but after about a year of tearing my hair out trying unsuccessfully to connect to an advertised network from a Windows machine, the solution was simply to right click OpenVPN and select "Run as Administrator." Suddenly I was able to connect without issue!

Anyway, if that works, you can right click on OpenVPN, select Properties, go to Compatibility, and select Always run as Administrator so you don't have to right click every time.