Remote Desktop

  • Thread starter Thread starter Obsidian Eternus
  • Start date Start date
O

Obsidian Eternus

I am unable, after 2 hours of scouring, to find the Remote
Desktop Host software, to allow my Windows XP Pro box to
connect to my Win2k Pro router rig. Has anyone else
managed to find such software, if it exists?
 
Obsidian Eternus said:
I am unable, after 2 hours of scouring, to find the Remote
Desktop Host software, to allow my Windows XP Pro box to
connect to my Win2k Pro router rig. Has anyone else
managed to find such software, if it exists?
Click to expand...

Remote Desktop requires either Windows XP Professional to run
on the host, or Windows Terminal Service (which is available on
Windows Servers).

In other words, a Windows 2000 Workstation cannot act as a
host for a Remote Desktop session. You have to use some other
tool such as WinVNC or pcAnywhere.
 
Remote Desktop requires either Windows XP Professional to run
on the host, or Windows Terminal Service (which is available on
Windows Servers).

In other words, a Windows 2000 Workstation cannot act as a
host for a Remote Desktop session. You have to use some other
tool such as WinVNC or pcAnywhere.
Click to expand...

To use Windows 2000 as a Remote Desktop Session just get the remote
Desktop from XP home or from XP Pro and install it to Windows 2000. It
will show up under "Start" "Programs" "Accessories" "Communications"
"Remote Desktop Connections" I use it on Windows 2000 to access
XP Pro at work.. Works just great! To use Windows 2000 as
a Host just load the Terminal Server to Windows 2000 and it will
then act as a HOST... Hope this helps...
 
Joe said:
To use Windows 2000 as a Remote Desktop Session just get the remote
Desktop from XP home or from XP Pro and install it to Windows 2000. It
will show up under "Start" "Programs" "Accessories" "Communications"
"Remote Desktop Connections" I use it on Windows 2000 to access
XP Pro at work.. Works just great! To use Windows 2000 as
a Host just load the Terminal Server to Windows 2000 and it will
then act as a HOST... Hope this helps...
Click to expand...

Sounds interesting. How exactly do you load Terminal Server on
a Windows 2000 Professional PC?
 
Sounds interesting. How exactly do you load Terminal Server on
a Windows 2000 Professional PC?
Click to expand...

Sorry for the incorrect wording! You don't run Terminal Services on
Windows 2000 Professional, It has to be either Windows 2000 Server,
Advanced Server, or Data Center Server in able to run..But, the Remote
Desktop can be run on Windows 2000 Professional as described above after
installation..
 
Joe said:
Sorry for the incorrect wording! You don't run Terminal Services on
Windows 2000 Professional, It has to be either Windows 2000 Server,
Advanced Server, or Data Center Server in able to run..But, the Remote
Desktop can be run on Windows 2000 Professional as described above after
installation..
Click to expand...

.. . . which is exactly what I wrote in my first reply to the OP!
Furthermore,
Remote Desktop can be installed on any Windows PC, including Win9x.
 
Pegasus said:
. . . which is exactly what I wrote in my first reply to the OP!
Furthermore,
Remote Desktop can be installed on any Windows PC, including Win9x.
Click to expand...

Which side? The Client side or the "Host" side?
 
Phillip Windell said:
Which side? The Client side or the "Host" side?
Click to expand...

The host side requires Terminal Server. This service is available on Windows
Servers only.
The client side requires Remote Desktop. Remote Desktop can be run on any
flavour of Windows.
 
Pegasus said:
The host side requires Terminal Server. This service is available on Windows
Servers only.
The client side requires Remote Desktop. Remote Desktop can be run on any
flavour of Windows.
Click to expand...

Ok, so it is the Client side, that is what I thought. Doesn't Win2000
already have the TS Client that does the same thing?
 
Phillip Windell said:
Ok, so it is the Client side, that is what I thought. Doesn't Win2000
already have the TS Client that does the same thing?
Click to expand...

I forgot one thing, so let me rephrase my statement:

The host side requires:
- Terminal Server (available on Windows servers only), or
- Windows XP
It is not available on Windows 2000.

The client side requires Remote Desktop. Remote Desktop can be run on any
flavour of Windows.
 
