IPSec VPN issue

[mwiner]

ok. Well I have a VPN setup. With a Linksys BEFVP41 and SSH Sentinel VPN client I am establishing an IPSec VPN.
During my testing on a test network the VPN client was able to ping and access directories on the "server" via windows file sharing.

So I have put the vpn router in production. From home (I sit behind a linksys router) I connected successfully to the VPN. But I wasn't able to ping or see anything on the inside. So with the understanding that double NAT'ing and same network scheme of 192.168.1.0 might cause issues. I bypassed the router and plugged directly into the cable modem.

Now I reconnected the VPN and I was ABLE to ping everything on the inside. I was even able to RDP into machines. But file sharing didn't appear to be working. I tried by IP and by netbios name. Nothing... On the VPN router I have turned on NetBIOS broadcast for my VPN tunnel and I am sure I was able to do this in my testing previously.

I am getting very frustrated...

Anybody have any ideas? Thank you!!!!!


-Matt

 

[bcastner]

1. Use a different IANA approved NAT addressing scheme on both ends, not the same.

Have you thought about a Class A 10.0.x.x scheme at home?

2. You in the absence of a DNS ir WINS router at the far end, need to set the connection not to use the local gateway for name resolution.

 

[mwiner]

ok.. well to get over half of it I changed my network addressing scheme at home. So we got one part solved. I am now able to ping inside the network.

forgive once again Bill, but how would I set the connection to not use the local gw for name resolution?

would this be done in SSH Sentinel?


Thank very much!

-Matt

 

[bcastner]

Count me as lazy tonight, but use Google.
Search for "sentinel vpn client local gateway"

There are a lot of setup options explained in detail, and I hope one helps.

Best regards,
Bill Castner