• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1116
  • Last Modified:

Microsoft Windows 2003 Remote Desktop has stopped working

I have a client that has been using Remote Desktop with Windows 2003 Server for about two years now very successfully. Two days ago, in the afternoon, Remote Desktop stopped working, in that it began saying "This computer can't connect tot he remote computer".
I initially thought it was the update to the end users machine, a Microsoft Update, but I have checked on different machines with the same result.

If I open up remote desktop on the server itself and make it connect to itself it of course works great.

I have looked for changes but I just don't see anything glaring at me. If anyone has come across this, or if you can give me things to check I'll be happy to check them and give you what I have.

The clients are down until I get this fixed, so it is worth the 500 points as it is a down system.

Thank you everyone!!!

Shon
0
sscottincanyon
Asked:
sscottincanyon
  • 8
  • 6
  • 2
  • +3
5 Solutions
 
tboy6423Commented:
We had a silmilar problem and it had to do with a microsoft update on the users machines...if you use Windows Firewall (even if you don't ) check this first, the update wiped out all of our exceptions so Remote desktop and File sharing was disabled. You may want to start there, I cannot remember what update it was but re-checking the exceptions Remote Desktop and File Sharing worked.
0
 
gblundCommented:
also the sp3 to xp disables the function in ie. you should go in the ie, functions "administer add on programs" and choose to activate the Microsoft RDP Client control.
0
 
sscottincanyonAuthor Commented:
Hey tboy:
I also experienced this with another client, and looked at it just to make sure because it did through me off last time. I just checked on my machine and the firewall is off and the exceptions are correct.

Thank you :) I hope to see more solutions coming,

Shon
0
Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

 
sscottincanyonAuthor Commented:
GBlund, I checked this and everything is as you said it should be.

Just to add on, I can connect to any other clients RDP/Windows 2003 server without issue, it is just this one that rejecting the connection.

If you would like to try it from your machine, e-mail me and I will send you the credentials so you can verify.

Thank you,
Shon
0
 
tboy6423Commented:
Is the Firewall still running in services? or is it disabled and stopped?
0
 
speshalystCommented:
On the Remote Machine.. verify if  the "allow remote users to connect remotely to this computer"  has been disabled by any chance
you can get there by right-mouse Mycomputer>Properties>remote
 
 
0
 
sscottincanyonAuthor Commented:
These are all great suggestions, please keep them coming!!!

I have checked the remote computer and it is still enabled for remote connections and control.

Tboy: The firewall is not running at all.

Thank you everyone!!
SHon
0
 
speshalystCommented:
0
 
sscottincanyonAuthor Commented:
The version on this client is 6.1, to make sure I ran the update from the link you supplied Tboy and it stated that the version I had was newer than the one being installed.

Shon
0
 
sscottincanyonAuthor Commented:
Speshalyst: Thank you for the additional link within the exchange, I am currently using administrator, RDC port 3389 is open on the routher. and remote access is enabled. I will certainly check out remote desktop on the web that was mentioned there. However, since I have all those set correctly too, sadly, that was not the solution.

Again, thank you for keeping them coming, I know there is a solution it is just hitting the right one.

Shon
0
 
tboy6423Commented:
Is .net 3.0 installed on that client?
0
 
tboy6423Commented:
0
 
sscottincanyonAuthor Commented:
Just to restate, I may not be communicating clearly. On this client I can connect to any and all other Remote Desktop Connection, it is just this one in particular. With this one connection, I cannot connect to it from any other computer.

I hope that makes more sense,

Shon
0
 
tboy6423Commented:
yep understand perfectly..you can connect out, but cannot connect RDP to that particular client. it's strange...I will see what else it may be..
0
 
ChiefITCommented:
SP2 has a little quirk that requires two reboots before RDP will work again. Reboot the server.
0
 
JOSHUABTCommented:
Check if you have installed Terminal server component.
Sometimes, people install TS and enjoy 120 days grace period and forget about it until it expires.
If you have installed, you have to either purchase the TS CAL license or uninstall TS component.
If will go back to RDP server with default 2 licenses.

Hope it works.
0
 
ChiefITCommented:
There is a couple quirks with SP2 and RDP. One of them is TS stops listening on the default port. Here you go, you might want to check this out.

http://www.lan-2-wan.com/2003-SP2.htm
0
 
sscottincanyonAuthor Commented:
It turns out that I had to replace the router. I thank everyone for their input.

Have a great night,

Shon R. Scott
0
 
sscottincanyonAuthor Commented:
I know that you all had some very valuable input and I don't like just closing a question, so I am awarding you equally with a grade of A. Moderators, if this isn't a usual practice and isn't acceptable please let me know and I/you change it?

Thank you for all the help!!
Shon R. Scott
0

Featured Post

Take Control of Web Hosting For Your Clients

As a web developer or IT admin, successfully managing multiple client accounts can be challenging. In this webinar we will look at the tools provided by Media Temple and Plesk to make managing your clients’ hosting easier.

  • 8
  • 6
  • 2
  • +3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now