Re: additional license
comments inline
=?Utf-8?B?ZGVuaW0=?= <denim@discussions.microsoft.com> wrote on 09
nov 2007 in microsoft.public.windows.terminal_services:
> Are you sure that you installed Terminal Services, in Add/Remove
> Windows components?
>
> Yes.
OK, then we've rules that out.
> And what *exactly* is the error message that you get when the
> third user tries to connect?
>
> "The cannot connect to the remote computer. Try connecting
> again. If the problem persists, contact the owner of the remote
> computer or your network administrator."
This can mean anyting. I assume that the clients can all ping the
terminal server?
> Is it always the third user who gets refused, irrespective of
> which client the user is connecting from, or are specific
> clients allowed / refused?
>
> It is the third user, whoever it is.
Terminal Server licensing is *never* per concurrent usage. So if it
is always the third session which is refused, irrespective of which
*client* is trying to make the connection, this points to a lack of
server CALs, rather then TS CALs. You need both. Server CALs are
per concurrent usage. But I would expect an Event saying "The
licensed limit for product Windows Server 2003 has been exceeded"
or something very similar.
> Have you checked the EventLog on the server for warnings and
> errors related to licensing or refused connections?
>
> I see event ID 861, "The windows firewall has detected an
> application listening for incoming traffic."
OK, forget this, has nothin to do with your current problem.
> By the way, I was looking at Terminal server license server
> discovery in tscc, it lists my 2 previous license servers no
> longer used in "automatically discovered license servers". One
> was Windows 2000 and the other was windows 2003. How can I
> update this listing? Also, I checked for "licensing mode" in
> tscc, it was per user mode, but it also states that "The
> allocaiton of licenses to users in not currently managed." What
> is this mean?
Here we have a real problem. It seems that your previous TS
Licensing Servers weren't properly deactivated and uninstalled,
maybe you just shut them down? Then they are still registered in AD
and the Ts will continue to locate them.
The easiest way to point your TS to your new TS Licensing Server is
to configure it in Terminal Services Configuration - Server
settings - License server.
The Per User licensing mode of your TS is correct, since you bought
Per user TS CALs. As the comment says, Per user licenses are
currently unmanaged, meaning that they will never be issued to
users. The TS will simply check if it finds a license server, and
then allow the connection. You will have to keep track of the
number of TS CAls needed by hand.
So after you fix the TS Licensing discovery, and verify that the TS
now detects the correct TS Licensing server, it should work.
If it still doesn't then the problem cannot be caused by TS
Licensing.
It could still be server CALs (check this in Control Panel -
Licensing applet), or maybe your TS is hardcoded to allow a maximum
of 2 connections? Check in tscc, under rdp-tcp - properties
> Thanks for your help.
> Hiro
>
> "Vera Noest [MVP]" wrote:
>
>> Are you sure that you installed Terminal Services, in
>> Add/Remove Windows components?
>> It sounds as if your server has only remote Desktop for
>> Administration enabled, which gives you2 (+1) concurrent
>> connections, without the need for TS licenses.
>>
>> And what *exactly* is the error message that you get when the
>> third user tries to connect?
>> Is it always the third user who gets refused, irrespective of
>> which client the user is connecting from, or are specific
>> clients allowed / refused?
>> Have you checked the EventLog on the server for warnings and
>> errors related to licensing or refused connections? If there
>> are any, what are the EventID, Source and Description?
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> =?Utf-8?B?ZGVuaW0=?= <denim@discussions.microsoft.com> wrote on
>> 09 nov 2007 in microsoft.public.windows.terminal_services:
>>
>> > Hi,
>> > I have a Windows 2003 Std server with terminal services
>> > running with 2 CAL for TS. I recently added 2 more TS CALs,
>> > but it seems I can still have only 2 connurrent access. I
>> > want to be able to have 4 people access it concurrently.
>> > How do I fix this?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting:
http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
