Remote Desktop Disconnected

[Guest]

The error message is "The remote computer has ended the connection."

The computer I am trying to connect was purchased a month ago with Windows
XP Home Edition. Upgraded to XP Professional SP2 this past weekend. It has a
static IP: 192.168.2.*. Remote Desktop is turned on. Windows Firewall
Exception created for Remote Desktop. Port is 3389.

I am trying Remote Desktop on another machine on the network. After I click
on the Connect button, the small tab will show up on top of the screen, but
immediately the above error will show up.

I have been reading the search results from the Internet. Tried all
suggestions, but not successful. Searched Microsoft Knowledge Base and
Technet, and I could not find any solution.

This is my last resort. Would appreciate if somebody can help.

Thank you in advance.

 

[Sooner Al [MVP]]

See this page for troubleshooting help...

http://theillustratednetwork.mvps.org/RemoteDesktop/RemoteDesktopSetupandTroubleshooting.html

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the mutual
benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...


"Perplexed not Confused Yet" <Perplexed not Confused
(e-mail address removed)> wrote in message
news:[email protected]...

 

[Guest]

Thanks for the response.

I have read the article before I made the original post, and just read it
again. It did not help me solve the problem.

I could use Remote Desktop to connect to the other machine, but not vice
versa.

 

[Guest]

Al,

I have been reading off the Internet. It seems quite a few people are having
similar problems, but I am not seeing any solution addressing this issue.
Most suggestions are directing to the URL you gave.

Is there any Registry entry that is missing or corrupt to prevent a remote
client to connect? All relevant ports are enabled to pass through the
Firewall, which in this case is 3389. I even disable the Firewall to test,
but the same thing happened.

Would appreciate if you can provide more suggestions that I can try.

 

[beb]

First you have to list what you have tried.

If you have tried everything then you should be able to say if the port is
open. If you are not getting any event in the log then backup and repair and
if that don't work reinstall.

"Perplexed not Confused Yet"

 

[Sooner Al [MVP]]

You might try this...

1. Re-registering Remote Desktop using the command line that
follows...Reboot the PC after doing this...

regsvr32 remotepg.dll

2. Doing a "repair installation". Note the warnings on the page...

http://michaelstevenstech.com/XPrepairinstall.htm

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the mutual
benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...


"Perplexed not Confused Yet"

 

[Guest]

1. Remote Desktop was turned on from the Remote tab on the System Properties.
"Allow users to connect remotely to this computer", - the checkbox is
checked.

2. Remote Desktop is in the Exception tab for the Firewall. Port 3389 - the
checkbox is checked.

3. Used the PortQueryUI tool. Typed in the address of the machine, and
manually input query port, the port number, for example: 192.168.2.13 and
port 3389. The query came back with
"IP address resolved to mymachinename".
"TCP port 3389: LISTENING"
return code 0x00000000.

4. The machine has a static IP, like the above 192.168.2.13. I can ping it
on the network.

5. I temporarily disabled the Firewall, and it didn't help.

6. I created a MAC address filter in the router, which is a D-Link, so that
only the MAC addresses of all my desktops and laptops can connect to the
network.

7. I have McAfee installed on the machine.

8. I do have Spybot S & D installed and SpywareBlaster installed.

9. All the patches for Windows XP pro has been applied to the system from
Microsoft.

10. I am in the process of trying to connect back to the machine using the
SSH tunnel, but without the ability to connect to the machine on the local
network, this step will have to postponed before I figure out why I cannot
connect to it on the local network.

11. I have Cygwin SSHD installed and running on the system. Putty was also
installed.

Items 10 and 11 can be ignored right now before I can figure out why I could
not even using Remote Desktop on the local network.

12. The following websites that I have been referencing:

http://www.engr.wisc.edu/computing/best/rdesktop-putty.html
http://www.geek.com/news/geeknews/2003Aug/fea20030828021469.ht
http://theillustratednetwork.mvps.org/RemoteDesktop/RemoteDesktopSetupandTroubleshooting.html
http://pigtail.net/LRP/printsrv/cygwin-sshd.html
http://ncyoung.com/entry/389

Hope this can give you some idea. Thank you.

 

[Sooner Al [MVP]]

Hey... You forgot my SSH-RDP page...

http://theillustratednetwork.mvps.org/RemoteDesktop/SSH-RDP-VNC/RemoteDesktopVNCandSSH.html

Note that I now use CopSSH as the server, because its being actively
maintained, and Tunnelier, because it has built-in support for RDP, with a
2048-bit RSA private/public key pair (w/Strong Pass Phrase) versus a
password for authentication. The ssh-keygen program, that is included with
CopSSH, now creates a 2048-bit key by default. You still need to specify the
type of key using the -t switch...

http://www.itefix.no/phpws/index.php?module=pagemaster&PAGE_user_op=view_page&PAGE_id=12
http://www.bitvise.com/tunnelier.html

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the mutual
benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...


"Perplexed not Confused Yet"

 

[Guest]

Al,

I will try it out this evening, and keep you posted. Thanks for the
suggestions.

 

[Guest]

Sorry, Al. Forgot to list it.

I did read this page. Thanks. Interesting thing, though. Once I installed XP
Pro SP2, I could not find the SSHD service in the Services list any more. Is
there any way I can get it back? Right now, I have to start through command
line everytime I log onto my machine.

 

[Sooner Al [MVP]]

Talking about CopSSH? On my XP Pro box services list its listed as "Openssh
SSHD". I guess you could try uninstalling then reinstalling the software...

I beginning to think you should have simply done a full install versus the
upgrade when you moved from XP Home to XP Pro. By that I mean wiping the
preexisting XP Home installation then installing XP Pro. Its an option you
can do with the XP Pro Upgrade CD...

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the mutual
benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...


"Perplexed not Confused Yet"

 

[Si]

Out of interest, did the repair install fix this problem?

I have the same problem with my work laptop.

"Perplexed not Confused Yet"