Remote Desktop not working / Terminal Server

November 21, 2011 at 11:10:51
Specs: Windows 7
Hi all,

I have a problem with a Windows 2003 R2, Service Pack 2, Datacenter Edition Server.
We used RDP to this server only for administrative purposes until today and therefore did not install the Terminal Server Component.
Today I installed that component using the 120 days test license and can not connect to this server using RDP as a user. The user is member of the Remote Desktop Group and if I uninstall the Terminal Server Component he can connect. That's why I'm thinking the user rights should be OK. I re-installed the Terminal Server Component and connecting is not possible except to the console.
Any ideas? (Reboot was done several times, Client OS is Win 7 on the machine trying to connect but using another 2003 server and connecting to the "new" one using RDP gets the same result.)

Regards,

Michael


See More: Remote Desktop not working / Terminal Server

Report •

#1
November 21, 2011 at 18:28:51
It seems that Terminal Server & RDP both use the default port of 3389. Could that be the problem?

http://support.microsoft.com/kb/187623

http://support.microsoft.com/kb/306759

How do you know when a politician is lying? His mouth is moving.


Report •

#2
November 22, 2011 at 06:22:39
Hi guapo,

thank you but this did not do it. On the console of that server I got a message today that the grace period has expired. I think that is the problem. Now I'm wondering why this has expired. That period is 120 days and I added the TerminalServer component yesterday. Those 120 days have gone really fast..


Report •

#3
November 22, 2011 at 12:41:20
That sure was fast. My only other guess would be firewall settings of some sort.

How do you know when a politician is lying? His mouth is moving.


Report •

Related Solutions

#4
November 28, 2011 at 13:04:36
Nope, no firewall settings that block this. The firewall settings are the same on other servers and on those I can access using Terminal Service

Report •

Ask Question