RDC broke upon MacOS upgrade to 10.4.10

Recently upgraded to Mac OS 10.4.10 from 10.3.9

Had been using Microsoft Remote desktop v 1.0.3 to connect to a Windows 200
server remotely at work.

Getting the "Cannot connect error" "Eiterh remote connections are not
enabled, the maximum number of connections was exceeded or an error
occurred. Try connecting again later of contact your administrator"

Then I downloaded the 2.0 beta and it doesn't work either. I get the
following error:

"remote desktop cannot verify the identity of the computer you want to
connect to. Yada yada.. Do you want to connect anyway"

I click yes and get the following error:

You were disconnected from the windows based computer because there were
problems with the licensing protocal.

Pressing reconnect does not do any good.

Yet I can launch VPC and used the RDC client in windows just fine(except I
can't print........what gives??

I am running RDC Beta 2 on an Intel Mac with 10.4.10 and am not getting these
errors.

However, I have two other Macs (pre-Intel, if that matters) that ARE getting
these errors. Also, both machines worked for a period of time and suddenly
began throwing the errors upon attempting to connect.

Any further thoughts would be much appreciated. I'd like to use this RDC
client in a work environment, but it hardly seems stable enough.

--BPierce

"Dave" wrote:

> Recently upgraded to Mac OS 10.4.10 from 10.3.9
>
> Had been using Microsoft Remote desktop v 1.0.3 to connect to a Windows 200
> server remotely at work.
>
> Getting the "Cannot connect error" "Eiterh remote connections are not
> enabled, the maximum number of connections was exceeded or an error
> occurred. Try connecting again later of contact your administrator"
>
> Then I downloaded the 2.0 beta and it doesn't work either. I get the
> following error:
>
> "remote desktop cannot verify the identity of the computer you want to
> connect to. Yada yada.. Do you want to connect anyway"
>
> I click yes and get the following error:
>
> You were disconnected from the windows based computer because there were
> problems with the licensing protocal.
>
> Pressing reconnect does not do any good.
>
> Yet I can launch VPC and used the RDC client in windows just fine(except I
> can't print........what gives??
>
>