WINGATE VPN - LAN Not Acessible

[geraldo]

Hi

I am having trouble with browsing over my vpn connection.

Wingate server - win2k with wingate 5.2.3 and vpn 1.2 installed. This server belongs to a domain tree in which a domain server handles the dns control for the domain. The gateway is set to the wingate server. The pc have shares and are accessible on the network. There are 2 network cards one with an private and one with a public address.
Rip v2 has also been installed but this does help either

I have a pc with wingate vpn on the other side which has one network card with a public address.

The machine have different subnets.

The connection is established but after that is just shows the wingate server and the network pcs as "NOT ACCESSIBLE"

[Pascal]

First test is to see if you can ping any of the internal IPs. Start with the server and work your way to one of the clients. This is a basic test to see that the tunnel is created and accessible.

If you can ping; the problem is with Microsoft Networking. Normally, if a computer only has a public interface (Such as dial-up, etc.) File and Printer sharing is not started. This means that MS networking is non operational and things like testing to see if a machine is accessible won't happen. Is File and Printer sharing started on the remote client?

[geraldo]

I have already made the conection and it is up and runing but i cannot ping any of the inetrnal addresses either of the pcs on th network or the inetrnal ip of the host. How do i check if the filesharing is available on the host machine?

[genie]

Are you trying to ping a VPN machine or a client behind it?

[Pascal]

There's a difference between the control channel connection (Commands, etc. and TCP based) and the data channel (Network traffic and UDP based).

I don't think you need to worry about file/print sharing on the host - that machine has a local network behind it; so that will be started. However, if you can't even ping then something is blocking the tunneled packets.

Are you going through a device that requires port forwarding / virtual servers? Something like a DSL Router, etc. that will NAt traffic basically - in some cases you need to forward port 809 UDP for the tunneled traffic to reach the VPN.

I'd recommend that you have a look through our VPN Setup guide; you can find it here: http://www.wingate.com/resources.php

[adrien]

This sounds to me like the bog-standard routing configuration issue on your LAN.

When the WinGate VPN server is not the default gateway on your LAN, then the machines on the LAN need to be told to use the WinGate VPN gateway to access the rest of the VPN, else they will send the VPN packets to the main LAN gateway instead.

There are typically 3 ways around this.

1. enable the RIP listener on your main network gateway if there is one. then this gateway will learn the routes to the VPN, and make them available to machines on your LAN that use this gateway.
2. install the Qbik RIP2 client on the machines on your LAN that you need to access.
3. manually add routes to either the main network gateway or each machine on your LAN that you need to access pointing them to the WinGate VPN server for access to the subnets on your VPN.

Adrien

[geraldo]

All the last requisites have been done but i have notocied that when i connect via vpn the following happens
1. you cannnot ping the external ip of the vpn host which works when there is no connection.
2. all other internet connections are then disbaled.

[Pascal]

all other internet connections are then disbaled.

All other connections from the VPN Server to the outside world or client machines behind the Server out to the Internet?

Does your VPN Server double as your Internet Gateway? If it does, how are you sharing the connection?