microsoft.public.access

Thanks, David. Your assistance is greatly appreciated. A VPN-based solution
is no longer looking quite as fearsome as I once suspected! I'm unlikely to
make a start on this for a week or so, but when I do I'm guessing that I
could run tests between my laptop PC as the client and my desktop PC as the
server and thus avoid involving my users until I know what I'm doing.

David


"David W. Fenton" wrote in message
news:Xns99D2686F999C3f99a49ed1d0c49c5bbb2@216.196.97.142...
> "David Anderson" wrote in
> news:uWqXrrPFIHA.1208@TK2MSFTNGP05.phx.gbl:
>
>> I've interpreted your post as meaning that VPN enabled routers and
>> software such as the free OpenVPN are the only building blocks
>> required to construct a VPN and that, if the relevant router(s)
>> already have VPN capability, then a VPN can be set up at no
>> additional cost. Is this correct?
>
> Yep.
>
>> My own router
>> certainly supports VPNs and I will make a point of reading the
>> relevant parts of the user manual asap. I'm assuming that my
>> Windows XP PC will be the focal point of the VPN connection and
>> that I am the one that creates the VPN, while my users have only
>> to install some sort of VPN client software. Do the routers at the
>> user sites also need VPN capability?
>
> Nope -- you've got it right. It's only the "server" site that needs
> to offer the VPN capability, and the clients only need a VPN client.
> The Windows VPN client is sufficient (though you'll likely want to
> use something other than the default settings, which last I checked,
> didn't even encrypt the tunnel!).
>
> --
> David W. Fenton http://www.dfenton.com/
> usenet at dfenton dot com http://www.dfenton.com/DFA/