User:Mjb/Setting up Remote Desktop

From Offset
< User:Mjb
Revision as of 12:10, 23 April 2013 by Mjb (talk | contribs) (+Network Level Authentication detail)
Jump to navigationJump to search

It's easy to set up Remote Desktop so that you can control your Windows computer from another computer.

Compatibility

You can't set up Remote Desktop on Windows 7 Starter. You can use Windows 7 Starter as a client, though.

Basic setup

  1. Go to Remote Settings (it's in the System Properties, e.g. right-click on My Computer and go to Properties).
  2. Choose one of the "Allow connections..." settings for Remote Desktop. If you choose Network Level Authentication, it will probably lock out non-Win7 clients (see below).
  3. Click Apply or OK.

That's all you need to get it going. Try logging in from a Remote Desktop client elsewhere.

Extra security

Require Network Level Authentication

In the Remote Settings configuration, you choose whether only allow connections from computers running Remote Desktop with Network Level Authentication, which is a feature of Remote Desktop Client 6.0 and up. It generally means that the client must be running on Windows 7 and up. However, Microsoft makes updated clients available for Vista and XP, so you can still connect from those OSes if you want. To get Network Level Authentication working in the client on XP, you have to enable the CredSSP service.

After applying the April 2013 update KB2813347 (Remote Desktop cleint update for vulnerability MS13-029), I could no longer connect a client from Windows 7 Starter to a server on Windows 7 Professional without reconfiguring the server to not require Network Level Authentication. I had installed the update on both systems. I haven't yet investigated further.

Change the listening port

For extra security, I suggest changing the listening port. Details are in a Microsoft Knowledge Base article, but basically you just run Regedit, go to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\PortNumber and enter the port number. The change will take effect after the next reboot. Don't forget to create a custom rule in Windows Firewall to allow TCP traffic inbound on that port. You can disable all the other Remote Desktop rules; they are for the default port. Of course, you will need to make sure that you include the port number after the computer hostname in the client's logon settings, like the.remote.host:12345.

Temporarily prevent login after too many failed attempts

I also suggest setting an account lockout threshold in the Local Group Policy Editor > Local Computer Policy > Computer Configuration > Windows Settings > Security Settings > Account Policies > Account Lockout Policy. When you enter a threshold, it will suggest 30 minutes for the other values; this is good. This will make brute-force attacks difficult. I set mine to 5, which should be enough retries for a real person who just can't remember or is fat-fingering their password.