Hello @Xander Traptow ,
This will be due to one or more of the below reasons:
- There is an NSG at the subnet level as well which is blocking the port.
- There is a firewall on the VM its self (windows firewall etc.).
- There is nothing listening on that port.
You should check your service first. To find specified open port, use find switch. For example, to find if the port 560 is open or not, do netstat -an |find /i "560" command. The service should listen on 0.0.0.0 not 127.0.0.1.
The article you are referring assumes that you've already started the appropriate services and opened any OS firewall rules on the VM prior to opening the ports in NSG rules. If there is no service running on port 560/561, opening those ports in NSG rule will not help.
Kindly let us know if the above helps or you need further assistance on this issue.
----------------------------------------------------------------------------------------------------------------
Please "Accept the answer" if the information helped you. This will help us and others in the community as well.