Windows Server 2008 Remote Desktop Problems

Question

I've got an installation of Windows Server 2008 (not R2), and I was previously running Remote Desktop via the Terminal Services 120 day free license. That has since expired, and I un-installed the Terminal Services Role, I also believe that you are able to run two instances of remote desktop without needing to pay for the terminal services licence (all I really want is one).

I am unable to remote desktop to the machine, and am not sure where the problem lies... I know that the firewall has been turned off (and port 3389 is open), and I've enabled Remote Desktop under the system properties.

I am using the Remote Desktop Connection for Mac client from within the network, and the message I get is: "You were disconnected from the Windows-based computer because of network problems". When I try using "telnet [server IP] 3389" the response is "Trying [server IP]... Connection refused, unable to connect to remote host". I never make it to a login screen.

Can anyone help point me in the right direction to figure out how to get the Remote Desktop on the machine?

Solution 1

In Windows Server 2008 (not R2) the service is called Terminal Services, not Remote Desktop Services (that was changed in R2). If that is started, make sure terminal services connections are allowed in system properties, make sure your firewall allows TCP port 3389, and make sure the RDS role is not installed.

Solution 2

Remote Desktop Services is not called Remote Desktop Services in W2K8, it's called Terminal Services. Check for the existence of the Terminal Services service and make sure it's started.

User session host mode and management mode both use the same underlying service and protocol; TS service in W2K8 or RDS service in W2K8R2 and the RDP protocol, the difference is in the mode of operation and in the license requirements.

Solution 3

When you attempt to RDP into the server, what do you get as a response?

Does it say it cant find an RDP (Terminal Server) or does it get in and not take your username and password?

I only ask this because you never actually said and nobody else asked it. Jason and Joe are both right about the requirements though! ;)

Also, for arguments sake, are you RDPing from within your network or outside, if from outside, try from inside to see if you get the same results.

HTH

Comments

[Zoredache]

So what is the actual problem? Are you not able to RDP into the machine or just that you aren't seeing something in the services window?

[Brett]

Well, I can't RDP to the machine, and I assumed it was because I couldn't find RDP in the services window, but thanks to the answer, I'm realizing there is in fact a much larger difference between RDP in W2K8 and W2K8R2

[joeqwerty]

The only difference is in the name. Both use the same underlying technology. One is called Terminal Services (W2K8) and the other is called Remote Dekstop Services (W2K8R2), other than that they're the same thing.

[joeqwerty]

Curses. We posted very similar answers at the same time... Well played, Mr. Berg. :)

[Jason Berg]

Well played yourself. How could I not +1 this? I'm pretty sure I'd say the exact same thing :-)

[joeqwerty]

You did say the same thing. It's like we're brothers from different mothers! ;)

[Brett]

So, two points of confusion: 1) Can I use Remote Desktop/Terminal Services without a license (beyond the 120 day trial, and for 2 or less users)? 2) What Roles do I need installed to do that?

[Brett]

I've made sure that the system properties allow connections, and the firewall allows connections, when you say "RDS role not installed", do you mean Terminal Server role? I am at a loss for what else to try in order to get it working...

[joeqwerty]

You can use Remote Desktop for Administration with no TS licenses. This does not require that the TS role is installed, the only things required are to have remote desktop connections enabled (System Properties|Remote tab), that the TS service is running, and that the appropriate user is a member of the local Remote Desktop users group. Take note that what you're asking is a nuance of the licensing requirements/limitations... using Remote Desktop for Administration to connect to the server and run productivity applications (MS Office, etc.) is probably a violation of the EULA.

[Jason Berg]

Yes. The terminal server role. That should NOT be installed. If it is, it requires a licensing server. If it isn't, the terminal services service is still installed, but running in remote administration role.

[Brett]

So, I believe I have the exact set-up that you're suggesting, and I am still unable to connect to the server remotely. I've tried both Remote Desktop, and using telnet on port 3389. Any suggestions?

[Brett]

I'll update the question with answers to your questions, thanks for chiming in!

[joeqwerty]

Run netstat - a -n from a command prompt and verify that the server is listening on port 3389.

[Jason Berg]

The Terminal Server role is what distinguishes it. Can you telnet to port 3389 on your server?

[Jason Berg]

Sorry...clarification...can you telnet to port 3389 from the server to 127.0.0.1?

[Brett]

I ran netstat -a -n and saw a bunch of ports (including 21 and 80), but did NOT see 3389. So its currently not listening, how do I make it listen if the service is started?

[Brett]

I ran that, and just as from another machine on the network, "Connection refused". I did as joeqwerty requested and ran netstat, and saw that the machine was not listening on port 3389, but the service is running... any thoughts?

[Jason Berg]

Did the port get changed? Check HKLM\System\CurrentControlSet\Control\TerminalServer\Winstat‌​ions\RDP-TCP\PortNum‌​ber

[joeqwerty]

Try rebooting the server, then check the service to make sure it's running, then check to make sure that remote connections are enabled, then check the Windows firewall, then check the event log for any clues.

[Brett]

I checked the port number, and it is still 3389.

[Brett]

Just checked all that and it looks as it is supposed to :/

[Lemuel]

This is strange, you have everything set up correctly as I can tell. For arguements sake, disable the windows firewall long enough to do a test with netstat as well as telnet and a test RDP session and see what you get. If it works you know something is wrong in the firewall. Otherwise it's windows itself. BTW, when you RDP are you using the Servers name or the IP?

[Brett]

I've actually had the Firewall disabled for quite some time (and on top of being disabled, I've opened the RDP port). I am using the Server's IP rather than name, and I regularly share drives with the server via IP/FolderName