Use firewall to see which ports are available

afarr

When creating a new service in a development environment (with several other services already created), it can be tedious to find out which ports have not yet been used.

Fortunately, there is an easy work around for that, at least in NAV 2013 (R2), because by default NAV creates an inbound firewall rule for the Client, Soap, Odata ports (but not the management services port).

So just go to Control Panel\System and Security\Windows Firewall, open the Advanced Settings, click on Inbound Rules, and sort by Local Ports to see all the rules that have been created.

GreatScott000

Or you code just use TCP Port Sharing. Before you create any instances use these 2 commands (from CMD.EXE as Administrator)

sc config NetTcpPortSharing start= demand
sc config MicrosoftDynamicsNavServer$DynamicsNAV71 depend= HTTP/NetTcpPortSharing

Now you don't have worry about consuming ports for every instance.

You will have to run

sc config MicrosoftDynamicsNavServer$DynamicsNAV71_2 depend= HTTP/NetTcpPortSharing

if you set up a new service not just a new instance of the base service. Or have existing instances.