Remote Desktop just stopped working

TRMNTR · External Since: Dec 06, 2006 Posts: 2

I had my computer, modem and router configured for Remote Desktop and it has
been working fine until last Friday when it just stopped working.

I have recently downloaded the update for 6.0 from Microsoft but it quit
working prior to me downloading the new version.

After the download the error I get when trying to connet is: "This computer
can't connect the to the remote computer. Try connecting again. If the
problem continues, contact the owner of the remote computer or your network
administrator."

I played around with some settings but nothing seemed to work. All the
settings have been set back to the way they were when it worked fine.

Both computers have XP Pro and I have Norton Antivirus 2006. All is the same
when it was working.

This just happened one day. Don't know what happened. Please help. Thanks.

Sergey Kuzin [MSFT] · External Since: Dec 06, 2006 Posts: 4

Let's first try to diagnose the problem.

On the server machine open a cmd window and run "qwinsta".
Do you see the following line: "rdp-tcp 65536 Listen rdpwd"? If not, your
server is not listening for Remote Desktop connections. You need to re-check
the server's configuration (or maybe reboot the machine).

Can you ping the server machine from your client machine?
Also, check if your server's computer name resolves to a correct IP address
on your client machine. Find out your server's IP address by running
"ipconfig" on the server and try to use it instead of computer name when
making a Remote Desktop connection.

Can you connect to IP port 3389 on your server machine from the client
machine? (I usually use telnet for this check).

--
This posting is provided "AS IS" with no warranties, and confers no rights.

"TRMNTR" <TRMNTR.RemoveThis@discussions.microsoft.com> wrote in message
news:BFFFC01C-0B67-449B-8EB9-2954A38BA336@microsoft.com...
>I had my computer, modem and router configured for Remote Desktop and it
>has
> been working fine until last Friday when it just stopped working.
>
> I have recently downloaded the update for 6.0 from Microsoft but it quit
> working prior to me downloading the new version.
>
> After the download the error I get when trying to connet is: "This
> computer
> can't connect the to the remote computer. Try connecting again. If the
> problem continues, contact the owner of the remote computer or your
> network
> administrator."
>
> I played around with some settings but nothing seemed to work. All the
> settings have been set back to the way they were when it worked fine.
>
> Both computers have XP Pro and I have Norton Antivirus 2006. All is the
> same
> when it was working.
>
> This just happened one day. Don't know what happened. Please help. Thanks.

Ankur · External Since: Dec 07, 2006 Posts: 1

Hi,

I am having the same problem described here and I have run the tests you
have advised. The server is listening (desktop PC running XP Pro SP2).

I am also able to telnet 192.168.0.1 or HomePC 3389.

BUT, when I try to use the Terminal Services Client (this is the latest
version from Windows Update) I enter the username ans password (both my PCs
have the same username and password and the accounts on both PCs belong to
the Administrators group), and then I get a message saying Unable to connect.
The messages vary, sometimes advising me that I'm running low on virtual
memory, other times to simply "try again".

I must emphasise that this was working fine to and from both PCs until the
RD client was updated via windows update.

My machines are Windows XP Pro SP2 and Windows XP MCE 2005 SP2.

Any advice will be greatly appreciated!

Thanks

"Sergey Kuzin [MSFT]" wrote:

> Let's first try to diagnose the problem.
>
> On the server machine open a cmd window and run "qwinsta".
> Do you see the following line: "rdp-tcp 65536 Listen rdpwd"? If not, your
> server is not listening for Remote Desktop connections. You need to re-check
> the server's configuration (or maybe reboot the machine).
>
> Can you ping the server machine from your client machine?
> Also, check if your server's computer name resolves to a correct IP address
> on your client machine. Find out your server's IP address by running
> "ipconfig" on the server and try to use it instead of computer name when
> making a Remote Desktop connection.
>
> Can you connect to IP port 3389 on your server machine from the client
> machine? (I usually use telnet for this check).
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> "TRMNTR" <TRMNTR.RemoveThis@discussions.microsoft.com> wrote in message
> news:BFFFC01C-0B67-449B-8EB9-2954A38BA336@microsoft.com...
> >I had my computer, modem and router configured for Remote Desktop and it
> >has
> > been working fine until last Friday when it just stopped working.
> >
> > I have recently downloaded the update for 6.0 from Microsoft but it quit
> > working prior to me downloading the new version.
> >
> > After the download the error I get when trying to connet is: "This
> > computer
> > can't connect the to the remote computer. Try connecting again. If the
> > problem continues, contact the owner of the remote computer or your
> > network
> > administrator."
> >
> > I played around with some settings but nothing seemed to work. All the
> > settings have been set back to the way they were when it worked fine.
> >
> > Both computers have XP Pro and I have Norton Antivirus 2006. All is the
> > same
> > when it was working.
> >
> > This just happened one day. Don't know what happened. Please help. Thanks.
>
>
>

