VPN SETUP USING A 3G (VERIZON) CARD

[ybrit]

Hi.

I have found it very easy to set up my VPN's except a new one I am trying.

I setup up the client side (vista64) with a 3g Verizon card and I can ping the home office
side but I can not ping the client side from the home office.

I think the problem is no default gateway on the client side. The internal network on the client
is 192.168.6.1.

What to do?

[adrien]

Hi

What routes are exported by the client?

These are what makes it accessible or not.

Are any routes showing up as in conflict on the server or client?

[ybrit]

Published route:

255.255.255.255/75.213.174.46 (dynamic - changes every connection - say once a day. - verizon card)
255.255.255.255/192.168.6.1

The client properties in the VPN tree in wingate shows a IP address issued by a T-1 router - I have no idea where this is coming from.
Ipconfig shows two connections as above plus some IPv6 connectors that I have no knowledge of.

[jeff]

Hi

On client side, do you have your network card connected to a physical network ? (to make the "Link" comes up, and then be able to publish you local route)
If no link is detected, the route won't be published.
I had the same problem using a 3G card. I found an issue using a virtual network adapter. (the link is always "UP", so the IP is allways published thru the VPN).
You can find it here.
http://www.ntkernel.com/w&p.php?id=32
You will be able to reach the virtual ip at any time from the other side of the VPN.(as far as you publish the ip)
You just have to configure the IP / Mask. No gateway needed

Regards.