In
Pegasus said:
I forgot one thing, so let me rephrase my statement:

The host side requires:
- Terminal Server (available on Windows servers only), or
- Windows XP
It is not available on Windows 2000.

The client side requires Remote Desktop. Remote Desktop can be run on
any flavour of Windows.
Click to expand...

Just want to point out, that on WIndows 2000, Terminal servics needs to
installed thru Add/Remove Programs. It can be installed as either in Remote
Adminstration mode (which only allows two sessions to 'administer' the
server and is designed just for administrators) or in Application Mode,
which allows mutliple user sessions, which allows remote desktop usage. The
advantages of Application Mode are obvious and is the toned down version of
what Citrix offers.

In Windows XP and Windows 2003 Server (any version) they have the Remote
Desktop Service installed, but not started, until you go into My Computer
properties, Remote tab, and enable it. This mode is WIndows 2003 Server is
the equivalient to Windows 2000's "Remote Administration Mode". If you want
full "Terminal Services" functionality, which is the equivalent to Windows
2000 Application Mode, then you need to isntall it thru Add/Remove Programs.

Of course all the above 'modes' can be accessed by a number of methods. One
is using the Terminal Services Console (MMC), which I use. You can configure
it to add mutliple sessions and toggle back and forth thru them in the list
while they are all active. The other method is to use Terminal Services
client that can be installed from Windows 2000 once Terminal Server services
(either mode) have been installed. That is located in
system32\config\clients. The third method is to use Remote Desktop Client,
which is installed by default in Windows 2003 Server or XP Pro. THe other
operating systems, you need to download it from Microsoft's download center.

I hope that helps!
Cheers! :-)

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
 
"Ace Fekay [MVP]"
while they are all active. The other method is to use Terminal Services
client that can be installed from Windows 2000 once Terminal Server
Click to expand...
services

Yes, that was the point I was making was that there isn't a need to install
XP's Remote Desktop client on Win2000 because it already has Terminal
Services Client which does the same job and is compatible with the Remote
Desktop features of XP and 2003 when they act as "hosts". Otherwise Win2000
couldn't connect to Remote Desktop Services unless someone happened to have
an XP CD around or downloaded the client from the Internet.
 
"Ace Fekay [MVP]"
In

Just want to point out, that on WIndows 2000, Terminal servics needs to
installed thru Add/Remove Programs.
Click to expand...

Your post does not spell it out but I assume that when you say
"Windows 2000", you actually mean "Windows 2000 Server",
not "Windows 2000 Professional". The difference is essential!
 
Pegasus (MVP) said:
Your post does not spell it out but I assume that when you say
"Windows 2000", you actually mean "Windows 2000 Server",
not "Windows 2000 Professional". The difference is essential!
Click to expand...

My understanding is that Windows2000 Pro, before XP or 2003 ever came along,
had a Terminal Services Client that could connect to a Terminal Services
Server and is also capable of connecting to the Remote Desktop Services of
XP and Server2003 without having to download and install the RD Client from
XP on it. This was the point I was trying to make earlier but it may not
have been clear.
 
In
Pegasus (MVP) said:
Your post does not spell it out but I assume that when you say
"Windows 2000", you actually mean "Windows 2000 Server",
not "Windows 2000 Professional". The difference is essential!
Click to expand...

You're correct. Windows 2000 Server versions, not Pro.
The difference is very essential!
:-)

Ace
 
In
Phillip Windell said:
My understanding is that Windows2000 Pro, before XP or 2003 ever came
along, had a Terminal Services Client that could connect to a
Terminal Services Server and is also capable of connecting to the
Remote Desktop Services of XP and Server2003 without having to
download and install the RD Client from XP on it. This was the point
I was trying to make earlier but it may not have been clear.
Click to expand...

Still confused. Win2kPro never had a "built in" terminal service client. SP2
and newer offers it, but it still has to be installed.

Ace
 
In
Phillip Windell said:
"Ace Fekay [MVP]"


Yes, that was the point I was making was that there isn't a need to
install XP's Remote Desktop client on Win2000 because it already has
Terminal Services Client which does the same job and is compatible
with the Remote Desktop features of XP and 2003 when they act as
"hosts". Otherwise Win2000 couldn't connect to Remote Desktop
Services unless someone happened to have an XP CD around or
downloaded the client from the Internet.
Click to expand...

