Putting Windows Remote Desktop on an old PC

I'm sure I read this is fairly easy, however I only have about 5 minutes
of spare time today, perhaps some kind soul could tell me how?

I need to put remote desktop client on a very old PC running NT4
workstation.

Thanks
--
Regards
Jon


Jon

In article <(E-Mail Removed) >, Jon
(E-Mail Removed) says...
> I'm sure I read this is fairly easy, however I only have about 5 minutes
> of spare time today, perhaps some kind soul could tell me how?
>
> I need to put remote desktop client on a very old PC running NT4
> workstation.
>
Download msrdpcli.exe, run it, run mstsc.exe, enter the name or IP
address of the PC you want to connect to (adjust firewall rules as
necessary) ... I'm not sure that's really what you wanted to know
though.

"Jon" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) et...
> I'm sure I read this is fairly easy, however I only have about 5 minutes
> of spare time today, perhaps some kind soul could tell me how?
>
> I need to put remote desktop client on a very old PC running NT4
> workstation.
>
> Thanks
> --
> Regards
> Jon

My favourite is RADMIN, at work I use PCAnywhere, VNC is good but
I havn't used it much. The one utility that I have never seen used is the
built-in on in Windows.

--
Graham.
%Profound_observation%

Graham wrote:

> My favourite is RADMIN, at work I use PCAnywhere, VNC is good but
> I havn't used it much. The one utility that I have never seen used is
> the built-in on in Windows.

I have no experience on RADMIN or PCAnywhere, but the built-in Remote
Desktop functionality in Windows XP Pro is pretty good. In my opinion,
it is actually better than VNC as it offers easy drive and printer
mapping and sound redirection facilities over the network. In addition
to that, it just generally feels snappier.

* * *

It is also technically possible - although probably not permitted by the
EULA - to enable an XP Pro system to serve multiple concurrent remote
desktop sessions.

This means that several family members can use the same XP Pro system
simultaneously, by logging in to their desktops with their personal
accounts from remote machines (and from the local console, of course.)
(Just like with Terminal Services, really, but that's not too surprising
as the Remote Desktop feature in XP Pro is actually just a castrated
version of Terminal Services.)

For example, if a family member wants to check their e-mail on the
desktop PC, or even play games on it, you can detach from your session
by using Fast User Switching (Windows-L), let them log in while your
session (with all the applications you have opened) is still running on
the background, and then reconnect to your session from a laptop or some
other secondary PC - even Linux computers, using "rdesktop" - while
they're still using the desktop PC locally.

--
znark

On 23/07/2007 in message
<109pi.196493$(E-Mail Removed) > Jukka Aho wrote:

>It is also technically possible - although probably not permitted by the
>EULA - to enable an XP Pro system to serve multiple concurrent remote
>desktop sessions.

Like you I find the native XP remote desktop quickest. Is there any way at
all of running a W2K PC from an XP laptop? I know you can do it the other
way round but W2K with remote desktop gives me all I need.

--
Jeff Gaines Damerham Hampshire UK
There are 10 types of people in the world, those who do binary and those
who don't.

Jeff Gaines wrote:

> Like you I find the native XP remote desktop quickest. Is there any
> way at all of running a W2K PC from an XP laptop? I know you can do
> it the other way round but W2K with remote desktop gives me all I
> need.

I think the only way to do that in a W2K environment would be running
Terminal Server on a Windows 2000 Server. But what you probably have is
an ordinary workstation version of the W2K, which does not support this
option.

(The reason why XP Pro has this capability is because the Fast User
Switching feature is based on [a version of] Terminal Server
components - so allowing remote desktop logins was a natural extension
of that concept - but W2K does not have Fast User Switching.)

I don't think there is any easy way of allowing Remote Desktop logins
with a mere workstation version of Windows 2000. Surely it would be
_technically_ possible to achieve that by resorting to some sort of
advanced, hackish trickery - such as manually copying and installing the
required Terminal Server components from a W2K Server and tricking them
into believing they're still running on a W2K Server while they're not -
but I don't think anyone has actually gone through that trouble and
documented it. And needless to say, it would be in violation of all
kinds of licences.

--
znark

On 24/07/2007 in message
<vwapi.196519$(E-Mail Removed) i> Jukka Aho wrote:

>I think the only way to do that in a W2K environment would be running
>Terminal Server on a Windows 2000 Server. But what you probably have is an
>ordinary workstation version of the W2K, which does not support this
>option.

Many thanks Jukka :-)

I have MSDN copies of all MSFT OS's back to DOS 6.2 so may well have W2K
Server. Can't check ATM as house is upside down due to decorating.

--
Jeff Gaines Damerham Hampshire UK
There are 10 types of people in the world, those who do binary and those
who don't.

(E-Mail Removed) declared for all the world to hear...
> Graham wrote:
>
> > My favourite is RADMIN, at work I use PCAnywhere, VNC is good but
> > I havn't used it much. The one utility that I have never seen used is
> > the built-in on in Windows.
>
> I have no experience on RADMIN or PCAnywhere, but the built-in Remote
> Desktop functionality in Windows XP Pro is pretty good. In my opinion,
> it is actually better than VNC as it offers easy drive and printer
> mapping and sound redirection facilities over the network. In addition
> to that, it just generally feels snappier.

Only disadvantage is that it boots out the currently logged on user, so
they can't see what you're doing - no good for remote support where you
want to "teach" the user what to do next time.
--
Regards
Jon

(E-Mail Removed) declared for all the world to hear...
> In article <(E-Mail Removed) >, Jon
> (E-Mail Removed) says...
> > I'm sure I read this is fairly easy, however I only have about 5 minutes
> > of spare time today, perhaps some kind soul could tell me how?
> >
> > I need to put remote desktop client on a very old PC running NT4
> > workstation.
> >
> Download msrdpcli.exe, run it, run mstsc.exe, enter the name or IP
> address of the PC you want to connect to (adjust firewall rules as
> necessary) ... I'm not sure that's really what you wanted to know
> though.

Thanks, that's just the job.
--
Regards
Jon

On Mon, 23 Jul 2007 21:34:22 +0100 Graham
from the village of (E-Mail Removed)
felt we might be interested in the following...



> My favourite is RADMIN, at work I use PCAnywhere, VNC is good but
> I havn't used it much. The one utility that I have never seen used is the
> built-in on in Windows.

LogMeIn (logmein.com) has a variety of different solutions, one of which
is a free offering. I use it to admin several remote PC's.

Only drawback is you have to get to the remote PC to install the
software, or ask the user to do so, and if they are asking for help
anyway, talking them through installing via the phone is no fun at all!

But once it is up and running - well, i've found it flawless thus far,
and i 'control' PC's in England, Spain and Cyprus.


--
My reply address is valid, but incoming mail is set to 'auto-delete'
so will not be seen. Please post replies to the group.
XPS M1710 / 2.16 GHz dual core / 2Gb DDR2 / nVidia GeForce 7950GTX