Re: "The session was disconnected because no Terminal Server Licensing Server could be found."
- From: "Granny" <granny@xxxxxxxxxxx>
- Date: Mon, 18 Jul 2005 10:10:25 -0500
thanks Vera, I had already found that KB article and I did check event
viewer and investigated that.
jeanette
"Vera Noest [MVP]" <Vera.Noest@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:Xns96979B3A89489veranoesthemutforsse@xxxxxxxxxxxxxxxx
> You write that you bought 25 CALs, but did you also bought 25 TS
> CALs?
> And if you did buy TS CALs, were did you install them?
>
> A W2K TS Licensing Server cannot handle 2003 TS CALs, because it
> doesn't understand the new licensing types (Per user versus Per
> Device).
> So you must install and activate Ts Licensing Services on the 2003
> member server.
> Next, you have to point the 2003 TS to the 2003 LS (even if it's
> the same server).
> Then install the 2003 TS CALs on the 2003 LS.
> Next, you have to make sure that the 2003 TS is in the same
> licensing mode as the type of 2003 TS CALs that you bought (Per
> User or Per Device).
>
> And finally a friendly tip: read the EventLog when you have a
> problem. Most problems, and especially licensing problems, are
> spelled out in clear text there. Saves you a night of Googling....
>
> 279561 - How to Override the License Server Discovery Process in
> Windows Server 2003 Terminal Services
> http://support.microsoft.com/?kbid=279561
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> *----------- Please reply in newsgroup -------------*
>
> "Granny" <granny@xxxxxxxxxxx> wrote on 18 jul 2005:
>
>> A bit of history:
>> We were running Win2000 Adv Server as Domain Controller, Active
>> Directory and Terminal Service Licensing Server
>> On this same server was our accounting software that 35
>> employees accessed thru Terminal Server. Bought 10 Cals to
>> cover 10 workstations running Win98SE. - other 25 workstations
>> are running WinXP Pro which Win2000 Adv Server gives free CALS.
>> Server name = Dataserver
>>
>> We had problems with the server not being powerful enough so we
>> bought a new super-dooper Dell
>> bought Win2003 Ent Server and 25 Cals
>> Named it Dataserver2 and moved the accounting software to this
>> server
>>
>> Dataserver is still the DC and Terminal Licensing Server.
>>
>> All was working fine until Saturday when users could not RDP
>> into the accounting software. Error message stated:
>>
>> "The session was disconnected because no Terminal Server
>> Licensing Server could be found."
>>
>> I discovered this on Saturday while working on some of the
>> workstations. After staying up all night Googling and reading MS
>> KB's, and trying suggestions I found, problem was not resolved.
>> On Dataserver and Dataserver2 TS License Manager showed the 2
>> servers active and the TS licenses just fine. I then did an
>> RDP to Dataserver and discovered I could obtain license fine.
>>
>> So the problem is not with Dataserver - it's with Dataserver2
>> not acknowledging the license server. All other network
>> functions work fine - Ping the Dataserver from Dataserver2 by IP
>> and name shows no problems.
>>
>> Then I ran across something in my research about 120 days and
>> that MS changed the policy of granting free CALS to XP Pro -
>> unless you had bought the XP Pro before Win2003 was released.
>> But still, we had paid for 25 CALS so we should be OK. ?????
>> But it would not work. Then I went to Dataserver2 and checked
>> the date we put it on-line. March 17th, 2005. How about that
>> being close to 120 days? Now, you may ask, why the 120 days
>> thing should apply since we bought the 25 CALS. Beats the heck
>> out of me, but it's the only thing I can come up with.
>>
>> I contacted the boss at home today (Sunday), told him we have a
>> major problem but I figured a work-around until we get a network
>> expert in to solve the problem. We can't have 35 angry
>> employees trying to work and having computer problems :)
>>
>> I copied the accounting software back to Dataserver and went to
>> every workstation and created new RDP's pointing to Dataserver
>> for everyone - Accounting software via RDP now works again.
>>
>> Big question now is: why did this all work on Friday - nothing
>> new downloaded/installed on either server, etc - then Saturday
>> it does not work?
>>
>> In hindsight, we probably should have moved the Terminal Service
>> Licensing Server to the new Dataserver2 - but I was not involved
>> in that process. When I questioned this I was told terminal
>> Service Licensing is such a headache and MS is very difficult to
>> deal with when moving the CALS to a new system, that it was
>> easier to leave this on Dataserver. I just get to come along
>> and fix problems. LOL.
.
- Follow-Ups:
- References:
- Prev by Date: Environment
- Next by Date: Re: "The session was disconnected because no Terminal Server Licensing Server could be found."
- Previous by thread: Re: "The session was disconnected because no Terminal Server Licensing Server could be found."
- Next by thread: Re: "The session was disconnected because no Terminal Server Licensing Server could be found."
- Index(es):
Relevant Pages
|
