micky said:
Sorry about the FF question. This is definitely On Topic, afaik.
Will Remote Desktop do this?
I don't like running two computers, even if I can synchroonize them.
I have a desktop computer running XP (It may turn out to be Home or
Pro, if that matters) , but it's in the basement, which has seemed
really cold this year for the first time, and I'm not getting enough
fresh air anyhow**.
I think I would like to get a netbook and sit in the back yard and use
the netbook, via WiFi, as a terminal for the computer in the basement.
Can I do that with Remote Desktop? (Or some other feature of
Windows?)
I've never used that. Does it have visible overhead, or would the
full screen match my usual full screen?
Or, since both computers would be on the same wired/wireless network,
is there a better way? (Ill ask about that on
alt.comp.networking.connectivity if you say Remote Desktop is good.)
**I've just been sick for 2 weeks, and for 6 of the days, I spent an
hour in the backyard, in too much pain to do gardening, just sitting,
and for the first time in 28 years, really appreciated my pretty back
yard. I think I should spend more time there.
Thanks a lot.
I doubt your small netbook is going to have the same [max and native]
resolution as your monitor on your desktop. As a consequence, the
desktop you see on your netbook, even if full sized (instead of
windowed), will be smaller which means RDP on the desktop will have to
reduce its screen resolution to match what you are using on your
netbook. That means desktop icons will probably get moved around. Apps
that you open on your desktop that have a certain width and height won't
have that when you view them via RDP at the smaller screen resolution on
your netbook.
For example, say the LCD monitor you have on your desktop has a native
resolution of 1920x1080. Well, that's the resolution you should be
running that monitor so to eliminate artifacts, like fuzziness or color
tinging caused by having to interpolate between pixels at other non-
native resolutions. Your netbook has a max/native resolution of, say,
1024x640. So how are you going to view a 1920x1080 desktop monitor on a
1024x640 netbook monitor? By have RDP change the screen resolution on
the desktop monitor to reduce it down to 1024x640. So consider what
your desktop monitor would look like with its total pixel count reduced
to a third ((1024*640)/(1920*1080)=0.32). Because you are viewing the
remote desktop with a local desktop that is much smaller means you only
get the resolution of the smaller desktop. RDP is showing you a desktop
so it has to match the resolution of your local desktop. RDP does not
provide for virtual desktops where you can pan around but then you still
don't get to see all of the virtual desktop, just a piece of it. This
is the best scenario only if you maximize the remote desktop client to
fullscreen. If you window the remote desktop then you'll have an even
smaller resolution to work with on the remote desktop.
Typically users of RDP (or any remoting software) use an equal or larger
resolution local desktop when viewing the equal or smaller resolution
remote desktop. That way, they get to see the remote desktop at its
normal resolution. Because of changing resolutions on the remote
desktop (to make it smaller) can result in unwanted artifacts, like the
desktop icons getting moved around so they can fit the now smaller
space, usually you want to use a larger viewport on the local end than
the screen size on the remote end. You're going the opposite direction
where you would use a smaller viewport locally which results in having
to reduce resolution on the remote end.
Even with compression, you are pushing a lot of traffic across the
network. If your setup is between intranet hosts then you don't have to
contend with the slower Internet speeds along with hosts getting busy in
the route between your local and remote hosts. With RDP between RDP
hosts, and disallowing any other network traffic, you'll have the full
speed available for the slowest connection you have for the end point
hosts and the network between. If you have 1Gbit bandwidth in the NICs
in both hosts and the router or other access points in your network then
you'll get 1Gbits transfer. If one of the hosts only has 10Mbits then
that's the highest transfer rate. Since you're likely talking about
wireless connection with your netbook via a wireless access point or
wireless router, you might only have a max of 11 or 54Mbps which means
that's as fast as you can transfer. You never mentioned what hardware
is employed in your network.
If you are going between just your intranet hosts then you don't need
punch holes in your router's firewall, like opening port 3389 to
unsolicited outside connection requests and then having to port forward
3389 to whatever intranet host is running RDP (the remote desktop to
which you want to connect). However, if you are running a software
firewall on the remote host then you need to punch a hole in that
firewall to permit unsolicited inbound connections on port 3389 (the
default one used by RDP). You will not be able to connect to a remote
desktop unless you have a password on the accounts on that host. That
means you cannot have blank passwords on accounts there. When you use
RDP to connect to the remote host, you will be required to enter a
username (account name) AND a password. The is the security mechanism
to ensure that someone else doesn't remotely connect to that host.
You never mentioned what type of security mechanisms you enabled or
employed in your wireless network. If you left it insecure than anyone
else can tap into your wireless network and possibly remote into your
desktop host. While RDP requires a login, that won't prevent hacking in
by guessing on the login credentials (unless you also configured
security on that host to disable further logins for a specified time if
a threshold of failed logins is met) so you want your network secured
when it's wireless. Search Windows own help on "remote desktop" and
read the "Best practices: Security" topic on using strong passwords and
also how to remotely login without having to use an admin-level account
(on the remote host) by adding your non-admin account to the Remote
Desktop Users group. RDP means you are permitting an external
connection to that remote host and you want only yourself to be allowed
that external connection.
Are there apps that you can only install on your desktop that you can't
put on your netbook? If it's not the apps but just the data files you
want to get at, why not share them across the network? Some apps don't
like sharing (well, not concurrent sharing), like Outlook with its .pst
file, and many are not designed for concurrent sharing; however, if
you're out in the backyard running Excel then it's not likely that you
have Excel running on the basement computer or with the same document
opened in it. Just what is it that you expect or need to do via RDP
that you couldn't do by having the app local on your netbook? A
licensing issue perhaps? If you read the EULA and it really doesn't
allow multiple concurrent installs on different computers (versus
multiple concurrent *running* instances of the software), there are
likely freeware alternatives you can put on your netbook to work on the
same docs that you could share from your desktop host to your netbook
host.