Forum for all technical support and trouble shooting of the WinGate VPN.
Post a reply

VPN connection is establish, but client can't ping server...

Apr 19 05 3:53 am

VPN connection is establish.
Rip clients installed and running on client & server.
"Send local RIP2 updates" and "Enable RIP2 listener" enabled on both server and client.
I can ping & access to client from server, but I can't ping & access
server from client.
I think, something wrong with routing on client ,
but I can't understand what.
My configuration

192.168.0.134 (mask 255.255.0.0)- Client (my home computer)
WG VPN Client, WinXP Sp2
(Def. gateway & WINS 192.168.0.1)
|
|
192.168.0.1 - Provider's server. I have no access to it.
NAT (Linux based router)
|
|
195.131.. (Static IP ) - (external IP, ADSL Modem Zyxel 630)
192.168.25.25 (Ethernet Netcard) (Internal IP ) -
(Mask 255.255.255.0)
(WG Server , W2Kserver)
Internet Provider tells me that all ports are open on router.
But On client
Routes (Published on server)
192.168.25.25/255.255.255.255 In Conflict
and
192.168.25.0/255.255.255.0 In Conflict
I can't understand why ?
Please help me....

Apr 19 05 8:01 am

The subnet mask you are publishing on the client encapsulates the server's routes. I'd bet if you changed the mask on the client (If possible) to 255.255.255.0 it should work.

This PDF guide to routing should help clear up the hows and whys of WinGate VPN and how routing will affect it.
Post a reply