RDC can't connect to windows 2003 server

Hello everyone,


RDC suddenly stopped working on my mac.

I'm using os x 10.4.2 and a VPN connection to my office from home.

The VPN works fine but RDC does not.

I get the following error message :
"The client could not connect to the remote computer.
Either remote connections are not enabled, the computer is too busy to
accept ew connections, or network problems are preventing your
connection. Try connecting again later or contact your administrator."

I've heard that this is a licensing issue.

The problem is I can't delete the license on my mac because there is no
"Microsoft" folder inside the users/shared directory.

I'm logged in as the admin and I can't see that folder.

So how can I delete the license (if this is in fact what causes the problem)?

Do I have to make a successful connection in order for this folder to
be created (i.e. users/shared/microsoft)?

Please help!

Thanks,

Noam.

In article <2005102616105216807%noamfrie@posttauacil>,
Noam Friedman <noamfrie.RemoveThis@post.tau.ac.il> wrote:

> Hello everyone,
>
>
> RDC suddenly stopped working on my mac.
>
> I'm using os x 10.4.2 and a VPN connection to my office from home.
>
> The VPN works fine but RDC does not.
>
> I get the following error message :
> "The client could not connect to the remote computer.
> Either remote connections are not enabled, the computer is too busy to
> accept ew connections, or network problems are preventing your
> connection. Try connecting again later or contact your administrator."
>
> I've heard that this is a licensing issue.

Hi Noam!

It may be a licensing issue if you're connecting to a Windows 2000 or
2003 Terminal Server. If you're connecting to a Windows XP Professional
computer, then licensing won't come into play.

Try a little troubleshooting. Use the Network Utility in
/Applications/Utilities to verify that you can ping the computer you're
trying to connect to. The Traceroute feature will allow you to see the
hops you're making to get to your machine. Something may be getting
blocked.

Also, verify that the computer you're trying to connect to does indeed
still have the service turned on and that incoming connections aren't
being blocked by a local firewall that has been enabled.

Hope this helps! bill
--
William M. Smith
(Microsoft Interop MVP)