Page 1 of 1

site to site vpn issues

Posted: Sun Sep 07, 2014 2:35 pm
by auntiepattykho
Hi,
I want to connect two offices:

Site 1:
- Softether VPN Server(Installed) have single NIC Card with LAN IP 192.168.0.33
- Created a virutal hub, a user for that hub and Locally bridged to NIC card.

Site 2:
- Softether VPN Server/Bridge(Installed) have single NIC Card with LAN IP 192.168.10.212
- Virtual Hub "BRIDGE" is bridged to the NIC card
- Cascaded connection to VPN Server and connection was established.

I am unable to ping other address from the other subnet from 1 site to the other. I am able to ping the gateway address of site 1 which is 192.168.0.1 but the rest of the ip address in the range it gives a destination unreachable.

Also pinging from site 1 to the site 2 gives a request time out. Can you shed some light on this? Attaching the sample server config.

Re: site to site vpn issues

Posted: Wed Sep 17, 2014 7:53 am
by thisjun

Re: site to site vpn issues

Posted: Thu Sep 25, 2014 7:13 am
by auntiepattykho
Hi thisjun,

Have followed the steps provided but still no go. I am only able to ping the interface which is assigned to the same subnet on the remote site when I do the L3 switching, and it is only from the machine where the bridge /cascade connection was made and not on the entire network. Anything else that I need to do to have this working?

Re: site to site vpn issues

Posted: Thu Oct 09, 2014 5:14 am
by thisjun
Which way did you try?

Re: site to site vpn issues

Posted: Thu Oct 09, 2014 5:39 am
by auntiepattykho
Tried all the 3 methods indicated.

Re: site to site vpn issues

Posted: Thu Oct 16, 2014 8:48 am
by thisjun
Did you do these ways separately?

Re: site to site vpn issues

Posted: Tue Oct 21, 2014 9:04 am
by auntiepattykho
Tried doing this separately and tried doing 1 and 3 separately also but didnt work so I did it the same time but I still could not connect to the other remote clients and servers.

Did not do the number 2 as we need to be on a different subnet.

Re: site to site vpn issues

Posted: Thu Oct 30, 2014 9:04 am
by thisjun
For way No.1, your default gateway may not know route to far site.
Could you confirm your routing table configuration of default gateway router?