> For the complete documentation index, see [llms.txt](https://docs.soraco.co/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.soraco.co/docs/troubleshooting/diagnosing-network-connectivity-issues-with-the-qlm-license-server.md). # Diagnosing network connectivity issues with the QLM License Server I**mportant Note:** *Diagnosing network connectivity issues between a client's computer and the QLM License Server is beyond the scope of the technical support provided by Soraco.* The QLM API used by your application communicates with the License Server over http (port 80) or https (port 443). On most systems, these ports are open for outbound communication. Connectivity issues between a client and the QLM License Server can be due to several reasons. Here are some reasons why communication may fail: * A firewall is blocking outbound connections to the QLM License Server. * The client uses a proxy server that requires authentication in order to connect to the internet. * The URL to the License Server is incorrect or the DNS name used in the URL does not resolve. * The URL to the License Server uses https and the server certificate is invalid or expired. * The QLM License Server is blocking the IP address of the client Troubleshooting steps: * Open any browser on the end user system and paste the URL to the QLM License Server. * If the URL does not return any result, you should ask the customer's IT team to diagnose the issue. * If the URL resolves properly, the issue could be a firewall rule that blocks applications (except the browser) from connecting to the internet. The issue could also be that the browser is configured to use a proxy server. If this is the case, you need to configure QLM to use a proxy server as well. If you are using any of the QLM .NET controls or the QLM License Wizard, all that is required is to set the Proxy Server properties to the correct values. If you are using your own activation form, you can use the QLM API to set the proxy server settings. The QlmNetworkTester tool can be used to test network connectivity to the QLM License Server. QlmNetworkTester requires as input the settings xml file generated by the "Protect your application" wizard. This xml file is typically used as an argument to the QLM License Wizard. If you do not have this xml file, you can generate it as follows: * Launch the QLM Management Console * Go to the Protect your application tab * On page 2, select your product, your license server and your programming language * On page 3, click Next (no changes required) * On page 4, set QlmStoreKeysLocation to Registry or File depending on which option you selected for your application then click Next * On page 5, select a temporary location to save your customizations and click Save * Several files will be created. The file with an extension lw\.xml is required as input for the QlmDeleteKeys application. To run QlmNetworkTester: * Copy QlmNetworkTester.exe and QlmLicenseLib.dll from the QLM installation folder to a new folder on the customer's system that's experiencing network connectivity issues. * Execute QlmNetworkTester.exe * Click the ... button and select the location of the settings xml file. * Click Test Connection * Click Finish when done --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.soraco.co/docs/troubleshooting/diagnosing-network-connectivity-issues-with-the-qlm-license-server.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.