Help, can not connect to computers, not accessible

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

Moderator: Qbik Staff

Help, can not connect to computers, not accessible

Postby Ann » Jun 05 07 8:50 am

Hello

On VPNing into the server, the network is visible, but the computers are all inaccessible!

I looked at the MTU setting and all is working correctly.

Please get back to me.

Ann
Ann
 
Posts: 38
Joined: Feb 20 04 5:54 am
Location: U.S.

Postby Pascal » Jun 08 07 12:33 pm

Ann, the list of computers shown in GateKeeper is transferred across the control channel. They do not rely on the machines actually being accessible.

For a machine to be accessible you need to have it aware of the remote network. This is so it can route traffic to it. To do that you need to do one of a few things:

1. Set the WinGate VPN server as the client's default gateway. If your VPN server has a private IP of 192.168.0.1, with the client at 192.168.0.2 you would set the client's default gateway (And usually DNS) to 192.168.0.1. This is done through TCP/IP properties.

2. Setup a RIP v2 listener on the client. Then go into VPN properties and configure it to broadcast discovered routes.

3. Setup static routes to the remote network on each client PC that goes through the VPN server on the local end.

If you've done one of the three and the machines are still showing as not accessible then we might need to look into firewalls, etc.
Pascal

Qbik New Zealand
pascalv@qbik.com
http://www.qbik.com
Pascal
Qbik Staff
 
Posts: 2623
Joined: Sep 08 03 8:19 pm
Location: Auckland, New Zealand


Return to WinGate VPN

Who is online

Users browsing this forum: No registered users and 16 guests