Objective
This article guides you through configuring ADSelfService Plus to run on a specific IP address on your server. This configuration is essential when you have multiple applications sharing the same server and need to assign dedicated HTTP (port 80) or HTTPS (port 443) port numbers to each of them. By binding ADSelfService Plus to a specific IP address, you can avoid port conflicts and ensure each application uses its intended port on its designated IP.
Prerequisites
Administrative access to the machine running ADSelfService Plus
A valid unused static IPv4 address to bind to ADSelfService Plus
A backup of relevant configuration files before making any changes
Steps to follow
Step 1: Add a virtual IPv4 address (if needed)
If you do not already have a dedicated network interface card available, you'll need to add a virtual IP to your existing network adapter.
Go to Start > Settings > Control Panel > Network Connections.
Right-click Local Area Connection (or the appropriate network adapter) and select Properties.
In the dialog box, select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
Click Advanced.
Under IP Addresses, click Add... and enter your new IP address along with the subnet mask.
Click Add to confirm, then OK on all open windows to apply the changes.
Step 2: Bind ADSelfService Plus to the specific IP address
Stop ADSelfService Plus:
If running as an application: Navigate to Start > All Programs > ADSelfService Plus > Stop ADSelfService Plus.
If installed as a service: Open Run (Win + R), type services.msc, press Enter, then locate and stop the ManageEngine ADSelfService Plus service.
Open the system_properties.conf file located in <ADSelfSelfService_Plus_install_dir>\conf (default: C:\ManageEngine\ADSelfService Plus\conf) using a plain text editor (e.g., Notepad or Notepad++).
Add the following entry at the end of the file:
bindaddress=<ip_address>
Example:bindaddress=192.168.111.162
Save the file.
Step 3: Remove IP bindings (if the ADSelfService Plus IP was previously used by IIS)
This step is necessary if the IP address you are assigning to ADSelfService Plus was previously bound by IIS, especially for ports 80 and 443.
Open Command Prompt in elevated mode. Go to Start > Run, type cmd, then right-click Command Prompt and select Run as administrator.
Execute the following command to remove any existing IIS bindings for that specific IP:
netsh http delete iplisten ipaddress=<IP_address_of_ADSelfService_Plus>
Example: netsh http delete iplisten ipaddress=192.168.111.162
Restart IIS to apply the changes. You can do this by running iisreset in the elevated Command Prompt or through IIS Manager.
Note: This ensures that IIS does not reserve the same IP, which could conflict with ADSelfService Plus. Step 4: Change the port number in ADSelfService Plus
Back up the server.xml file located at <ADSelfSelfService_Plus_install_dir>\conf (default: C:\ManageEngine\ADSelfService Plus\conf). This file contains the port configuration.
Start ADSelfService Plus. (You might need to access it via its current IP and port for this step before it fully switches to the new IP.)
Log in to the ADSelfService Plus portal with administrator credentials.
Navigate to Admin > Product Settings > Connection.
Under General Settings:
Change the ADSelfService Plus Port [http] to 80.
If SSL [https] is enabled, set its port to 443.
Click Save. In the prompt that is displayed, click the Restart Now link to apply the new port settings. You can also restart the service manually from the services.msc menu on the server.
Validation and confirmation
After completing the configuration steps:
Verify access: Try accessing ADSelfService Plus using the new IP address and the configured port: http://<new_IP_address>:port_number or https://<new_IP_address>:port_number.
Check other applications: Ensure that any other applications on the same server that use ports 80 or 443 are still accessible via their respective IP addresses or hostnames.
Troubleshooting tips
If ADSelfService Plus fails to start:
Review the system_properties.conf file for any syntax errors.
Check the wrapper.log file (located in <ADSelfService_Plus_install_dir>\logs) for any errors.
Ensure the IP address you specified is valid and assigned to the server's network adapter.
Connectivity issues:
Verify that no firewall (e.g., Windows Firewall, a network firewall, or antivirus software) is blocking communication on the new IP address or ports (80 or 443).
Check IIS bindings using the command netsh http show iplisten to confirm that ADSelfService Plus's new IP is not listed under IIS bindings. If it is, repeat step three.
General
Best practices
Always back up configuration files before making any changes.
Use a dedicated IP address for each application to avoid conflicts and simplify management.
Monitor network connectivity and firewall settings after configuration.
Test thoroughly in a non-production environment first, if possible.
How to reach support
If the issue persists, contact our support team here.