Windows Cannot Connect To A Licensing Server 2003
Latrisha Adan
I was just trying to open Rhino using cloud licensing. It prompts me to sign in to the accounts.rhino3d.com, which I can do successfully. I get to the screen that says that you can return to Rhino and close this screen. When I go back to Rhino I see the above error message. I have tried logging out of my account, I have no other internet connection issues, have tried uninstalling and reinstalling Rhino 6 to no success. Thanks.
Hi Charlie - you could try disabling the firewall to see if that changes anything.
Alternatively, a tool like should be able to test the connection for you. Remove the https:// parts of the urls that John posted above:
@charlie.foss do you have the latest service release for Rhino 6 installed? It looks to me like a bug we fixed a while ago - where Rhino was using an insecure version of TLS by default. Some installations of Windows rightly deny use of the older insecure TLS 1.0 protocol. I believe Rhino 6.14 and newer use a more modern version of TLS that should get past this restriction.
@brian I just tried to use a standalone license just so that I could keep working and it said that the validation server could not connect. I am able to connect to api.mcneel.com via my web browser. Not sure if this is related but it seems to be.
We have a number of terminal servers, all running Server 2019. For most purposes they are standalone (they each handle their own connection broker service), and the only shared resource is the licensing server, which is a dedicated VM (also Server 2019) which does nothing apart from act as the licensing server. From when set up about a year ago (session hosts and licensing server) all worked fine until a couple of months ago when three (so far) of the terminal server started randomly giving the following error:
In most enterprises, Tableau Server needs to communicate with the internet. Tableau Server was designed to operate inside a protected internal network. Do not set up Tableau Server directly on the internet or in a DMZ. Instead, communications between your network and the internet should be mediated using proxy servers. If the computer running Tableau Server cannot access the internet directly, then you may need to deploy forward proxy servers to mediate traffic from inside the network to targets on the internet. Tableau Server doesn't support pass-through or manual proxy authentication.
You can upload log files to Tableau when working with Support. See tsm maintenance send-logs(Link opens in a new window). To successfully upload files to Tableau, your Tableau Server must be able to communicate with the send-logs server on port 443:
Licensing. Tableau products connect to the internet to activate product keys. Unless you activate Tableau software with the Offline Activation Tool, all Tableau products must have access to the internet to validate licenses. Specifically Tableau requires internet access during the following licensing operations: activation, deactivation, and on the refresh maintenance date. For more information about these operations, see Manage Licenses(Link opens in a new window).
Requests to the ocsp.*.amazontrust.com and crl.*.amazontrust.com domains are managed by Amazon for certificate revocation information. See ACM certificate characteristics(Link opens in a new window) for more information.
If Tableau Server is able to access the licensing server, it displays an "OK" message. Otherwise, an error such as "Can't reach this page" may be displayed. To resolve this issue, work with your networking team to unblock access to atr.licensing.tableau.com:443 on the Tableau Server computer.
If you are integrating Tableau with a Slack workspace, there are a number of steps you need to take, including adding specific URLs to the Tableau allowlist. These are listed here(Link opens in a new window). For complete details on how to do this, see Integrate Tableau with a Slack Workspace.
Tableau Server can run without internet access. For more information about deploying Tableau Server in organizations without access to the internet, see Install Tableau Server in a Disconnected (Air-Gapped) Environment.
In many enterprises, users also need to access Tableau Server from outside the network (that is, from the internet). For example, in many enterprises, users want to be able to reach Tableau Server from their mobile devices in order to interact with views that are stored on the server. To configure access to Tableau Server from the internet or from mobile devices, you should use a reverse proxy.See Configuring Proxies and Load Balancers for Tableau Server.
PCoIP agent license registrations are managed automatically by Teradici's Cloud Licensing service. If necessary, you can manage them yourself, using your own locally-installed PCoIP license server instead.
The Windows setup wizard collects this registration code during installation. If you're already registered your PCoIP agents, there's nothing more to do here. If you've already installed the PCoIP agent software but have not registered it yet, you can register post-installation using the PCoIP Control panel or via a PowerShell Script.
PowerShell scripts must be permitted to run on your machine. If your execution policy prevents pcoip-register-host.ps1 from running, you can temporarily enable PowerShell script execution with the following command:
In deployments where PCoIP agents cannot access the internet, or where cloud-based licensing is not permitted or desired, a local PCoIP License Server can be used instead. The PCoIP License Server manages PCoIP session licenses within your private environment.
Configuring PCoIP agents to use a local license server is done in one of two ways, depending on whether your deployment uses a PCoIP Connection Manager, or whether your PCoIP clients connect directly to PCoIP agents.
To verify your system's licensing configuration, run the pcoip-validate-license.ps1 PowerShell script on the PCoIP Agent machine. The script will ping the license server and attempt to retrieve information on an available license:
If you have only one license on the license server and run pcoip-validate-license.ps1 from a PCoIP session, the command will fail because you are currently using the single license. In this scenario, disconnect your PCoIP session and try again from an RDP session instead.
In direct, or unbrokered, deployments, each PCoIP agent is configured with the license server address via a GPO variable. When a client initiates a new PCoIP session, the PCoIP agent uses its local configuration to communicate with the license server.
To verify your system's licensing configuration, run the pcoip-validate-license.ps1 PowerShell script. The script will ping the license server using the local GPO configuration and attempt to retrieve information on an available license:
When connecting to an Amazon Elastic Compute Cloud (Amazon EC2) Windows instance using Remote Desktop Protocol (RDP), I receive this error message: "The remote session was disconnected because there are no Remote Desktop License Servers available to provide a license. Please contact the server administrator." How can I resolve this?
If you installed the Remote Desktop services host settings on your Amazon EC2 Windows instance to allow more than 2 concurrent RDP client sessions, then you must purchase Client Access Licenses (CALs). RDS provides a licensing grace period of 120 days. After the grace period expires, you must purchase CALs to allow more than two concurrent RDP user sessions.
If you purchased CALs and receive the error, then the server might not be reachable by the instance that you're connecting to. For more information, see Cannot connect to RDS because no RD Licensing servers are available.
Note: If you still can't connect to a Windows instance using RDP, you might have to perform additional troubleshooting. For more information, see How do I troubleshoot Remote Desktop connection issues to my Amazon EC2 Windows instance?
"Windows cannot find the Microsoft Software License Terms. Make sure the installation sources are valid and restart the installation" while I install windows server 2016 on HPE Proliant ML110 Gen9 with Intelligent Provisioning
Issue was once the iso would actually read (you can't do assisted install or it will fail) it would not read the drives. Having this driver allowed it to see the drives and install on them. Hope this helps!
When I try to activate Passolo 2018 using a license server (on Windows Server 2019), no connection can be established. If I click on "Alternative licence activation", the option "Offline activation" is disabled. How can I activate my Passolo 2018 on an Windows 2019 remote desktop server?
After the license is activated in License Manager you can connect Passolo by clicking on Activate > Alternative activation options > Use a license server > type "internal.licensing.sdl.com" > click "Connect".
I had another License Manager that I downloaded from the relevant section of my RWS profile. I have downloaded the one from your link and when I wanted to install it, I saw that it's called Trados License Server Manager. Does that work for Passolo?
Make sure you have the correct license file in the correct location. Under Windows, the xpauth.xpr file should be placed in the Xpress bin directory (the directory on the path containing the Xpress DLLs). If you are using the XPAUTH_PATH environment variable on Windows, check that it is set to the full path to your license file. (We recommend not setting XPAUTH_PATH on Windows, and instead placing xpauth.xpr in the Xpress bin directory.) Under Unix, the XPAUTH_PATH environment variable must be set to the full path of the xpauth.xpr file.
Note: Previous releases of Xpress used the XPRESS environment variable to locate the license file. This is now deprecated in favour of the XPAUTH_PATH environment variable. When troubleshooting licensing issues, make sure that XPRESS is not set.