Active tunnel but cant ping server

[Paulferrari]

Gateway machine is the VPN server connected to the web on IP address 217.xx.50.xxx. Local IP 10.100.3.250

Client connects to VPN server and establishes active tunnel. GAtekeeper can see the gateway machine (VPN server) and all of the network work stations but they are all marked not acessible.

Client machine allocated 193.113.235.169 by isp (this is the ip address seen by the server when the client connects).

Both machines using wingate firewall ONLY with hole for port 809 TCP and UDP

Published routes showing on server
Published routes on local network of server:
10.100.3.0/255.255.255.0
10.100.3.25/255.255.255.255
217.xx.50.xxx/255.255.255.255

Published routes on local network of client:
10.226.159.190/255.255.255.255
10.255.255.255/255.255.255.255

Published routes showing on client
Published routes on local network of server[MASTER]:
10.100.3.0/255.255.255.0
10.100.3.25/255.255.255.255
217.xx.50.xxx/255.255.255.255

Published routes on local network of client[LOCAL]:
10.226.159.190/255.255.255.255
10.255.255.255/255.255.255.255

Can you tell me what is wrong and how I can access the server please?

[genie]

Can you ping Wingate server itself over VPN when the tunnel is established?

[Paulferrari]

When the tunnel is established i can see the VPN server in the list of machines on the network. the properties of that machine report its IP address correctly as 10.100.3.250 but pings to that address time out.

I can successfully ping the VPN server from any workstation on the network but not from the client connected by VPN.

[genie]

Paul, we have the new driver that might help in your situation - basically it solves the problem when there is a NATing router in fron the Wingate VPN server - is it your case? Let me know if you want to try this new driver - I will need your OS type on both sides on the VPN tunnel.

[Paulferrari]

The VPN server is connected directly to a basic ADSL modem which doesn't have NAT.

The client machine is behind a NAT router though.

I'll gladly try the new driver if you think it will solve the problem. Both server and client are using Windows XP pro SP2 with all updates installed.

[genie]

Paul, the new driver is on its way.

[sduffey]

Paul, the new driver is on its way.

Could you please send me the driver as well? I have identical issues where I can attach to the remote VPN server but can not ping or browse. The server is running Win2k, the client is XP SP2. I am running 2.04. Thanks!

Perhaps a patch section of the site could be created so we can download these sort of fixes quickly?

[genie]

Drivers have been sent to you.

[Paulferrari]

Thank you for the drivers.

The problem was actually a firewall issue on the router the client PC was behind. The router was reporting that port 809 TCP and UDP were open but I coukd not connect, yet when I disabled the firewall I connected straight into the server.

I spent a lot of time trying to find an issue which could have been solved by the quick test of disabling the firewall, so my advice is try this first if you have problems connecting.

[genie]

Thanks for the information, Paul.