Grief with Contivity VPN Client and 1010

Greetings. I tried posting a message twice but got a 440 posting denied error. Anyway, I'm in a test phase for a project where people will be able to connect and authenticate remotely to the office.

Right now I have a laptop directly connected on the public side of the Contivity 1010. From there, I launch the Contivity VPN client, enter my RSA credentials and hit connect. It authenticates me, and I establish a connection to the private side of the

1010. If I issue an ipconfig on the laptop, it gives me my standard network settings as well as network settings for the virtual connection. The strange thing is, my virtual default gateway is the same as the virtual IP address from the address pool I created. When I created the address pool on the 1010, it asks for the ip range and a subnet mask. Nowhere does it ask for a default gateway. The 1010 does have a default gateway defined for both private and public sides but the connecting client doesn't know about it.

When I'm connected, I can ping the private side of the 1010, the management port and that's it. It cannot ping anything else on the private side including the default gateway. Systems on the private side cannot ping the virtual ip address. (I don't know if that is suppose to work or not).

Anyway, I'm stuck and cannot figure this out.

Here are some of the concerns/questions I have:

1) Is what I'm using (Contivity VPN client and Contivity 1010) sufficient for creating a vpn or is a vpn server required somewhere along the way?

2) Could some of my problems be caused by the fact that I'm directly on the same network as the Contivity 1010 and not going through an ISP to get to it?

3) Why doesn't the VPN client software know anything about the existing default gateway on the 1010 and substitutes the IP address instead? Is it suppose to work this way (same IP for both client and gateway) or don't I have something right?

I'd truly appreciate any feedback or directions on where to go from here. Thanks.

Reply to
Loading thread data ...

The contivity 1010's are great soho vpn servers and with the stateful firewall license (i believe it comes standard) there's alot of flexibility with filtering and nating. This vpn router/server can also terminate branch office (b2b) connections..

The default gateway issues you are having with your vpn client are by design. If you don't have split tunneling enabled, all traffic will route through your vpn tunnel and to the contivity device, you essentially are your own secure "gateway" if you would. What needs to happen in order to see other subnets is you'll need to define your default route or add static routes to a gateway device/router that knows how to direct your traffic. Oh, and don't forget to remove any "deny-all" filters on any interfaces...sometimes they are there by default.

hope this helps.

RM wrote:

Reply to

Thanks for your help. I eventually figured out that I needed to add a specific route to the firewall and to remove two others that were confusing it.

Reply to
RM Forums website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.