zillah
Premium
join:2005-01-30
NewZeland
2 edits | Remote Desktop via SSH and error message
»theillustratednetwork.mvps.org/S···SSH.html
I tried to configure SSH server (let us call this PC : Server PC) and putty (let us call this PC: Client PC) exactly as described in the link above (step by step).
I have got two PC with XP Profe OS,,,,one PC (Where SSH server is installed) is on cable modem and other PC (where PUTTY is installed ) is on dialup.
I was able to establish a SSH Tunnel but I could not access RDP,,,,I do not know where was the problem.
Port forwarding is okay no problem otherwise I would not be able to establish SSH tunnel
from PC where PUTTY is installed (let us call it Client PC) when I tried to type in the ip address (for the PC where SSH server is installed let us call it Server PC) with source port number (for Client PC) I received the below error message :
»img687.imageshack.us/i/errormessagessh.jpg/
Any idea what troubleshoot should I perform ? |
|
Frodo
join:2006-05-05
Lees Summit, MO | Try using IP 127.0.0.2. I haven't used RDP for years now, but I think that'll fool the computer.
The way I went was Stunnel -> RDP, using certificates to authenticate. |
|
zillah
Premium
join:2005-01-30
NewZeland
3 edits | reply to zillah
quote:
Try using IP 127.0.0.2. I haven't used RDP for years now, but I think that'll fool the computer.
Thanks using ip address (127.0.0.1) solved the problem ,,,,appreciate your hint
I did try 127.0.0.1:3390 and it did work.
Although I did try 127.0.0.2:3390 it did not work
Then after your advice I did google I found this
»www.engr.wisc.edu/computing/best···tty.html
quote:
Start your Remote Desktop program as usual. Instead of entering the name of the computer that you want to connect to, you must type in the address and port that Putty is forwarding to. Depending on your operating system, this may be different from what is shown in the example:
Windows XP: 127.0.0.2
Other Windows Platforms: 127.0.0.1
|
|
Frodo
join:2006-05-05
Lees Summit, MO
| I think I had trouble with 127.0.0.1 - it thought I was logging on to RDP from the same computer, which, in a sense, I was. So, I went 127.0.0.2. I had to load a hotfix from Microsoft to get the rest of the 127s to work, but I had thought that hotfix would have rolled out subsequently with windows update.
Haven't played with it for a couple of years now. |
|
SoonerAl
Old Enough To Know Better
Premium,MVM
join:2002-07-23
Norman, OK
| reply to zillah
If the SSH client PC is running XP SP2 you need to apply this patch from MSFT that fixes an issue using the 127.0.0.1 loopback address.
»support.microsoft.com/default.as···s;884020
»theillustratednetwork.mvps.org/S···_session
That issue has been fixed in SP3 and later versions of Windows, ie. Windows 7 and Vista.
Once you connect using to the SSH server using PuTTY use the address form localhost:port-number as illustrated on that page. This presumes you have port forwarding setup correctly in the PuTTY client.
»theillustratednetwork.mvps.org/S···re_PuTTY
--
"When all else fails, read the instructions..."
MS-MVP Windows Desktop Experience |
|
zillah
Premium
join:2005-01-30
NewZeland
| reply to zillah
quote:
If the SSH client PC is running XP SP2 you need to apply this patch from MSFT that fixes an issue using the 127.0.0.1 loopback address.
Both PCs (server and client) running XP Prof with SP3.
quote:
PuTTY use the address form localhost:port-number as illustrated on that page.
Link suggests either to use private ip address for the localhost or a host name. |
|
SoonerAl
Old Enough To Know Better
Premium,MVM
join:2002-07-23
Norman, OK
1 edit | said by zillah  : quote:
If the SSH client PC is running XP SP2 you need to apply this patch from MSFT that fixes an issue using the 127.0.0.1 loopback address.
Both PCs (server and client) running XP Prof with SP3. quote:
PuTTY use the address form localhost:port-number as illustrated on that page.
Link suggests either to use private ip address for the localhost or a host name. No, see the screen shot...
localhost = 127.0.0.1
You would use the host name or private IP address when setting up the forwarding. See the other screen shot.
--
"When all else fails, read the instructions..."
MS-MVP Windows Desktop Experience |
|
zillah
Premium
join:2005-01-30
NewZeland
| reply to zillah
quote:
No, see the screen shot...
You are 100% right, thanks for this observation,and help.
I got confused with bold prase in the below quote
quote:
To configure port forwarding for the example network click on Tunnels and for Remote Desktop enter a Source port of 3390. Enter a Destination IP or name and port number of 3389 using a colon separator character. An example is for a Remote Desktop session to the PC Ashtabula. Tap the Add button. Repeat for additional Remote Desktop host PCs. Use a different Source port for each additional Remote Desktop host PC.
|
|
