User can't connect to Windows 2000 Terminal Server using RDC 2.0Beta 2 for Mac

  • Thread starter Thread starter Jon Sherry
  • Start date Start date
J

Jon Sherry

Guest
Hi,
I've been running Win2K Terminal Services for quite some time, and I'm
looking to upgrade a Mac user to the new client, since the old one is bit
buggy on Intel Macs.

The user gets: "You were disconnected from the Windows-based computer
because there were problems during the licensing protocol. Try reconnecting
to the Windows-based computer, or ask your administrator if the license is
properly configured."

The log on the client shows:
2008-02-07 11:25:11.015 Remote Desktop Connection[374] Disconnect code
class: 0, main reason:8, error code: 8
2008-02-07 11:25:11.015 Remote Desktop Connection[374] Main disconnect
reason code is 0x0.
2008-02-07 11:25:34.009 Remote Desktop Connection[374] Disconnect code
class: 0, main reason:8, error code: 8
2008-02-07 11:25:34.009 Remote Desktop Connection[374] Main disconnect
reason code is 0x0.

There are no events in the System or Application Event Log on the Terminal
Server.

Terminal Services Licensing shows 2 CALs available. It also shows a CAL
token for the users machine, issued in July of last year using the old RDC.

Any ideas on how to trouble-shoot this? Can I delete the existing machine
CAL token?

Thanks,
-jb
 
Re: User can't connect to Windows 2000 Terminal Server using RDC 2.0 Beta 2 for Mac

Re: User can't connect to Windows 2000 Terminal Server using RDC 2.0 Beta 2 for Mac

You can't delete the license from the TS Licensing Manager (it will
eventually expire and be removed one month after expiration), but
you might be able to solve the problem by deleting the license from
the Mac client.

I'm no Mac expert, but I believe that the license is stored in
/Users/Shared/Microsoft/RDC Crucial Server Information/RDC GLOBAL
DATA.
Also check the permissions on this folder.

If the above doesn't solve the problem, I'd repost to the Mac rdc
or rdc2 newsgroups:

microsoft.public.mac.rdc
microsoft.public.mac.rdc.rdc2
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

Jon Sherry <js@classicmedia.tv> wrote on 07 feb 2008 in
microsoft.public.windows.terminal_services:

> Hi,
> I've been running Win2K Terminal Services for quite some time,
> and I'm looking to upgrade a Mac user to the new client, since
> the old one is bit buggy on Intel Macs.
>
> The user gets: "You were disconnected from the Windows-based
> computer because there were problems during the licensing
> protocol. Try reconnecting to the Windows-based computer, or ask
> your administrator if the license is properly configured."
>
> The log on the client shows:
> 2008-02-07 11:25:11.015 Remote Desktop Connection[374]
> Disconnect code class: 0, main reason:8, error code: 8
> 2008-02-07 11:25:11.015 Remote Desktop Connection[374] Main
> disconnect reason code is 0x0.
> 2008-02-07 11:25:34.009 Remote Desktop Connection[374]
> Disconnect code class: 0, main reason:8, error code: 8
> 2008-02-07 11:25:34.009 Remote Desktop Connection[374] Main
> disconnect reason code is 0x0.
>
> There are no events in the System or Application Event Log on
> the Terminal Server.
>
> Terminal Services Licensing shows 2 CALs available. It also
> shows a CAL token for the users machine, issued in July of last
> year using the old RDC.
>
> Any ideas on how to trouble-shoot this? Can I delete the
> existing machine CAL token?
>
> Thanks,
> -jb
 
Re: User can't connect to Windows 2000 Terminal Server using RDC2.0 Beta 2 for Mac

Re: User can't connect to Windows 2000 Terminal Server using RDC2.0 Beta 2 for Mac

On 2/7/08 3:31 PM, in article
Xns9A3DDB08DDE39veranoesthemutforsse@207.46.248.16, "Vera Noest [MVP]"
<vera.noest@remove-this.hem.utfors.se> wrote:

> You can't delete the license from the TS Licensing Manager (it will
> eventually expire and be removed one month after expiration), but
> you might be able to solve the problem by deleting the license from
> the Mac client.
>
> I'm no Mac expert, but I believe that the license is stored in
> /Users/Shared/Microsoft/RDC Crucial Server Information/RDC GLOBAL
> DATA.
> Also check the permissions on this folder.
>
> If the above doesn't solve the problem, I'd repost to the Mac rdc
> or rdc2 newsgroups:
>
> microsoft.public.mac.rdc
> microsoft.public.mac.rdc.rdc2
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> Jon Sherry <js@classicmedia.tv> wrote on 07 feb 2008 in
> microsoft.public.windows.terminal_services:
>
>> Hi,
>> I've been running Win2K Terminal Services for quite some time,
>> and I'm looking to upgrade a Mac user to the new client, since
>> the old one is bit buggy on Intel Macs.
>>
>> The user gets: "You were disconnected from the Windows-based
>> computer because there were problems during the licensing
>> protocol. Try reconnecting to the Windows-based computer, or ask
>> your administrator if the license is properly configured."
>>
>> The log on the client shows:
>> 2008-02-07 11:25:11.015 Remote Desktop Connection[374]
>> Disconnect code class: 0, main reason:8, error code: 8
>> 2008-02-07 11:25:11.015 Remote Desktop Connection[374] Main
>> disconnect reason code is 0x0.
>> 2008-02-07 11:25:34.009 Remote Desktop Connection[374]
>> Disconnect code class: 0, main reason:8, error code: 8
>> 2008-02-07 11:25:34.009 Remote Desktop Connection[374] Main
>> disconnect reason code is 0x0.
>>
>> There are no events in the System or Application Event Log on
>> the Terminal Server.
>>
>> Terminal Services Licensing shows 2 CALs available. It also
>> shows a CAL token for the users machine, issued in July of last
>> year using the old RDC.
>>
>> Any ideas on how to trouble-shoot this? Can I delete the
>> existing machine CAL token?
>>
>> Thanks,
>> -jb
Vera, thanks for the suggestions, and thanks for pointing out those other
groups! Somehow I missed them.
 
Back
Top