Troubleshooting

This chapter provides troubleshooting information for common issues encountered with Milan Manager.

Milan Manager Failed to Bind Port on Windows

On some computers, launching Milan Manager may fail with a fatal error message:

There are two known root causes for this issue. Firewall and TCP dynamic port range.

Firewall

A personal firewall might be blocking Milan Manager's internal communication.

Solution

Ensure that the firewall allows access to Milan Manager.

TCP Dynamic Port Range

Windows reserves certain TCP ports for dynamic use during runtime. Even if these ports are not actively in use, they may be blocked for other applications. The TCP ports used by Milan Manager might fall within this dynamic range and need to be excluded.

To check the current port range in use, open a PowerShell window with administrator rights:

1. Press WIN + X, then release both keys and press A.
2. Within the PowerShell window, display the current dynamic port range:

   netsh int ipv4 show dynamicport tcp

3. List existing exceptions:

   netsh int ipv4 show excludedportrange protocol=tcp

Solution

To exclude the ports used by Milan Manager from the dynamic port range, execute the following commands in PowerShell with administrator rights:

1. Press WIN + X, then release both keys and press A.
2. Stop the Windows driver managing the dynamic port range:

   net stop winnat

3. Exclude the TCP ports used by Milan Manager:

   netsh int ipv4 add excludedportrange protocol=tcp startport=60061 numberofports=3

4. Restart the Windows driver managing the dynamic ports:

   net start winnat

In rare cases, if one of the ports was already excluded, the second command may fail. Instead, add the ports individually using:

netsh int ipv4 add excludedportrange protocol=tcp startport=60061 numberofports=1

netsh int ipv4 add excludedportrange protocol=tcp startport=60062 numberofports=1

netsh int ipv4 add excludedportrange protocol=tcp startport=60063 numberofports=1