Comments on: Secure Remote Desktop on Linux and Windows

By: Fat Pop Do Wop

Fat Pop Do Wop — Sat, 06 Jun 2009 20:42:29 +0000

Hi Ice Crash.

You can connect to a Windows server for command prompt only but not using RDP. Assuming you’ve installed and set up OpenSSH for Windows including setting up allowed users, you just use the ssh command with no tunneling and you’re at a command prompt. As follows: ssh -p 1357 username@external.address.of.remote.system
The -p 1357 assumes you’ve changed the firewall port for ssh to 1357 to prevent brute force or random name/password guessing.

If you’re going Windows to Windows, you need to use an SSH client such as PuTTY.

(Put the correct URL this time)

By: Can

Can — Mon, 08 Sep 2008 02:07:25 +0000

hi ice crash,
not sure, but there should be some rdp options for it

By: ice crash

ice crash — Tue, 02 Sep 2008 22:46:17 +0000

Autoselected keyboard map en-us
ERROR: Failed to open display:

there is some way how to connect to the rdp without showing the display? only to connect to the server, and some how to make the commands like you are in the command promt?

By: Bern

Bern — Sat, 19 Jan 2008 23:50:23 +0000

Tim is correct. If you have an SSH server just sitting on the Internet with port 22 wide opened, you become a target for automated brute force attacks. I noticed my server was being pounded with logins almost an hour every night. I switched the port to 6667 and haven’t had the problem since. It is also a good idea to deny root login from ssh as that is the easiest way for an attacker to compromise your system.

By: Can

Can — Mon, 10 Dec 2007 09:33:56 +0000

It is not the ssh port. It is the windows remote desktop port. The reason to change it windows doesn’t allow to open the port because it is also hosting the server of remote desktop.

By: Al

Al — Mon, 10 Dec 2007 05:31:43 +0000

Tim,
What’s a reason of changing SSH port? Those who want to see you SSH port, no matter what U set up, will nmap you server.

By: Tim Archer

Tim Archer — Mon, 09 Apr 2007 23:47:23 +0000

Agreed that the remote desktop connection is a great idea. I use it at work to centralize the development environment for all my developers. If you're using SSH you may want to change the default port it runs on to discourage automated password crackers from finding your SSH service and running brute force password attacks on it. I did a small write on changing the port at: http://timarcher.com/?q=node/46