We have a Windows 2003 Terminal Server working perfectly, with clients able to connect externally - no problem. However, we have 1 client who cannot connect - just gets the 'cannot connect...' message back immediatley upon trying to connect.
He is running XP Pro, no software firewall...
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
He has an ADSL router, all working fine. Any other machine plugged in to his router has no trouble connecting to the TS. On the dodgy machine he can browse the web no problem. But he just cannot access the TS, no matter what client - RDC, TS client, webclient (tsweb)... It must be something on his PC?
well if he has got direct connection to the terminal server through router what do you mean by (just gets the 'cannot connect...' message back immediatley upon trying to connect) ? does he logon to this terminal server by entering user name , password , and domain name and he couldn't connect ?? does he configure his computer to work within domain or alone (no domain) just accessing the server by entering user name and password remotly??
Ok - he switches his PC on, gets his desktop etc. He can go on to the Internet no problem.
He clicks the 'Remote Desktop Connection', enters the IP address of the server, clicks 'connect', and BANG - he cannot connect, just gets a message box saying '....cannot connect to the server..... may be busy...'
No TS server logon. nothing. Just this error.
Any other PC works fine.
It is still possible to browse without all the required IP settings,
specifically Derault Gateway, and DNS
by using a the proxy settings int the web browser.
Is the default gateway set in his TCP/IP settings?
Can he trace the route to the RDP server?
start->run
cmd
tracert ww.xx.yy.xx
What does he happens when he telnets to the RDP Server RDP port?
telnet ww.xx.yy.xx 3189
(not sure about that port)
The response should be...
"Press any key to continue"
yes this is the point if TSWEB does not work that mean his computer has nothing to do with configuration , because TSWEB act as a remote server if it does not work then there is missed configuration with port mapping , please check back if he could connect to the internet he could see TSWEB site but he could not login . is that true ?? or either he couldn't see the web server ???
Looks like we have tried everything.
I suggest you repair your XP installation by doing an inplace upgrade an described in:
http://support.microsoft.c
This machine originally had a USB modem, which did not connect as I have stated. Then we've installed a router, other clients can connect from this users site, but not this particular PC. We've removed the USB modem and used the on-board ethernet card, still connot connect. The PC must have a fault. I will recommend that the user rebuilds his PC from scratch. I will lcose this question as unaswerable.
im actually having this exact same problem...
on client computer A you can access all different terminal servers except for a terminal server X
the other computers in the same network can access the terminal server X just fine
but as soon as computer A tries to access the terminal server X it recieves the message:
--------------------------
the client could not establish a remote connection to the computer
the most likely causes of this error are:
1) remote connections might not be enabled on the remote computer
2) the maximum number of connections was exceeded at the remote computer
3) a network error has occurred while establishing the connection
--------------------------
1) the remote computer has terminal services enabled and can accept connections from other computers on the network
2) the maximum number of connections was not exceeded because it is licensed for 10 users and only 1 user was trying to connect
3) network error has not occurred because it is able to connect to other terminal servers
OK....
Try this...
Reinstal Netowork protocals and cliet
riht click my network
right click on local area connection
remove microsoft client and all other clients
remove all other protocals except TCP/IP
right click on my comptuer
select properties
select hardware tab
select device manager
select network adapters
right click on the nic used by your pc to connect to the network.
right click on it
select uninstall
click on ok
Select action on the menu bar
select scan for hardware changes.
make sure your network settings (client and protocals) are a s before
try RDP to server
i wish that network protocols were the problem for this one, but i have tried all of this...
started off with a fresh preload from ibm
formatted drive and tried a full reload of volume licensed xp pro from msdn, still have the problem
tried a new nic card, still same problem
even tried a new hard drive, formatted it and installed xp pro, still same thing
i am having the client return the computer
I hate to ask a silly question because there are a lot of talented people looking at this, but are his user credentials cached? I read above that you had him try to log in as a new user...did it work? Did it update his default profile? I would verify that this machine is not set up to log in to TS as the user credentials that he is logging on to the local machine with. We had a similar problem with a contractor that was connecting to our servers and his home office servers.
Hi,
Has the PC been updated to SP2?
Is it automatically downloading the windows updates?
I recently had a client who couldn't maintain a citrix session over s/w VPN.
Turns out XP retrieving SP2 was killing the bandwidth to the point where a thin client session couldn't be maintained or established but browsing the web and downloading appeared as normal.
Appears Windows Update gives bandwidth back to IE but not thin clients.
Plus, (utterly guessing), all the restarts etc reset the SP download back to the start?
Try running the SP2 update?
on your 2k3 server do you the correct amount of cals, if so are they specified as per device or per cal? i would look there considering you have tried everything else. another common issue is a local GPO setting applied to the clients machine, but if this is just a standard install then that wpould not be the case.
as for the web client being greyed out, did the active x control load?
and if he can not telnet to port 3389 i would check to see if that port is restricted on that box.....
On his Home Router... you obviously have port 3389 open to his other home PC. What to his? On some home routers when you open a port (Forward) the port, it only goes to one internal client. What model router is at his home? Linksys? Netgear? If you could give me the make and model, I could look into it quickly and tell you how it SHOULD be configured.
I have a similar situation with some linksys router that you can only open a port once and forward it to one internal IP. Try this:
Jot down the IP of his other PC that CAN connect and work with TS. Shut off that PC.
Static configure the Problem PCs IP address to the one that the working PC had.
Then give it a shot.
If that works... Great. If not Let me know... I'll try to help more.
Has the computer got permission to connect on your server? go in your active directery users and computers and add it. i know it sounds simple but i missed that at first :s lol also is your server running a firewall? mine once ran one which blocked only one computer. if so, try removing it and see if it can connect
Although the questoin appears to be dead, I would just like to add my to cents worth to anyone else in a similiar situation. Did you ever check out the services that were running on the PC? With problems like this it is almost always a service issue, especially if a soft restore did not fix the issue, but a full restore did. Just a thought, hope it helps.
Lap, did you by chance replace the motherboard on the pc? because what i posted above about the client returning the pc. She went out and bought 3 more IBM desktop computers and they all have the same problem lol. tried a fresh install of xp, a new NIC, and a new HD. also tried a IBM labtop and it also refused connection.
To any one who has trouble connecting a client to a terminal server and is unable to.
See MS Article:
http://support.microsoft.c
This article talks about transferring a CAL from one pc to another, but I used it to delete the key when a client was unable to connect after being upgraded. The former client as a 98 machine upgraded to 2K.
We had a similar problem with a single xp pro client that could not connect via RDP to any server that it had previously connected. It also had problems with Microsoft's windows update....could not get it to install any new updates.....kept getting a failed message...so,
We register two dlls:
regsvr32 msxml3.dll
regsvr32 wuaueng.dll
then cleared the terminal server cache on the xp client machine under
C:\Documents and Settings\< user profile>\ Local Settings\Application Data\Microsoft\Terminal Server Client\Cache
and clear all info from IE, including files and history, etc
Had to reset default security levels also
rebooted xp client and was able connected to other servers using RDP and complete windows update.
dp
Business Accounts
Answer for Membership
by: novacopyPosted on 2004-06-30 at 08:07:57ID: 11436678
get the user to check his event view and also check the servers event viewer. they hold many secrets when it comes to terminal server :)