The remote session was disconnected because there are no Terminal Server client access licenses available for this computer

We have a Windows Server 2003 Terminal Server. it is setup with a Per User CAL Token for up to 10 users.

Users in our office have no problem connecting to this Terminal Server.
Users outside the office have had no issues.

There is 1 user who has a problem when connecting. When they VPN into the network and try to connect to this server they recieve this error

"The remote session was disconnected because there are no Terminal Server client access licenses available for this computer"

This user then connects to an older backup Terminal Server running Windows Server 2003.

I have checked the event logs and have found no errors for Terminal Server Licensing.

What could be causing this?
Drakin030Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

NJComputerNetworksCommented:
what operating system is the problematic user using?

Are there more then 10 people connected to the TS server when this happens?

Can you get this to work if the client uses the console switch:    
mstsc.exe /v servername /console
0
Drakin030Author Commented:
The user is running Windows XP (I think pro)

There are not more than 10 users connected while this happens. I can log in under her account while I was on the phone with her.

I will test the mstsc.exe /v and let you know how that works.
0
Drakin030Author Commented:
The method of typing

mstsc.exe /v:<servername>

does not work.
0
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

NJComputerNetworksCommented:
mstsc.exe /v:<servername> /console   <-- have to have the console swtich too... do you get a different error or same error?
0
Drakin030Author Commented:
When the user does that they get the following message.

The user <Domain>\<My Username> is currently logged on to this computer, only the current user or an administrator can log on to this computer

Note where I said <My Username> The user is typing in her login name but it says only my user account or an administrator can log into this computer.

What the mess?
0
grenadeCommented:
try deleting the MSLicensing key from the client computer and check once again.
it will be in registry at location HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing.
Delete the whole key and connect again.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Drakin030Author Commented:
Good call, that fixed the issue.
0
lukefunoCommented:
grenade - why does this occur any reason? or is this a temp fix?
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.