XP home - temp license

[Guest]

I have a remote user. They have XP home edition SP1.They use AOL dial up to get to the internet. I have a Windows 2000 server with TS loaded. It is a DC. I have TS loaded on it. I activated the server and loaded 5 CALS. I show unlimited licenses, Windows 2000 CALS 5 installed and 5 available. I also show temporary licenses. When the remote user connects they are granted a temp license instead of one of the 5 CALS. Also, the user can get connected the first time. Then when they try again, they get an error message that they cannot connect to the remote computer. I get event ID 1004 on the TS server when this happens. If I delete the registry key on the client PC I can get back on, until I disconnect and reconnect.

I have searched all of the Q articles and none have helped.

 

[Dirk-Thomas Brown]

First ? the cals are the acualy TS cals? You need TS cals to use TS.

Dirk-Thomas

 

[Dirk-Thomas Brown]

Ok, you have 5 of those? This is for one license only. Also, you activated
the license server, do you also have it running in app mode?

Dirk-Thomas

 

[Dirk-Thomas Brown]

You might also want to recheck those steps. If its a Windows 2000 Server
Running TS essentially XP Pro (Not Home) and Windows 2000 Pro get on without
using a license. XP Home requires one as I am sure you are aware. Did you
add the client license to the TS? Also noticed you said 2000 TS and the
client licenses are 2003 don't know if that matters... but do know you need
to add the TS client licenses to the TS.

To recheck the steps
http://www.microsoft.com/technet/community/columns/profwin/pw0601.mspx

Dirk-Thomas

 

[Guest]

I have activated it. What I assume I bought was CALS for non XP and 2000 Pro workstations. I have added the licenses to TS. They are displayed in TS license manager. The serve ris activated and XP and 2000 Pro workstations access it fine. It is in APPS mode.

 

[Vera Noest [MVP]]

What you describe seems to be a problem with the transfer of the
full TS CAL to the client. This can be caused by network problems.

There might be a black hole router between your client and the TS,
which blocks packets above a certain size. This prevents the
transfer of the permanent TS CAL to the client (on first
connection, the client gets a temporary license, on second
connection, it gets a permanent license).

If this is the problem, you have to change the MTU size. Check the
Terminal Services FAQ, there are 2 items about this under
"Connectivity"

http://www.microsoft.com/windowsserver2003/community/centers/termi
nal/terminal_faq.asp

 

[Guest]

The link does not work. Is there a Q article I can reference?

 

[Guest]

The URL is fine, it jsut wraps because it's too long, so you'll have to copy/paste into your Internet Browser

Patrick Rous
Microsoft MVP - Terminal Serve
http://www.workthin.co

----- peachy wrote: ----

The link does not work. Is there a Q article I can reference?

 

[Guest]

It was the black hole. I altered teh registry as directed in the article and rebooted. After that I get connected just fine

Thanks for the help.