RDC no longer connecting

  • Thread starter Thread starter Canes
  • Start date Start date
C

Canes

I have been using Win XP Home + RDC to access company's
server that is running Win NT Server for the past 3 months
without any problem. Just today, entering the first day
of the fourth month, it no longer connected and kept
showing me a licensing error. What am I supposed to do?
Thanks.
 
It sounds as if your office needs to purchase additional licenses for their
terminal server. A temp license which lasts for 90 days is created when you
first connect. Once 90 days passes, you will no longer be able to connect
unless the office has purchased and installed licenses to the terminal
server.

Kind Regards,

--

Colin M. McGroarty
MCP+I, MCSE, NT-CIP, Windows Server MVP

www.McGroarty.org
 
Hi, thanks for your kind reply.
This problem happened in my new laptop. I used to access
RDC without any limit on my old laptop. Ever since I get
a new computer, it turned out to be a temp license. If I
only got a temp license with my new laptop, who is using
my old license? Or as long as we re-install the OS or
change a computer, the company will need to buy a new
license for me. Is it the way it works? I am getting
confused. Thank you.
 
From a post by Alex Angelopolous:
Here's some info that may be helpful. Most of it is contained in the
MSKB
article referenced below.

The first thing is, you should make sure you have the licensing
enhancements
hotfix installed:

Terminal Services Licensing Enhancements (Q287687)
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q287687

This will allow you to "lease" and recover licenses. If you have been
running
without it, you may need to "recover" licenses by contacting the
clearinghouse
in order to get the behavior described below.

With the TS Licensing enhancements installed, here is how licensing
behaves.

The first time you login to the TS, Win9x/Me/NT4 systems are issued a
temporary
license. On second login, this is converted to a "leased" license if
any
license tokens are available, with a 52-89 day duration. If none are
available,
the temporary license remains valid for 90 days.

Each time you connect to a TS, the expiration data of the workstation
lease
license is checked. If it is due to expire within the next 7 days, it
is
automatically renewed.

As you can probably see, this solves a lot of headaches for TS admins.
It is
definitely a more complex licensing model, but is akin to a model we
already
deal with (DHCP leases) and allows for significant population
turnover. Your
largest concern at any time is your projected 90-day user base, and
via the
mechanism of the temporary licenses, you are covered when you have
minor
overlap - so you don't need to worry if someone is issued a token on
their last
connection to your server. By the time a competing "replacement"
connection
could have its license expire, a token will have been returned to the
pool for
them.
---

Jeffrey Randow (Windows Net. & Smart Display MVP)
(e-mail address removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone
 
Back
Top