Scott:

<daddepants (AT) gmail (DOT) com> wrote in message
Boy, famous last words! :-)

If this is your "only" other problem, you are one lucky dude! :-)

Bill

We use VPN via PPTP to connect to all of our customers system through the
internet. Providing the broadband router/firewall at the customer is up to
port forwarding port 1723 (and most of the do now), it's a doddle with a
Wiin2k+ server... You don't even need to reboot Windows to get it working.

Worse problem is dynamic ip addressing on the internet side - though with
dynamic name services this is also not a problem.

The OP is using Windows NT - which these days is probably a bad move and is
well overdue for an upgrade to Windows 2000/2003. The rest is just getting
to grips with the relevant protocols - which is pretty well documented (see
the links I pointed him to).

As far as reliability, it's (almost) bulletproof. The biggest problem is
routers that seem to "forget" to port forward and need rebooting. The
"quality" of the router seems not to be related to price or specification,
it's a question of trial and error or getting a good recommendation - I
always use Netgear's DG834 for this purpose.

Out of interest, for VPN between sites (ie lan-lan access), I recommend
looking at the SOHO 6 router from Watchguard (www.watchguard.com) - it needs
a broadband router and an internet connection with 2 ip addresses but works
superbly.

Regards
Simon
"Bill H" <notme (AT) bogus (DOT) com> wrote

Well, I got it working but instead of messing with the port numbers on
an already diffective network, I went with LogMeIn.com's connection.
Very simple, very much like VNC but more secure. Everything is handled
through https so it works perfectly for what I need to do.

The only thing left is to actually get the internal network working as
it should. Which is completely do-able as long as I have about 12
bottles of Excedrine...hehe!

Thanks a bunch for all your help!