Remote Desktop Connection
Our company makes extensive use of the Remote Desktop feature in Windows XP and Server 2K and 2K3. I have a user whose connection is being rejected for errors in licensing protocols. I moved him to a different laptop and still the same error, I re-named the laptop to no avial. All other functions of network connection are fine, still has access to the shared drive on 2K server. I log him in on my PC and everything works fine. Any ideas?
Software/Hardware used:
Software/Hardware used:
ASKED:
July 26, 2005 11:42 AM
UPDATED:
July 28, 2005 3:51 PM
Answer Wiki:
I am assumig terminal services. If so, is your terminal services configuration set to "Per Device" or "Per User"?
If it is per device, than termial services forces licening and will not let more devices connect than you have licenses. Check to to see if your TS configurationis Per Device and then check to see if you have enough licenses installed in terminal service licensing to account for the number of connections.
If you set TS configuration to Per User, than TS will not force liceniing.
To see all answers submitted to the Answer Wiki: View Answer History.
You also need to see if the Terminal Services component is configured for “Remote Desktop for Administration” or “Application Server” modes. The former is a freebie with a valid Windows Server license, and allows two concurrent sessions. Application Server requires additional licensing; it sounds like your server has been set to this mode.
Also, you will probably want to check the “Restrict Terminal Services users to a single remote session” check box in the Server Properties under the TS configuration snapin.
Cheers
I have a little more information to add, this connection was working and suddenly stopped. TS is running in Application mode but I have ample licensing to cover it. I don’t know if it’s related, but I just tried to ping the laptop (he’s currently on a VPN connection) and get no response from it. He can ping both me and the server and all other network functions are fine.
Well, my first reaction to this new information is that the laptop has been upgraded to XP SP2 – but the builtin firewall allows 3389/tcp in its’ default configuration.
Perhaps your organization has ripped out the Microsoft Firewall portion of SP2 and replaced it with a 3rd party software firewall, which is blocking 3389? Has TCP/IP Filtering been enabled/monkeyed around with on that laptop?
Cheers
Was this user able to logon to the terminal server before or is the client a new one. If so, make sure the users account has proper access to the terminal server, is the user a member of the security group that the terminal server is allowing permissions for?
No, this is not a new user, he had been logging on fine for almost a year, then one day – nothing. SP2 has been installed, but the firewall disabled when I began troubleshooting. I haven’t looked at TCP/IP filtering, but will check it out. It made no sense that the problem occurred on 2 different laptops, but he can log on on any other system in the building.