<snip>

> > > If your office DSL is not a fixed IP address, well, since it can
change
> > > on a daily basis, it would be impossible for you to GUESS the office
> > > network public IP address - you would have to get someone at the
office
> > > to tell you the IP address and then you could do it using the other
VPN
> > > or direct (port forwarding method).
> >
> > An easy solution to this problem is provided free of charge by
> > companies such as www.no-ip.com or www.dyndns.org.
>
> Yes, but you might still want a fixed IP so that everything works all
> the time and perfectly. Imagine the headache it causes when the lease
> expires and the new IP has not replicated to the public DNS servers yet.

I have several clients with dynamic addresses. Since the
addresses are stable, they don't have a problem. They know
that they get a new address after a power failure, and they
know that they need to wait ten minutes until the new address
is known. Nice'n'easy!


> > > What you need to do is ask the Administrator if they have VPN setup on
> > > the Windows 2003 server or if they have VPN Setup on the Firewall. If
> > > they run a Dual NIC setup and SBS 2003, then you will use one solution
> > > path, if a single NIC and a NAT Router, then it's another path.
> >
> > You do not need a VPN for Remote Desktop. It works just
> > as well without.
>
> Yes, but do you really want to expose your Windows connections directly
> to the Net, risking a weak password?


Same with a VPN: You're exposed with a weak password too!