I am unable to open Azure's VM port

0
votes

What i have tried so far...

  1. Created azure VMs both on Classic and ARM.
  2. Created end points of classic and ARM machine(NSG) port:9000
  3. Open allow port 9000 in firewall on Windows Server R2 Datacenter
  4. Check port status on check-host.net
  5. Default Port status (Remote Desktop) is open, other ports are closed.

This is how i have created my end point in azure classic VM & Make New Firewall Inbound Outbound Rules.

enter image description here

Test Result of My Custom Port (Closed) & Remote Desktop Port (Open):

(I'm going to add my second image as a link in the comments)

Sorry for improper way of screenshots..actually i am new here so i can post only upto two links.

2
azureazure-virtual-machine
Not exactly sure what's going on here but... There's currently a service outage - azure.microsoft.com/en-us/status - could it be that's the culprit (making changes to the VM would be a service management function, which is what is currently impacted) ? If so, nothing can be done here. If not: Please edit your question to show how you created the endpoints (or NSG). - David Makogon
Thanks for your reply david but... i don't think so there is any service outage issue linked with this because... I have check default port created with azure machine is open while all other ports created by me are closed. - Harram Butt

2 Answers

0
votes

I wrote a short post on how to do this a while ago for HTTP and HTTPS traffic. I think the same process applies in your case:

• The Azure Management Console has to be used to setup Inbound and Outbound security rules.
• This is necessary, for example, to allow HTTP and HTTPS traffic thru to the Azure virtual machine.
• NOTE: The Azure virtual machine will likely be configured with the Windows Firewall on. 
    ○ If the Windows Firewall is on, then it also will likely need to be configured with rules to allow HTTP and HTTPS traffic.
    ○ In this sense, Azure has two firewalls:
        § One firewall managed via the Azure Management Console.
        § Another firewall manage via the Windows Firewall.
• For inbound security rules, the following settings were used to allow HTTP and HTTPS traffic:
    ○ HTTP:
        § Name: Port_80_HTTP_Traffic
        § Priority: 100
        § Source: Any
        § Protocol: Any
        § Source Port Range: *
        § Destination: Any
        § Destination Port Range: 80
        § Action: Allow
    ○ HTTPS:
        § Name: Port_443_HTTPS_Traffic
        § Priority: 101
        § Source: Any
        § Protocol: Any
        § Source Port Range: *
        § Destination: Any
        § Destination Port Range: 443
        § Action: Allow
• For outbound security rules:
    ○ HTTP:
        § Name: Port_80_HTTP_Traffic_Outbound
        § Priority: 100
        § Destination: Any
        § Destination Port Range: *
        § Source: Any
        § Protocol: TCP
        § Source Port Range: 80
        § Action Allow
    ○ HTTPS:
        § Name: Port_443_HTTP_Traffic_Outbound
        § Priority: 101
        § Destination: Any
        § Destination Port Range: *
        § Source: Any
        § Protocol: TCP
        § Source Port Range: 443
        § Action Allow