JeffreyHess <DoNotEmail@MacForumz.com> wrote on 11 apr 2005 in
microsoft.public.mac.rdc:
> > I posted something similar a few months ago and received no
> > reply. My
[quoted text clipped - 64 lines]
>
> Go Figure. My head hurts from hitting the brick wall so much.
Is there anything in the EventLog on the server when the connection
is refused?
Have you checked the licensing situation in the TS Licensing
Manager?
--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
JeffreyHess - 27 Apr 2005 04:08 GMT
"Vera Noest MVP" wrote:
> JeffreyHess <DoNotEmail@MacForumz.com> wrote on 11 apr 2005 in
> microsoft.public.mac.rdc:
[quoted text clipped - 109 lines]
> http://hem.fyristorg.com/vera/IT
> --- please respond in newsgroup, NOT by private email ---
Well, I was able to work with our IT group at the time I was trying to
connect, and got the log information. It was saying my computer was
attempting to connect with an "illegal license". Our IT group
re-installed the licensing server, but are checking again to make sure
there is not a special license for non-Windows computers.
Strangely, my connection to the new Win2003 server no longer works
either. It was fine for several days, then stopped working. This
server is only serving me, with no other users yet!
Also, when at work, on the network, I can connect using the RDC within
VPC (a Win2000 setup), whereas the same machine at my house connected
through VPN, with all other services accessible, can no longer
connect, but others remotely on the PC can connect to RDC.
If this was not happening to two different computers, I would begin to
think some sort of hardware issue. But others can connect from my
house to RDC, both Mac and PC, and I can connect under VPC at the
office, so there does not seem to be a hardware issue going on.