Question Locked

Windows XP to Windows 2000 Server Terminal Server connection problem

0 helpful
13 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

connect xp pro to windows 2000 terminal server - admin mode
Hi All, HELP URGENTLY NEEDED! I have a windows 2000 server SP2 server with terminal server installed in administration Mode. when I try to connect to it using windows xp SP2 remote desktop it say:"The client could not connect to the remote computer. Remote connections might not be enabled or the computer might be too busy to accept new connections. It is also possible that network problems are preventing your connection. Please try connecting again later. If the problem continues to occur, contact your administrator."

Tried several configurations, disabled firewalls on both computers, but still I get this error, anyone know how to solve this problem? Any help will be appreciated! Thanks.

13 replies

by ge0rgei

right click on "my computer" select "remote" tab and enable remote desktop on the server

by bribenart

Right clicking on my computer does not have the remote desktop feature, ge0rgei.

by bribenart

Darre11, it is not a pre-windows xp problem. the problem is connecting windows xp using remote desktop to terminal server which is installed on a windows 2000 server machine. When I try to connect I get an error message.

by darryl~

Sorry about that, I didn't read it close enough.
Terminal Services Remote Administration Mode only allows for 2 concurrent administrator connections....you are attempting to log in with an administrator account on the Windows 2000 server...correct? Is the Windows 2000 Server sitting idle (nobody logged into it)?
Also, someone else asked this as well....how come you haven't installed SP4?

by pshiflet-24

Can you connect to the server using Remote Desktop when you are on the same network/LAN as the server? If so, can you do so with both the IP address and the server's FQDN?

by bribenart

The problem is that I can't connect through LAN, both the XP and the 2000 server(it's also a domain controller) machines are on the same LAN. I can do file sharing, they are on the same domain, chrisianshiflet.

by pshiflet-24

I assume you have tried to connect using both the LAN IP address as well as the computer's name. Have you tried connecting to it from a different computer than the one you are having issues with? What type of firewall are you running on the Win2K server? Why is the server still on SP2? Updates included in SP3 & SP4 may fix this issue. Since it is a domain controller, have you verified that the Domain Security Policy has a user group, usually Administrators, in the "Allow to log on to Terminal Server" policy? If that policy is empty, it may respond as if Terminal Services is disabled.

Let me know what you can. Thanks.

by bribenart

It is clearly to me that a maximum of two concurrent connections are allowed using Administration Mode. Also I am using an administrator account of the windows 2000 server machine, which is a domain controller account, because I turned this machine into a domain controller of the network. The computer from which I am trying to login to the terminal server is a member of the domain. The windows 2000 server computer is not sitting idle at the point when I am trying to login from the remote computer, at this point I already logged in to windows using the same administrator account.

I haven't thought of installing SP4 yet, has SP2 have a bug in it which prevents the logging into terminal server?

by bribenart

Yes, christianshiflet, I have tried both, LAN IP address and the terminal server computer name, they didn't work. I have tried a second computer on the network and I get the same error, this computer also has windows xp SP2 installed. I have not installedany firewall on the Win2K server, the only security program installed is Norton Antivirus coporate 9 edition. I haven't thought of updating to the latest updates, would this really be the problem?

by bribenart

I forgot, I haven't tried logging in using the terminal server LAN IP earlier, I thought I did, but that was something else. I tried it yesterday and it worked, thank you very much christianshiflet.

I wonder why it works with the ip address, but not with the terminal server computer name. When I browse for terminal server names using the RDP client the name of the server appears in the dialog box, but when I select it and try to connect to it, it does not work. I would like to know why. Any ideas you guys?

by pshiflet-24

Well, being able to RDP to the IP address but not the computer name usually signifies a DNS problem. If you are running DNS on the Domain Controller verify that the appropriate A/Host records exist under Forward Lookup Zones. Let me know if that helps. Thanks.

This discussion is closed to new replies.