Howard
"Phillip Windell" wrote:
> "howard" <how...@discussions.microsoft.com> wrote in message
> news:9FDFB471-A89C-4762...@microsoft.com...
> You don't need a "connection". It isn't that complex. A VPN link, by nature
> and by definition, is already part of your private LAN. Without knowing
> more about your LAN's design, I'd say all you need is the proper Static
> Route to be able to cross the VPN link.
>
> If you have a regular LAN Router (not an Internet NAT Device) that would
> already be all the machine's Default Gateway, then you'd simply add a Static
> Route to the LAN Router so that it knows that anything destined for the
> remote LAN is to use the VPN Device as the "gateway". If you run a single
> subnet, then the Static Route *might* be able to work from your Internet
> Sharing Device, assuming it is the Default Gateway of all the machines and
> that it can accept Static Routes. If that doesn't work, then your last
> option is to add the Static route to every desktop machine individually.
>
> The same process most likely will have to be repeated on the other remote
> LAN.
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
>
Thank you,
Robert
"Phillip Windell" wrote:
> "howard" <how...@discussions.microsoft.com> wrote in message
> news:FD3B0C58-2323-4B09...@microsoft.com...
> > You're right - I already have connectivity and it must be through the VPN
> > (typing "\\192.168.16.2" in the 'Run' window brings up the network shares
> of
> > that machine after I provide login info) Can I presume my VPN tunnel is
> > providing the routing function?
>
> Yes you are already working
>
> > Guess my next step is to create the necessary WINS and/or DNS entries.
>
> Just do WINS and use the netbios names of the target machines or the IP#.
> Leave the DNS and the FQDNs out of it unless you are going to crete a Trust
> between the two Domains at the opposite ends of the link.
"robinio" <rob...@discussions.microsoft.com> wrote in message news:44A2BC3F-A615-48B8...@microsoft.com...
"robinio" <rob...@discussions.microsoft.com> wrote in message news:BD06592E-D468-4620...@microsoft.com...
Regards,
Robert
"robinio" <rob...@discussions.microsoft.com> wrote in message news:D4983B00-3578-4DCF...@microsoft.com...