Thin client can no longer connect (NCD 200)

  • Thread starter Thread starter Arch Willingham
  • Start date Start date
A

Arch Willingham

Until yesterday morning, all of my thin clients could connect to the NT2000
(SP4) server. Now one of the five (its an NCD 200 terminal) can't connect. I
get a message on the server's event log that says:

Event Type: Information
Event Source: TermService
Event Category: None
Event ID: 1004
Date: 08/05/2003
Time: 8:05:33 AM
User: N/A
Computer: WAREAGLE
Description:
The terminal server cannot issue a client license.

I can see where all the thin clients pulled down and were issued their
licenses but one shows up as "unknown"....I have no idea if that's the one.

What do I do? Why did it know it had a licensee until yesterday?

Thanks,

Arch
 
Hi Arch,

Thank you for posting!

According to the post, I understand one client computer cannot connect to
the Terminal server.

On the client computer, what error message is displayed? Please let us know
the exact messages.

One thing you can try is to back up the MSLicensing registry key on the
client computer, and then remove it:

1. Log on to the client computer.

2. Start Registry Editor.

3. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing

4. On the "Registry" menu, click "Export Registry File".

5. In the "File name" box, type "mslicensingbackup" (without the
quotation marks), and then click "Save".

NOTE: If you have to restore
this registry key in the future, double-click the Mslicensingbackup.reg
file that you saved in this step.

6. On the "Edit" menu, click "Delete", and then click "Yes" to confirm
the deletion of the MSLicensing registry subkey.

7. Quit Registry Editor, and then restart the computer.

You can refer to the article below:
329888 "Error Connecting to Terminal Server: <ServerName>" Error Message
Occurs
http://support.microsoft.com/?id=329888

Hope this helps. Thank you!

Regards,
Bennie Chen
Product Support Services
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Bennie:

The machine that can't connect is a one of those Windows-Based Terminals,
thus I don't think there is a registry to delete. Does that make sense?

Arch
 
Any CE machine has a registry. The problem most of the time is how to access
it.
Decent terminals have an option on the setup screen to get rid of this key
used for Terminal Services.
If yours do not have, just reinstall the CE firmware to clear it.

--
Cláudio Rodrigues, MVP
Windows 2000/NT Server
Terminal Services

http://www.terminal-services.NET

-> The only Terminal Services Client for DOS.
-> The only customized RDP5.1 client with the close button disabled! :-)
-> Developers of SecureRDP, the BEST security utility for TS!

Do NOT email me directly UNLESS YOU KNOW ME or you are a Microsoft
MVP/Employee.
Use my support page on my website to submit your questions directly.
 
I did not get y'all's posts until today and the guy with the problem machine
was getting pissed off so I called Microsoft's clearing hose and got them to
re-issue the license. The machine was able to connect immediately.

Arch
 
Tim,

you have a completely different problem. I have answered your post
in microsoft.public.win2000.termserv.apps
 
I don't want to spoil your day, but if re-issuing the license
means that the client can connect, then I think that the problem
was not on the client, but that you were short of TS CALs. Make
sure that you are still complying by the EULA, since you now have
one license more than you paid for.
 
That's absolutely correct (but there can be other causes for the same
problem). That's why I wrote that you probably have one TS CAL more than
you paid for now.
Anyway, the problem that D. Sayers describes is documented in the following
KB article, and is fixed in SP4.

813508 - Cannot Connect to a Terminal Server From a Windows-Based Terminal
http://support.microsoft.com/?kbid=813508
 
No, you sound perfectly sane to me, but I can't say the same about
the thin client ;-)
I would reset/upgrade the firmware on the client to get rid of all
license information and other potential problems there. Configure
the client with your custom settings like name, IPnumber etc.

After that, the client should get a temporary license from the LS,
which lasts for 90 days. Since the TS CAL that you got from the
Clearinghouse should have a expiration date which is shorter than
90 days, the thin client will pick up this TS CAL eventually.
 
Cool...thanks!!!

Arch

Vera Noest said:
No, you sound perfectly sane to me, but I can't say the same about
the thin client ;-)
I would reset/upgrade the firmware on the client to get rid of all
license information and other potential problems there. Configure
the client with your custom settings like name, IPnumber etc.

After that, the client should get a temporary license from the LS,
which lasts for 90 days. Since the TS CAL that you got from the
Clearinghouse should have a expiration date which is shorter than
90 days, the thin client will pick up this TS CAL eventually.

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup ---
Click to expand...
 
More bizarre stuff....I re-set the firmware...nothing changed when I
re-logged in.

Arch
 
I called Microsoft on Saturday night to get the fix you mentioned. The guy
told me he would e-mail it to me immediately. I still have not heard from
them. Do you think they forgot or does it always talk this long to get an
e-mail??

Arch
 
No, you should get this within minutes. I'd phone them again and
stay on the telephone line until you have received the hotfix.

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup ---
 
Back
Top