From my last posting to you:
This is a server-side issue. From the FAQ:
The remote computer disconnected the session because of an error in
the licensing protocol. Please try connecting to the remote computer
again or contact your server administrator.
Cause: The licensing protocol handles the communication of licensing
information between your computer and the remote computer. If there is
an error in the licensing protocol, your computer cannot be connected
to the remote computer.
Solution: For step-by-step information about deploying Terminal
Server with Terminal Server licensing, see Guidelines for Deploying
Terminal Server at
http://go.microsoft.com/fwlink/?LinkId=34627. For
information about Terminal Server Licensing, see Windows Server 2003
Terminal Server Licensing Issues and Requirements for Deployment at
http://go.microsoft.com/fwlink/?LinkId=23444 and Windows Server 2003
Terminal Server Licensing at
http://go.microsoft.com/fwlink/?LinkId=26220.
==========
Note that this behavior can also be client driven... If you are using
XP Home and are attempting to connect to a Win2K Terminal Server, you
will not be comped a license and you get an error...
---
Jeffrey Randow (Windows Networking 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 Network Technology Community -
http://www.microsoft.com/windowsserver2003/community/centers/networking/default.mspx
Windows Home Networking Community -
http://www.microsoft.com/windowsxp/expertzone/communities/wireless.mspx