Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Remote Desktop connection issues

Status
Not open for further replies.

jimmytye

Technical User
Jan 7, 2004
2
US
I have a 2003 server setup as an FTP server. I connected via Remote Dektop (XP Pro) several times and it worked fine. Now, when I try to connect, I get the following message:

"The remotes session was disconnected because there are no Terminal Server License Servers available to provide a license."

Can anyone help me out?

Thanks
 
My understanding when using Remote Desktop, was that there was no license requirement for 2 users.

I thank you for any input.

Jim
 
Only if the server is running in administrative mode not in application mode.
Terminal server in application mode demands a licensing server.

Gary
 
If you turned on terminal services from the add/remove programs area in the control panel, then you installed the application mode version. Uncheck it, then right click on my computer and go to the remote tab, put a check in "allow user to connect remotely to this computer". That turns on term serv for admin mode.
 
Microsoft added the FIPS compliant setting to the options for Terminal Services encryption levels in Windows Server 2003.

NOTE: See How do I configure Windows Server 2003 Terminal Services for secure client communications?

Unfortunately, a Windows Server 2003 with the encryption level set to FIPS compliant does NOT allow Remote Assistance connections from a computer that is running Microsoft Windows XP.

Windows XP and Windows XP SP1a do not support the FIPS compliant encryption level and cannot connect to a FIPS compliant Windows Server 2003 for remote assistance.

FIPS support on the client is handled in the Terminal Services client, not by the operating system. Upgrading to the RDP 5.2 (Windows Server 2003) client permits a client that is running Windows XP to connect to a Terminal Services session on Windows Server 2003 that is configured for FIPS encryption, but it does not permit the Remote Assistance client to connect.

The only workaround is to turn off the FIPS encryption level.

Microsoft is aware of the problem.

 
This worked for me. In W2k, you had to install TS for any use of it. BUT in W2k3, if you install TS, you are installing the Application mode. The Administration mode is installed by default. Simple answer, uninstall TS, and admin TS mode worked great.
 
"The remotes session was disconnected because there are no Terminal Server License Servers available to provide a license."

I get this error too even after I remove TS as micronmega had say... Does remote desktop work for anyone after 90days??
 
30 days elapsed, you were in application mode, and you haven't stood up a licensing server and installed licenses.

 
How fo I change back to administrative mode??
I have already uninstall TS :(
 
Or you can simply delete the registry entry for the temporary license on the client workstation by going to HKLM\Software\Microsoft\MSLicensing.
 
jpm121, I have already UNINSTALLED TS, but its still not going back to admin TS :S
 
Reinstall Terminal Services and choose Administrative Mode this time around.
 
There is no option to install as Administrative Mode... Where can I find the option?
thanks
 
When you put the check back in next to Terminal Services, it should install the ncessary files and prompt with a scren asking you to select the mode via a radio button. Are you saying you get no such screen when installing it?
 
Terminal services for remote installation is installed by default on a windows 2003 server. You are supposed to not have to do anything.
 
shinedog- no I don't see any radio button
timsayles1- But I did... What can I do now?? :(
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top