winoto: They don't have to change but the should have some sort of inbound NATing setup to compensate for this. I deal with 100s of remote networks with all typing of addressing, there are ways around it.
Well, ask your company if they can do one-to-one static nats on a diffrent subnet range. I have never heard of a company handin out 192.168.x.x addresses it is rather silly, lack of foresight if they have home users.
Well, that error could mean the SA is not building properly. Also could mean your ACLs on each side do not match, verify that it is indeed the same encryption hash, group ect on both sides. Also make sure the ACL matches, do you see either phase l or phase ll come up? Do you have access to...
Uhm, in theory it could work, providing your VPN devices to their own authentication. XP can be used as a server, not very efficient though. You may want to hire a consultant or another company to help you out a bit.
Well the VPN is just IPsec over TCP/IP so my guess woudl be to make sure you do not have any browser scripts running, tools -> internet options -> connections tab -> LAN settings
Also, what is supplying your DHCP/DNS local servers? ISP?
JOAMON (IS/IT--Management) 18 Apr 05 13:56
Speaking from the lan/wan guy side I personally would not allow a router to router VPN connection for a home user. This would not only allow one machine at the home site but all machines on that network access through the VPN. With everything on the...
CaMiX (IS/IT--Management)
First off you have a few stipulations to building a VPN between a 3000 and a Linksys box. There is no static NATs which may or may not be a problem for you.
First you can go through your VPN Wizard in the 3000 box and enter the remote peer(Linksys) and keep paging...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.