Remote session was disconnected because the Terminal Server client access license stored on this computer has been modified: client, access, server, terminal, session

by: vskoric3Posted on 2005-03-17 at 20:18:53ID: 13571709

Hi

Terminal server will accept conections from clients without licences during first 90 days (or 180 I am not sure) from the moment when first client (user) connected to it using terminal connection, after that period it will accept only licenced clients.
Maybe licences for other computers are installed corectly and for your PC are not, now the time period expired and it wont accept connection from your computer.

Hope this helps

by: GinEricPosted on 2005-03-17 at 20:19:08ID: 13571712

Gee, what's it say? Someone [or some "License Server"] has modified your "client access?"

It's in the logs, if you keep them, under System Security. There should be a full message telling you who or what modified the access, and maybe why.

The "Terminal Server client access license"

Go to the License Server and find out if it did it, then check your logs to see if a someone did it.

At the time, or in proximity to that time, that you lost access.

Your machine is not licensed?

Maybe according to the License Server, or some ghost.

by: zlatyPosted on 2005-03-17 at 20:40:11ID: 13571765

Just wanted to add a couple of points. First it will issue temp licenses for 90 days there after you need to purchase tcals. since you are using a 2003 server as the terminal server your XP machine tcal will not work. XP only gives you the free license for 2000 servers. Another thing to check is how the licenses are being handed out 2003 it has two different ways, per user or per machine. This configuration has know to change take a look and make sure it is set how you would like. Lastly, if you never activated the license server activate it and you will get a new grace period.

by: parpakPosted on 2005-03-18 at 05:29:08ID: 13574126

I know these everythings and I would like to tell you a bit of more information that my Terminal server is having both the PER USER and PER DEVICE based licenses and I already talked to microsoft and they said they both work fine.
And my terminal server license is installed as a device based license and still showing that its valid upto april 20th.

Maninder Deol

by: GinEricPosted on 2005-03-23 at 20:19:10ID: 13618748

The your back to our old friendly tokens.

First, if it says " the Terminal Server client access license stored on this computer has been modified" then it has been modified and something doesn't like it.

Everyone working but your machine.

Both are telling you that it's your machine.

Does the license on your machine match the license that the server has? You're the client machine, with the client access license.

Was the date modified? Did you copy it and rewrite it? Did it get corrupted in your registry, or altered by the installation of some software? Did XP erroneously try to replicate it?

There either has to be a difference between the copy the server has and the one your machine has, or something is interfering with the authorization.

Start by looking at both copies, on the server and on your machine. You're running three servers, I would hazard a guess that you can find the license, registry key, etc..

Have a look, what do they say, are they different?

by: parpakPosted on 2005-03-24 at 12:36:19ID: 13625433

Yep this all make sense, but can you tell me where can I look at the terminal server client license on my xp machine.

thanks,

Maninder Deol

by: GinEricPosted on 2005-03-26 at 12:08:53ID: 13637068

Whoa! Good one! I always like trying to find those things. We can start with "cackles," that is, cacls

If I type in:

cacls pub

I get all the permissions on directory pub

If I were to type in something like cacls -D username that user's access would be revoked.

If I go to the File Server and type in cacls c:\
I would get to see the access for that server

Using the cacls command is somewhat dangerous. One misspelling and you can revoke the world.

cacls followed by a filename gives the permissions on the file

cacls C:\Bind\host.exe

returns something like

BUILTIN\Administrators:F

etc., which is full control.

I mention cacls because it pertains to the following and before and after doing these, you should first view the access rights at your machine to see if your usename has access to begin with.

Go here:

http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/ts_int_c_020.asp

and here:

http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/ts_adm_h_012.asp

But if you didn't install it on the PDC, then you also have to go here:

http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deployguide/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/all/deployguide/en-us/sdcce_term_ikac.asp

Note

For Windows Server 2003 you are no longer required to host Terminal Server licensing on a domain controller, but if you do not, you must configure the Terminal Server to discover the license server. For more information, see "Configuring the Preferred License Server" later in this section.

If you've already followed the rules, or the above is already done, then it boils down to the fact that your machine is not allowed to remotely administer, period.

" I am using windows xp for remote admistration of these services"

That is a cacls or terminal license server issue.

You're better off reading and doing it by the Terminal License Server managment console, at the Terminal Server and making sure that it is agreed for access to and remote administration of both the File Server and the Mail Server.

From your specific machine as your specific username.

License Server is integrated with cacls to use tokens, SID's, in cooperation with each other.

Most token ID's can be located in HKEY_USERS\{pick a long number there}\Identities\ and

HKEY_USERS\{pick a long number there}\RemoteAccess\Profile

If there's anything in there.

These are dangerous places even for an Administrator, look don't touch; use the Terminal License Manager to adjust.

It just seems like you haven't enabled remote administration for the servers to your machine and username.

by: GinEricPosted on 2005-05-04 at 15:00:52ID: 13931360

hmmmm . . .

Question

Remote session was disconnected because the Terminal Server client access license stored on this computer has been modified

Subscribe now for full access to Experts Exchange and get

Instant Access to this Solution

client

access

server

terminal

session

Operating Systems Miscellaneous

Remote Desktop/Terminal Services

Trusted by hundreds of thousands everyday for fast, accurate and reliable tech support.

See what Experts Exchange can do for you.

Got a question?

We've got the answer.

Need individual assistance?

Our experts are ready to help.

Want to learn from the best?

Read articles from industry experts.

Working on a long term project?

Store your work and research.

What Makes Experts Exchange Unique?

Trusted by the world's most respected brands.

Faithfully serving IT professionals since 1996.

Related Solutions

Free Tech Articles

Cloud Class Webinars

Join the Community

Give a Little. Get a Lot.

Answers

3 Ways to Join

The Experts

The Experts

Testimonials

Testimonials

Testimonials

Business Clients

Business Clients

In the Press

In the Press

In the Press