Tools

Unable to access Web Help Desk after installing DameWare

This article describes how to access Web Help Desk after you install DameWare on the same server. Both applications use the same port for communications, which creates a port conflict.

First published date

11/29/2018 10:59 PM

Last published date

8/11/2022 2:50 PM

Overview

After you integrate DameWare with Web Help Desk, you cannot access Web Help Desk.

Product section

Web Help Desk

Resolution

Environment

All Web Help Desk versions
Web Help Desk is using Apache Tomcat as an http engine on port 443.
DameWare and Web Help Desk are installed on the same machine.
DameWare is using http.sys (IIS engine) on port 443.

Workaround

Perform one of the following procedures:

Run Web Help Desk using https on another port (such as port 444). The Web Help Desk and DameWare integration runs correctly when both products are using separate ports.
Run Web Help Desk and DameWare on the same port with separate IP addresses or network interfaces.
If you cannot start Web Help Desk due to certificate errors, generate a new certificate. See Using SSL certificates in Web Help Desk for instructions.
Install DameWare and Web Help Desk on separate servers.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.