YES, the mistake we made was to use 192.168.1.X internally. AT&T also uses this as a default, but more important is for your road warriors. Apparently many hotels, motels, etc haven't bothered to change the default that comes with virtually ALL router manufacturers of using "0" or "1" (mostly "1") as the third digit in the default IP address.
Murray ________________________________ From: Erik Goldoff [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 05, 2008 11:13 AM To: NT System Admin Issues Subject: RE: vpn issue check your default gateway , AND because it's the same subnet as your own, you're probably not getting past the adjacency test ... when your IP stack goes to send a packet, first thing it'll do is check the destination IP and if it's on the same subnet as the machine you're sending from, just dumps it on the local wire (ARPs for mac for IP x) and then passes it on. You're never making it across the tunnel ________________________________ From: Jesse Rink [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 05, 2008 11:25 AM To: NT System Admin Issues Subject: vpn issue I thought this was odd, but maybe it's normal? My home network is on 192.168.1.0/24. I have a device at 192.168.1.1 and 192.168.1.2 (router and a network printer). When I VPN into another network on my Vista box, I am on their 192.168.1.0/24 network. They have a server I RDP into at 192.168.1.2, however, whenever I try to access that server, my Vista machine accesses the Printer I have at 192.168.1.2 instead of the server over the VPN. Is this normal behaviour? Just seems odd I have never run across this before in that 10-20 places I VPN into... No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.138 / Virus Database: 270.5.12/1592 - Release Date: 8/5/2008 6:03 AM ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
