Terminal Services

  • Thread starter Thread starter new2computer
  • Start date Start date
N

new2computer

All,

Case1:
I install Terminal Services Client V5.00 (Build 2195) on Machine A
running Win2000 Pro with SP4. Next, I used Terminal Services Client to
connect to Machine B running Win2000 Pro with SP4. Then I received
error message,"The client could not connect to the Terminal server. The
server may be too busy. Please try connecting later."

I can ping from A to B and B to A.

Case 2:
Win XP Pro can used its remote feature to log into Machine B
successfully.

Does Terminal Services Client work in Case1? Please provide
instruction.
Thanks,
 
From http://ts.veranoest.net/ts_faq.htm

Q. How can I Remote Control my Windows 2000 Professional computer?

A. You can't do this with the Remote Desktop Protocol client. A
Windows 2000 Professional workstation can only be an rdp client,
not a host.
Use NetMeeting or VNC instead to connect to your W2K Pro desktop.

So no, your case 1 will not work. And I would say that your case 2
cannot work either, if you mean that machine B runs Windows 2000
Pro.
The machine you connect *to* (the host) must at least run XP, or a
server OS. You can connect *from* any Windows client.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
SQL troubleshooting: http://sql.veranoest.net
___ please respond in newsgroup, NOT by private email ___
 
Back
Top