LOL @ epic fail. A VPN *CAN* use those ranges AND it depends on the configuration of each router whether or not it will route the RFC1918 space. Some do :)
> > -----Original Message----- > > From: [email protected] [mailto:hardware- > > [email protected]] On Behalf Of Brian Weeden > > Sent: Tuesday, April 27, 2010 10:56 AM > > To: [email protected] > > Subject: Re: [H] VPN connection seals computer off from LAN > > > > That doesn't make any sense - 10. addresses cannot be routed via VPN, > > same as 192. Both of those address ranges are explicitly defined as > private > > and cannot be routed on the Internet. The minute any packet with a 10. or > > 192. > > or any other private range hits an internet router it gets dropped. > > > > I think on my end the issue was with the public vs private network > > designations in Windows 7. I had the VPN connection defined as public > > which means it is untrusted and Windows won't allow network discovery or > > file sharing. I think somehow Windows got confused with the machine > > being on a private (trusted) LAN and public (untrusted) WAN at the same > > time. Not sure tho. -- Bryan G. Seitz
