Name: mdelato Date: September 18, 2005 at 12:04:27 Pacific Subject: Remote Desktop Login Prob OS: WinXP SP2 CPU/Ram: 3GHz,512 RAM
Comment:
I've been able to log into Win Server 2003 for quite a while using Remote Desktop. I'm using Win XP as the client. This problem just started out of nowhere and no changes have been made to my knowledge. When I call the Server 2003 computer and run Remote Desktop, after my login, a Logon Message appears from the host computer and forces the window closed. "To log on to this remote computer, you must have Terminal Server User Access Permissions on this computer". I checked that from the host machine and all is well. I have Admin and Terminal permissions ok.
I check Event Viewer and every RDT login attempt adds a new line. "Terminal server could not locate a license server. Confirm that all license servers on network are registered in WINS/DNS and running."
I open Terminal Licensing and my All Servers tree is empty. It won't let me do a "Connect" or "Active Server". We installed Win Server 2003 about 4 or 5 months ago. Are we supposed to upgrade and pay for a license fee? I'm really confused.
There isn't anyone logged in remotely. I can verify this under Sessions for Computer Management. I'll check all the user logins and verify no more than two people are designated with Remote Desktop permissions tonight.
If I open Terminal Licenses under Admin Tools, nothing is listed in the righthand pane. There should be a Terminal Server running right? I don't know if that matters or not since, I can access the login screen just fine using Remote Desktop, but then it gives the error I described. :-(
In 2003, you do NOT install Terminal Services via add/remove programs to do remote administration. Simply go to System properties -> Remote -> and check the box for allow these users to log on remotely. Make sure your user account is added to this list.
Help survivors of Hurricane Katrina. Please donate to the American Red Cross.
I found it. Thanks. However, it is greyed out. The box is checked but there seems to be some group policy overriding the ability to check/uncheck this. Any idea what that policy is?