Event ID 1004 and 1010

[Craig Householder]

We have several terminal servers setup in our environment and one in
particular seems to be getting these errors. Our clients are all Win2k Pro
boxes and some users are not being allowed to connect. They get a VBScript
error (VBScript:Remote Desktop Disconnected) that pops up and the only
option is to click OK.

Once a user gets this from their desktop they cannot access that particular
Terminal Server from that particular desktop. However if they go to another
2k workstation they can get on just fine.

Any help?

 

[MatthewHarris [MVP]]

Do you have a license server up and activated?

Have you tried hardcoding the name of the license server
into the registry of the terminal server:

support.microsoft.com/default.aspx?scid=kb;EN-US;239107

-M

 

[Vera Noest [MVP]]

Either you do not have a Terminal Services Licensing Server at
all, or the TS cannot locate the LS.

You *must* install and activate a LS, also if your clients are
running W2K Pro or XP Pro. These clients get a free TS CAL from
the LS, it is *not* build into the client. (This assumes that you
run W2K on the server; if the server runs 2003, you must also buy
and install TS CALs).

If you do have a LS installed and activated, then try to hardcode
the address of the LS into the registry of the TS. Check:

239107 - Establishing Preferred Windows 2000 Terminal Services
License Server
http://support.microsoft.com/?kbid=239107

 

[Craig Householder]

What would have changed to require this? We don't have any TS Licensing
servers setup and have been running this box for about 18 months. I can
certainly set one up and will if this is the only resolution but it seems
odd to me that "nothing" has changed in our environment and yet all of a
sudden some end users are being prompted for this from one workstation but
not another.

If it were truly this problem wouldn't all of my terminal servers be
exhibiting this problem for all of my users regardless of the workstation
they were logged in to?

TIA

 

[Vera Noest [MVP]]

Weird! I can't explain why it has worked for 18 months, you should
have reached this stage after 90 days (grace period of the TS, in
which it can work without a LS).
The only thing that I can think of is that there has been a
Licensing Server somewhere in your organisation, which you have
not been aware of, that has handed out TS CALs to your clients.
Check the change log on all your Domain Controllers, throughout
the AD forest. It's most likely that a previous LS has been
running on a DC.

All other symptoms of the problem are to be expected in the
absence of a LS..
I believe that you see only the tip of the iceberg at the moment.
My guess is that the client that gives you problems at the moment
is the first one that has an expired (temporary?) license. The
other clients should show the same behaviour soon.
You should be able to create the problem on a client of your
choice: just remove the license information from the registry of
the client, then try to connect. If there is no licensing server
available and the grace period for the TS has ended, the client
will be able to connect once and will fail to connect at the
second attempt.

187614 - Removing Terminal Server Licenses from an RDP Client
http://support.microsoft.com/?kbid=187614

 

[Jan]

Have the problem machines had a patch/update/service pack applied recently?

Jan

 

[Craig Householder]

OK, that fixed it. We brought up AD 3 months ago so I can only assume that
the 90 day counter starts when you run DCPromo on the first server.

Now I'm going to have to do some more reading to determine if we can have
multiple license servers and/or what the ramifications are if the license
server goes down.

Thanks,

Craig