jianlinwei / connectbot

Automatically exported from code.google.com/p/connectbot
Apache License 2.0
0 stars 0 forks source link

Problem accessing RDP from Android client. #454

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Use freesshd on windows server 2003
2. Connect via ConnectBot
3. Try to connect using tunnel from Android RDP clients.

What is the expected output? What do you see instead?
I get Connection reset by Peer in the RDP client.
The SSH connection also gets dropped.

What version of the product are you using (you can see this by using Menu
-> About in the Host List)?
V1.7.1

What type of system are you trying to connect to?
windows 2003

If you are able to connect, what is the output of "echo $TERM", "uname -a",
and any other relevant information on the host?
Windows 2003 server with freesshd installed on it.

Please provide any additional information below.

I am trying to setup a secure connection to my network for Remote Desktop 
connectivity.

I am using the following components.

freesshd on a windows 2003 server
Connectbot
Xtralogic Remote Desktop Client.

Connectbot connects fine and I can log onto the servers command line.
Tunneling is set up as follows.

local - 3389
Remote <server ip>:3389

When I attempted to connect to the local 3389 port from the client, it states 
it's connecting and then I get the message 'Connection has been reset by peer'.

When I go back into Connectbot the SSH session has disconnected.

This happens if I'm connecting over 3g or via WiFi (Obviously changing the 
client address for the Remote/Local addresses).

There is nothing in the servers eventlogs, apart from a successfull login in 
the security one. Just a connect/disconnect in the freesshd logs.

Using the RDP Client over WiFi directly it connects flawlessly.

I have tried one other Client and I got the same error, does anyone have an 
idea on how to resolve this?

Also I don't seem to be able to type anything on the connect SSH connection.

This is on a GB ROM.

Original issue reported on code.google.com by mrpaulry...@googlemail.com on 1 May 2011 at 9:20