Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 359
  • Last Modified:

Problems connecting to Terminal Server

When I first setup my Terminal Server I did not know much about the Licensing, so I did not activate the licensing. After a while a had some clients get error messages that their license was going to expire. I did some searching and activated the Licensing manager. I had Clients listed under Temporary but some have migrated over to Existing Windows 2000 License. My problem is and it has happened to a couple of clients now that they log on no problem then one day they start to connect and get automatically sent back to the white Remote Desktop page with no error message. It appears that if I reboot the server they can connect again at least for a little while.
0
nestey
Asked:
nestey
  • 5
  • 3
1 Solution
 
aleshmCommented:
On the client (yes, client) delete the following registry key:

HKEY_LOCAL_MACHINE, Software, Microsoft, MSLicensing, the whole HardwareId and the Store.

This will solve the problem.

A.
0
 
nesteyAuthor Commented:
Do I delete MSLicensing also, or just Hardware and Store?

One thing I noticed is this client is listed both in the Temporary and Exsiting Windows 2000 Licensing tabs on the server? Is this an issue

I will try this out next week as the client that this has been happening to is traveling at the begining of the week so have patience.

Thanks
0
 
aleshmCommented:
You can delete the whole MSLicensing... without damaging anything, it will be auto-recreated the next time you run Terminal Services Client.

You have an issue with licenses.

A.
0
Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
nesteyAuthor Commented:
Thanks,

 I will start another thread for the licensing issue.
 
0
 
nesteyAuthor Commented:
My client just informed me that he had the same problem again so I went in and deleted the registry key HKEY_LOCAL_MACHINE, Software, Microsoft, MSLicensing, the whole HardwareId and the Store and he is still not able to connect. I am able to connect as him from my machine with no problem and I can also connect as me on his machine no problem. I just rebooted his machine and still not able to connect.
0
 
aleshmCommented:
Exact error is and when does it happen? At connect time, after the login window is shown... when? Using which client? The one which comes with XP or the TS one?

A.
0
 
nesteyAuthor Commented:
The machine with the problem is a windows 2000 machine with TS installed, there is no error it just automaticly logs user back out to the white remote desktop screen. I have it set up to start our ACT! database upon startup whichs locks people just into this application and seems to work fine for all other users. I not sure how the licensing works or the client works but strange to me that I can not log on as XYZ on XYZ's machine but can logon as 123 on XYZ's machine, and also can log on as XYZ on 123's machine?
0
 
nesteyAuthor Commented:
Alleshm
I deleted the registry key HKEY_LOCAL_MACHINE, Software, Microsoft, MSLicensing again and also rebooted the server and it been 3 days now and my client has not had a problem logging on. So i am going to accept your answer and I will create another question as there still may be a licensing issue as this client now is listed 3 times in exsisting and once in temp.

Thanks
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now