WinGate VPN and Woosh

[rbaal]

Network description

Head office Wingate VPN Server on 2000 pro version 5.something, normal IP connection via firewall.

Outstation Wingate Version 5/6.03 Woosh 256K Radio service both VPN and WinGate proxy installed.

Was working fine then changed from JetStream to Woosh. Proxy functionality still working. VPN says it is active and shows the other nodes in the VPN network, shows routes , look fine BUT does not work. You can't ping the VPN server let alone the internal network. Now I know that regarding the internal network I need to run RIP because I am on a dynamic address but I though I would be able to ping the gateway as it does not need to run RIP.

I updates to Version 6 but that did not work. Everything else seems to be working.

Help!

[Pascal]

Sounds like your tunneled traffic is being blocked somewhere along the line. Does the Woosh device provide NAT / port forwarding? (Check that port 809 UDP is also being forwarded in to your server)

[rbaal]

No The Woosh Modem acts just like an Analogue Modem- there is a dialer entry for it. There is nothing to configure other than userid and password

Thanks
Bob

[adrien]

Hi

Did you upgrade both ends, or are you still running v5 on the server?

the connection type shouldn't matter, however woosh domestic services uses PPPoE, which will have an associated MTU issue.

So you get the control connection ok then? Do you see a tunnel created? This should show up in GateKeeper on both the client and server.

Adrien

[rbaal]

>>Did you upgrade both ends, or are you still running v5 on the server?

V5 at the server end as it supports several other nodes and I wanted to start with this one.


>>the connection type shouldn't matter, however woosh domestic services >>uses PPPoE, which will have an associated MTU issue.

I have seen something like that effecting throughput but not no connection at all.

>>So you get the control connection ok then?

Yes fine

>> Do you see a tunnel created?

Yes everything looks normal I see the tunnel, the routes, the remote IP address the remote machines (greyed out)

>>This should show up in GateKeeper on both the client and server.

Yes both end look completly normal except the data pipe seems to be closed

[adrien]

When you were on JetStream, was this through an external device connected by ethernet?

If so, the main difference that has happened on the VPN client, is that the IP address connecting would have been a private internal IP with Jetstream, vs a public IP address with Whoosh.

If your routing configuration on your main LAN is not automatically learning routes, then this could be a routing issue. Check the "most common issues" post at the top of this thread.

Adrien

[rbaal]

I agree that I need to fix the routing to make it dynamic for the rest of the network - but I should still be able to ping the VPN server at the HQ from the outstation. After all you don't run the rip client on VPN server itself only on nachines behind that VPN server.

Yes?

Bob

[adrien]

hmmm, that's correct.

So you can't even ping the VPN server?

That indicates an issue with the tunnel. None of that should have changed with simply a change in connection at the client end.

Any chance of running any network monitoring software to see if the packets are being transmitted/received etc from the server? It is possible that the packets are getting to the server, but that the return packets are not getting back.

Adrien

[rbaal]

Will see what I can set up and get back to you here