Peter Duniho wrote:
[snip]
I think "ir" should be "it"?
Correct.

[excellent info Rmt Desktop snipped]

Depending on the routers (might have to reconfig a bit) at home and the
hotel, you could set up a VPN (Virtual Private Network) between the
two, and further restrict access from undesirables by allowing only
certain IPs in (that way, only the hotel and house could talk.) A lot
of routers have hardware VPN capability and you can also do it in
software, but it gets more complicated. You could sent it up so it
works both ways, you could remote into your office PC at the hotel from
home using Rmt Desktop and work from home.

One thing to note about Remote Desktop - Windows XP Home only can be a
remote not a host. It takes WinXP Pro to be the host. So if you have
Pro on both ends, you are good to go, if not, options exist.

I use Remote Desktop very reliably and with very good response from
home to work - over a 256K (both up and down) DSL line. Almost as good
as sitting at my desk. Since the cable modem bottle neck Peter
mentioned would be at the hotel end, it shouldn't affect you much
accessing the home PC from work. The remote (hotel) machine only has to
send keyboard and mouse commands; since you are actually "working" on
the host PC, unless you transfer a file from remote to host, there is
not much overhead in the remote to host direction. What will use the
most bandwidth is home PC (host) sending the screens to the remote.

There are some performance parameters in Rmt Desktop that you can set
to customize the connection, also. I would disable remote printers and
themes (backgrounds) but leave "send sounds to the remote computer"
enabled.

Randy