Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.

iap desktop license negotiation failed - error code:2056

Hi, for a two days now I haven't been able to connect through IAP Desktop to Microsoft Windows Server 2022 Datacenter VM.
I receive errors
- License negotiation failed - error code:2056

2023-04-18_14h41_46.png


- Logon failed - The user was denied access.

2023-04-18_14h41_54.png

Restart doesn't fix it.

What could be the cause?
What should I check?

Solved Solved
0 2 2,062
1 ACCEPTED SOLUTION

Hello hubert,

Welcome to GCC! 

Troubleshooting RDP


If you have Windows Remote Desktop Services (formerly known as Terminal Services) installed on your instance, then the conditions of the Client Access Licenses (CALs) are enforced. With these CALs, RDP connections will fail under any of the following conditions:

  • You have used all your available licenses
  • Your license is installed, but not configured or activated correctly
  • Your RDS trial period of 180 days has expired

Symptoms that you may not have enough valid licenses include messages such as:

  • This remote session was disconnected because there are no Remote Desktop License Servers available to provide a license.
  • The remote session was disconnected because of an error related to licensing in terminal server.
  • The remote session was disconnected because there are no Remote Desktop client access licenses available for this computer.

If your RDP connections fail, you can use the admin switch to connect to the instance for administrative purposes. This can be done on a Windows machine by using the native Remote Desktop Connection client.

%systemroot%/system32/mstsc.exe /admin

To resolve issues with RDP connections, purchase new licenses for your instance. For more details about CALs, review the Microsoft documentation. Alternatively, if Remote Desktop Services are not required, uninstall the service and use regular RDP connections.


 

View solution in original post

2 REPLIES 2

Hello hubert,

Welcome to GCC! 

Troubleshooting RDP


If you have Windows Remote Desktop Services (formerly known as Terminal Services) installed on your instance, then the conditions of the Client Access Licenses (CALs) are enforced. With these CALs, RDP connections will fail under any of the following conditions:

  • You have used all your available licenses
  • Your license is installed, but not configured or activated correctly
  • Your RDS trial period of 180 days has expired

Symptoms that you may not have enough valid licenses include messages such as:

  • This remote session was disconnected because there are no Remote Desktop License Servers available to provide a license.
  • The remote session was disconnected because of an error related to licensing in terminal server.
  • The remote session was disconnected because there are no Remote Desktop client access licenses available for this computer.

If your RDP connections fail, you can use the admin switch to connect to the instance for administrative purposes. This can be done on a Windows machine by using the native Remote Desktop Connection client.

%systemroot%/system32/mstsc.exe /admin

To resolve issues with RDP connections, purchase new licenses for your instance. For more details about CALs, review the Microsoft documentation. Alternatively, if Remote Desktop Services are not required, uninstall the service and use regular RDP connections.


 

I started another VM in the same subnet.

This command helped

%systemroot%/system32/mstsc.exe /admin