Home | Site Map | Cisco How ToNet How To | Wireless |Search | Forums | Services | Donations | Careers | About Us | Contact Us|

error in the licensing protocol

RRAS, VPN, TS/RDP, Routing and remote Access.

error in the licensing protocol

Postby guest » Wed Feb 29, 2012 5:50 pm

i've a 2008r2 demo scenario with this server:

- RD Gateway + RD Web Access
- RD Session Host + RD Licensing
- DC + ADCS
- W7 workgroup

the gateway server have 2 nic, the internal and the external nic for the win7 communication.

i've create the RDWA certficate and the RDSH certificate (but i can't export the private key, because i think that it wasn't created in the right mode). these certificate are imported in the client (trusted certificate).

when i run IE, no cert error show, and do the logon and select the application (calc), but the RDSH cert gives an error but i bypass it. when they think....thnik...think.....after more second, compare this error: the remote computer disconnected the session because of an error in the licensing protocol.

how i can resolve it?
Tablet and Smartphone Setup Guide
http://www.quicksetupguide.com

Troubleshooting Vista Wireless
http://chicagotech.net/
guest
 
Posts: 9027
Joined: Mon Nov 27, 2006 1:10 pm

Re: error in the licensing protocol

Postby guest » Wed Feb 29, 2012 5:50 pm

Many possibilities may lead to the error message "The remote computer disconnected the session because of an error in the licensing protocol", to narrow down the problem’s scope, I recommend you to reproduce the issue and check the Event Viewer (eventvwr.msc) – Windows Logs for related information.



A common possible cause of this error is the TS may have the DefaultLicenseServer key configured to use the IP Address of the license server rather than the host name. In the same while, the Security Setting "Network Access: Restrict anonymous access to named pipes" is defined and enabled in the GPO that applies to the TSLS. Using the IP address instead of the host name of the TSLS will cause the TS to use NTLM authentication instead of Kerberos, as a result, the will be an anonymous access to the HydraLsPipe RPC. If the Security Setting to restrict anonymous access to named pipes is enforced on the TSLS then the request for a license from the TS will fail.



To resolve this issue, try to disable the setting "Network Access: Restrict anonymous access to named pipes" or use host name instead of IP address in the DefaultLicenseServer key.



For more information about this key, please refer to:



How to override the license server discovery process in Windows Server 2003 Terminal Services

http://support.microsoft.com/kb/279561



Let us know the result if possible. Thanks for your cooperation.



· Lionel Chen
Tablet and Smartphone Setup Guide
http://www.quicksetupguide.com

Troubleshooting Vista Wireless
http://chicagotech.net/
guest
 
Posts: 9027
Joined: Mon Nov 27, 2006 1:10 pm

Re: error in the licensing protocol

Postby guest » Wed Feb 29, 2012 5:51 pm

i'm back! the good news is that this is a RDC bug.....the bad news is that microsoft haven't released the fix. but i've find a workaround.....it's very ugly but it's the only way with windows 7. with the windows xp mode, the users can load the RDP 6.1 (not the 7.0) and use the remote desktop web access. the 6.1 haven't the SSO, like also more features, but anyway works.

i hope that this post can help someone who have the same problem
Tablet and Smartphone Setup Guide
http://www.quicksetupguide.com

Troubleshooting Vista Wireless
http://chicagotech.net/
guest
 
Posts: 9027
Joined: Mon Nov 27, 2006 1:10 pm


Return to VPN, TS and Remote Access

Your Ad Here

Who is online

Users browsing this forum: Google Adsense [Bot] and 2 guests