TRMNTR · External Since: Dec 06, 2006 Posts: 2

I ran "qwinsta" and it gave me: "rdp-tcp 65537 Listen rdpwd" instead of what
you said. How do I change it to the 65536. I have tried the restart thing and
that didn't work.

"Sergey Kuzin [MSFT]" wrote:

> Let's first try to diagnose the problem.
>
> On the server machine open a cmd window and run "qwinsta".
> Do you see the following line: "rdp-tcp 65536 Listen rdpwd"? If not, your
> server is not listening for Remote Desktop connections. You need to re-check
> the server's configuration (or maybe reboot the machine).
>
> Can you ping the server machine from your client machine?
> Also, check if your server's computer name resolves to a correct IP address
> on your client machine. Find out your server's IP address by running
> "ipconfig" on the server and try to use it instead of computer name when
> making a Remote Desktop connection.
>
> Can you connect to IP port 3389 on your server machine from the client
> machine? (I usually use telnet for this check).
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> "TRMNTR" <TRMNTR.RemoveThis@discussions.microsoft.com> wrote in message
> news:BFFFC01C-0B67-449B-8EB9-2954A38BA336@microsoft.com...
> >I had my computer, modem and router configured for Remote Desktop and it
> >has
> > been working fine until last Friday when it just stopped working.
> >
> > I have recently downloaded the update for 6.0 from Microsoft but it quit
> > working prior to me downloading the new version.
> >
> > After the download the error I get when trying to connet is: "This
> > computer
> > can't connect the to the remote computer. Try connecting again. If the
> > problem continues, contact the owner of the remote computer or your
> > network
> > administrator."
> >
> > I played around with some settings but nothing seemed to work. All the
> > settings have been set back to the way they were when it worked fine.
> >
> > Both computers have XP Pro and I have Norton Antivirus 2006. All is the
> > same
> > when it was working.
> >
> > This just happened one day. Don't know what happened. Please help. Thanks.
>
>
>

blando · Joined: Dec 10, 2006 Posts: 2

I am having the exact same problem. Everything worked fine until the 6.0 update went through. Now I can't connect to anything. I tried tweaking all the settings: always allow, no TS server, etc. and nothing. This is terrible.

blando · Joined: Dec 10, 2006 Posts: 2

It was a conflict with zonealarm. Will need to explore that more...

evotunedscc · Joined: Dec 10, 2007 Posts: 1

Any solution to this? This occurred to me about a month and a half ago. I spent days upon days trying to resolve the issue; from turning off all unnecessary startup services, to swapping onboard NICs that I was using to confirm there wasn't a hardware issue, to messing around with registry settings I had no luck at fixing this. I installed XP as a dual boot and Remote Desktop worked to XP. Seemed like after an update Vista Remote Desktop just stopped working.

I had called Microsoft and talked to their tech support for 2 days and got nowhere with this. The case is still opened but I had to stop fooling with it because of things going on with school and work. Please let me know if you get this fixed.

Thanks:)

javig · Joined: Jan 08, 2008 Posts: 1

I had the same problem about a week ago and the suggested info above didn't work for me. All I did to fix the issue was go to windows update > custom > Software optional > and installed the Remote desktop Connection (terminal Services Client 6.0) for windows Xp (kb925876). Here is the link

http://www.microsoft.com/downloads/details.aspx?FamilyID=26f11f0c-0d18...06-abcf

jimdill · Joined: Feb 02, 2009 Posts: 1

I had the same problem, remote desktop suddenly stopped working. I found a fix: in Computer Management > Services, the entry for Terminal Services showed it was not started, and was set to Manual. I started it and changed to Automatic.