Our production server is a Windows server running Windows Server 2012. IIS by default binds to all existing IP addresses on the server. We need to ensure:
None of the web sites served by IIS are bound to our dedicated IP address.
The dedicated IP address is removed from IIS's IP listen pool so no future website will bind to it.
Below are the steps to check and update bindings and remove the IP from the IIS IP pool.
1
Check site bindings in IIS
For each site in IIS open the Site Bindings dialog and verify the site is bound only to the IP address designated for that site.
Example: the prime.fmsoft.net site initially had bindings for all IPs:
Site bindings showing all IPs
You can ping the hostname to confirm which IP it resolves to (example shows it resolves to 82.113.145.191):
Ping showing IP resolution
Verify and update bindings as needed:
Edit bindings dialog example 1
Edit bindings dialog example 2
2
Remove the dedicated IP from IIS IP listen pool
Follow the procedure described in the "Running the Dedicated Server on Default Ports" section (link preserved):
https://unigui.com/doc/online_help/running-the-dedicated-server-o.htm
Run the following commands (example screenshot):
Command prompt showing netsh commands
Example commands (run in an elevated command prompt):
Commands to remove IP from iplisten
3
(Optional) Make IIS listen on localhost too
If you need IIS to listen on localhost, add this command as well:
4
Verify the configuration
Run:
Example verification output:
Verification that dedicated IP is removed
The output should show that the dedicated IP (e.g. 82.113.145.152) is no longer present in the IIS iplisten list.
Make sure you updated bindings for every IIS site so each site is bound only to its intended IP address before removing the dedicated IP from the iplisten pool.
