How configure W2000 Terminal Server to behave as W-XP Remote Desktop Server?

  • Thread starter Thread starter JMPD
  • Start date Start date
J

JMPD

Hello,

I have Windows XP-Pro installed on a machine, and I can control it
from any machine (i.e. NT40), using the Remote Desktop Client. When I
do so, I can see the desktop as if I were in front of my Windows XP
machine.

I have also a Windows 2000 Server, with Terminal Server enabled. I can
also control it with Remote Desktop Client. But the result is
different: I get started a new session, different from the one that is
running in the W2000 machine; so the W2000 is running two simultaneous
sessions. But that is not what I need, I only want to take control of
the session that is already running (let's call the 'console'
session).

Is there any way of configuring in my W2000 the Terminal Server to not
create a new session when a Remote Desktop Client tries to connect to
it? But to take control of the console session?

Thanks in advance for any help,
 
(e-mail address removed) (JMPD) wrote in @posting.google.com:
Hello,

I have Windows XP-Pro installed on a machine, and I can control it
from any machine (i.e. NT40), using the Remote Desktop Client. When I
do so, I can see the desktop as if I were in front of my Windows XP
machine.

I have also a Windows 2000 Server, with Terminal Server enabled. I can
also control it with Remote Desktop Client. But the result is
different: I get started a new session, different from the one that is
running in the W2000 machine; so the W2000 is running two simultaneous
sessions. But that is not what I need, I only want to take control of
the session that is already running (let's call the 'console'
session).

Is there any way of configuring in my W2000 the Terminal Server to not
create a new session when a Remote Desktop Client tries to connect to
it? But to take control of the console session?
Click to expand...

Windows 2000 doesn't know "console" mode.
CU
Bernd
 
Win2003 terminal server allows admin console access. For win 2000 Terminal
server search the internet for a copy of the free VNC program. Install it
as a service, allow access through the firewall for Port 5900 or whatever
TCPIP port you want to use and then use the VNC client on the remote system
to control the console on the terminal server.

VNC remote control is similar to using PC anywhere for the same purpose but
free and much more stripped down but in this case that is good. All you
need is remote control, as if you are sitting at the server console, and
that's what VNC does.

I have found this critical for the following things.

Running processes and servers that may take a great deal of time. As you
know if you log on a in remote desktop it creates a whole new admin session.
If you kick off the process and then logoff it's a high probability that
process will be killed upon logoff.

Dealing with backup software. most version of Backup exec and arcserve in
use have some real problems when you go in under a remote desktop session
and kick off a job or schedule a future job. Again once you log off it is
all lost. I heard the newest versions handle this better but I have yet to
see it.

Anyone that has a Lotus notes Server. There is no way to see the black
command console (which is critical in notes management without VNC or
PCanywhere running on that server.

Just to summerize what you are implying, my experience has been to properly
manage a server without buggy issues it is much better to use a program that
gives you true console access versus this remote desktop emulation. The
only exception, like I said, is win 2003 which allows you to enter a command
in the remote desktop software that gives your true console access.
 
Hi Mark!You wrote:.......The
only exception, like I said, is win 2003 which allows you to enter a command
in the remote desktop software that gives your true console access.
Click to expand...

Which command is this?Can you please tell me/us?
I have W2003 and have this double-session-problem.
I would be GREATFUL for help!
PEP
 
Back
Top