G
George
This just began happening and it is only on 5 of the 10
pcs that connect to Terminal server. Now 5 of my users
cannot get TS sessions withthe server. If anyone knows
anything, I would appreciate any guidance you can give.
The server is Win2K Server at SP3 with several security
patches and all PCs are Win2KPro at SP3.
The error Message is: "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."
Found the following, but this is bogus as it is NOT the
case: 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: Try connecting to the
remote computer again. If you continue to receive this
error message, contact the server administrator.
This began happening on MOnday and server was converted to
Terminal Server on 5/28/03.
Further, when I look at my TS Licensing's MMC, it cannot
find my Licensing server which happens to be on the same
machine. And nothing I do will cause the TS Licensing MMC
to find the local Licensing server. When I look at my
licensing server's MMC, it shows Domain and server name.
Also, it shows 20 per-seat and 16 allocated.
I'm confused as what this "Licensing" and "Terminal SErver
Licensing" is suggesting; and how to retify it. Help!!
pcs that connect to Terminal server. Now 5 of my users
cannot get TS sessions withthe server. If anyone knows
anything, I would appreciate any guidance you can give.
The server is Win2K Server at SP3 with several security
patches and all PCs are Win2KPro at SP3.
The error Message is: "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."
Found the following, but this is bogus as it is NOT the
case: 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: Try connecting to the
remote computer again. If you continue to receive this
error message, contact the server administrator.
This began happening on MOnday and server was converted to
Terminal Server on 5/28/03.
Further, when I look at my TS Licensing's MMC, it cannot
find my Licensing server which happens to be on the same
machine. And nothing I do will cause the TS Licensing MMC
to find the local Licensing server. When I look at my
licensing server's MMC, it shows Domain and server name.
Also, it shows 20 per-seat and 16 allocated.
I'm confused as what this "Licensing" and "Terminal SErver
Licensing" is suggesting; and how to retify it. Help!!