Remote Desktop over SSH tunnel

I've got Cygwin/SSHd/RDP set up properly on a WinXP SP2 box and am able to connect fully via 2 XP/sp2 clients.

However, on the third XP/sp2 client system after we log on via SSH and try to connect to using RDC we get an error. Failure to connect system may be in use, blah blah blah.

I'm not at the console of this third client system but have been verifying her configuration via telephone. The server, myself, and she are in 3 different cities. I have been able to connect from home and work, she has not.

All clients are XP/sp2 build 2600
All Putty clients log on properly and tunnel settings have been verified.

I connected with my client and checked the Event Viewer app logs of the server; after showing the problem clients SSH connect it shows the following error when they try to RDC:

Code:

Event Type:	Error
Event Source:	sshd
Event Category:	None
Event ID:	0
Date:		11/6/2005
Time:		8:52:23 PM
User:		NT AUTHORITYSYSTEM
Computer:	EDITED
Description:
The description for Event ID ( 0 ) in Source ( sshd ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: sshd : PID 3640 : error: connect_to local host: unknown host (no address associated with name).

Help interpreting this error log would be appreciated.
Further info regarding my setup has been uploaded here:
http://members.dslextreme.com/users/claytonmanning/remote/README.html

 

I think I may have figured it out:
"error: connect_to local host: unknown host "
it didn't make sense to me for the system to think of itself as
an unknown host. Then I noticed the space.

localhost is should be one word. I'm guessing that she has "local host "
not "localhost" in either Putty's tunnel configuration, or Remote Desktop
Connection.

I'll find out tommorow

 

Yup that was the problem.

Thanks anyway

 

Thanks for the update and a very nice pickup on the problem. That one could easily have been missed.