Phillip, are you saying that Windows 2000 Pro has the terminal service built
in?

Not to contradict, but what I was actually saying, either the Terminal
Services Client, Remote Desktop client or the Terminal Services Connections
MMC needs to be installed on Windows 2000 Pro, none of which are built into
Windows 2000 Pro, that is previous to Service Pack 2 (but didn;t install it,
but just available in the i386 folder of the SP), unlike XP, which has the
Remote Desktop Client built in.
http://www.experts-exchange.com/Operating_Systems/Win2000/Q_20281938.html
http://www.windowsxpuser.com/forums/viewtopic.php?p=20063

But one cool thing I forgot about that can be used to access a Terminal
Server server is the TSAC ActiveX web based client. TSAC needs to be
installed on the Windows 2000 servers running Terminal Services to add this
functionality so it can be accessed by a browser.
http://msdn.microsoft.com/library/d...rv/termserv/remote_desktop_web_connection.asp

You can even make an XP Pro machine work like this so you can connect to it
thru a web page instead of using any of the client apps:
XP Pro Remote Desktop Connection Web Connection Software Download:
http://www.microsoft.com/windowsxp/pro/downloads/rdwebconn.asp

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
 
"Ace Fekay [MVP]"
In Phillip, are you saying that Windows 2000 Pro has the terminal service built
in?
Click to expand...

No, I'm saying that is has a TS Client,...the "Viewer" side of the thing.
There is no need to download or get the Remote Desktop Client from XP to run
on it. Windows 2000 Pro had to have *something* to connect to a TS Server
before XP and Server 2003 was invented.

I got in this conversation because it sounded like I was hearing that
Windows 2000 Pro could not connect to a Remote Desktop Host (Server-side)
unless you hunt down the Remote Desktop Client from XP and install it on the
2000 Pro box so it (Client-side) could connect to the Host (Server-side) and
I don't think that is the case,...I think there is already a TS/RD
compatible Client already supplied with Windows 2000 Pro.
 
"Ace Fekay [MVP]"
Still confused. Win2kPro never had a "built in" terminal service client. SP2
and newer offers it, but it still has to be installed.
Click to expand...

Then that is the one I am talking about. I just didn't know it came with
SP2. All the Win2000 boxes I dealt with TS/RD on were already at SP4, so I
wouldn't have known the difference.
 
In
Phillip Windell said:
No, I'm saying that is has a TS Client,...the "Viewer" side of the
thing. There is no need to download or get the Remote Desktop Client
from XP to run on it. Windows 2000 Pro had to have *something* to
connect to a TS Server before XP and Server 2003 was invented.

I got in this conversation because it sounded like I was hearing that
Windows 2000 Pro could not connect to a Remote Desktop Host
(Server-side) unless you hunt down the Remote Desktop Client from XP
and install it on the 2000 Pro box so it (Client-side) could connect
to the Host (Server-side) and I don't think that is the case,...I
think there is already a TS/RD compatible Client already supplied
with Windows 2000 Pro.
Click to expand...

Sorry, I meant to ask:
Actually it never came with a client installed out of the box. One would
need to have installed the client from either (once Terminal Services on a
W2k Server was installed) the TS Client creator (for floppies) from the
Start/Prog/Term Server client creator or by going physically into
system32\config\clients folder and sharing that out and doing it across the
network.

But now days, with Win2003 (any version) and XP, it's built in. Win2k SP2
and newer, it's available in the i386 folder. The RDP client for Win2k (any
version) was an after thought and optionally downloadable. Believe me, been
teaching W2k stuff for awhile now, and when using TS with W2k Pro or server,
it was a PITA to always have to install the client on an unused student
machine that I would sit down in front of so when my studetns would be
working on a lab, I would TS into my own machine or a client's to get some
work done.

It;s nice now that the RDP client is built into XP and W2k3. At home I use
the Terminal Services Connections snap-in. I like it because on the left
side of the screen I can create mutliple sessions, and it shows up on the
right pane. I can connect to them all and toggle back and forth between them
by clicking on the session ID on the left, copy and paste between them, etc.
Cool tool.

Ace
 
Back
Top