I have a VM on Azure running Windows Server and IIS. I have also set up a couple of websites that work fine within the VM. I'm trying to access a website binded to port 80 using the public IP set up, nevertheless, I can't make it work. So far, I've done the following: Allow port 80 in NSG Associated NSG to my subnet Open port 80 in Windows Server Firewall (right now, I have the firewall off completely just in the meantime I find the solution) Could somebody shade some light on this problem? Thanks!

Thanks to @msrini-MSFT , I've figured it out that the Azure VM was not set up to listen to the private IP. The solution, in this particular case, was to run the following command: netsh http add iplisten 10.0.5.4 Hope it helps!

Can you please share the netstat-ano output from your cmd prompt of the Web server? Also , I checked from my end to the IP which you have shared, it works fine with port 3389. I can say that the port 80 is not blocked by the platform.

Unable to access my public IP using port 80

Paris Pantigoso 96

I have a VM on Azure running Windows Server and IIS. I have also set up a couple of websites that work fine within the VM.
I'm trying to access a website binded to port 80 using the public IP set up, nevertheless, I can't make it work.
So far, I've done the following:

Allow port 80 in NSG
Associated NSG to my subnet
Open port 80 in Windows Server Firewall (right now, I have the firewall off completely just in the meantime I find the solution)

Could somebody shade some light on this problem?
Thanks!

Accepted answer

Paris Pantigoso 96 Reputation points

2020-03-06T16:32:04.5+00:00

Thanks to @msrini-MSFT , I've figured it out that the Azure VM was not set up to listen to the private IP.
The solution, in this particular case, was to run the following command:

netsh http add iplisten 10.0.5.4

Hope it helps!
Please sign in to rate this answer.
msrini-MSFT 9,261 Reputation points Microsoft Employee

2020-03-06T16:36:00.697+00:00

Please mark the response as answered to help other community members

Joydeep Banerjee 1 Reputation point

2021-04-07T03:46:41.447+00:00

Worked for me! Thanks!
Sign in to comment

1 additional answer

msrini-MSFT 9,261 Reputation points Microsoft Employee

2020-03-05T12:22:31.407+00:00

Can you please share the netstat-ano output from your cmd prompt of the Web server? Also , I checked from my end to the IP which you have shared, it works fine with port 3389. I can say that the port 80 is not blocked by the platform.
Please sign in to rate this answer.

1 person found this answer helpful.
Paris Pantigoso 96 Reputation points

2020-03-05T12:58:44.79+00:00

Hi msrini-MSFT, please find attached the file requested.
It's right, I have remote access using port 3389
I can even ping port 80
Nevertheless, when browsing http://bm3testing.westus2.cloudapp.azure.com:80 or http://bm3testing.westus2.cloudapp.azure.com:8082 (I have both websites exposed in IIS), nothing happens.
Thanks.

3852-netstat.txt

msrini-MSFT 9,261 Reputation points Microsoft Employee

2020-03-06T04:52:04.587+00:00

The private IP which you mentioned in the screenshot and the IP in the netstat output doesn't match. Are you looking at the wrong machine with the same name ?

Paris Pantigoso 96 Reputation points

2020-03-06T12:25:17.637+00:00

I'm afraid I don't follow. My private IP is 10.0.5.4 according to Azure screenshot configuration.
What should I do?

msrini-MSFT 9,261 Reputation points Microsoft Employee

2020-03-06T13:57:25.517+00:00

In the netstat output, I see 192.168.0.7 IP as local.

TCP 192.168.0.7:139 0.0.0.0:0 LISTENING 4
TCP 192.168.0.7:49691 52.177.166.224:443 ESTABLISHED 3488
TCP 192.168.0.7:49777 52.177.166.224:443 ESTABLISHED 13068
TCP 192.168.0.7:49933 40.97.154.242:443 ESTABLISHED 12856
TCP 192.168.0.7:49951 40.97.154.242:443 ESTABLISHED 12856
TCP 192.168.0.7:50062 184.26.134.121:443 CLOSE_WAIT 9320

Paris Pantigoso 96 Reputation points

2020-03-06T14:02:05.157+00:00

I think I captured my local PC netstat mistakenly when switching to the VM. Here is the netstat file verified with the right IP.3961-netstat2.txt

msrini-MSFT 9,261 Reputation points Microsoft Employee

2020-03-06T14:10:42.237+00:00

Seems like the web server is listening on port 80 of the IPv6 address. I cannot see port 80 on local address 0.0.0.0:80.

Paris Pantigoso 96 Reputation points

2020-03-06T14:17:24.913+00:00

How can I fix it, please?

Paris Pantigoso 96 Reputation points

2020-03-06T14:32:26.657+00:00

]Here's my subnet configuration. As you can appreciate, the NSG is bind with all ports open.
How can you tell IPv6 is the protocol listening and not IPv4. Whatismost, could you please tell me how to fix it?
Thank you!

msrini-MSFT 9,261 Reputation points Microsoft Employee

2020-03-06T14:35:49.48+00:00

It is on the guest OS level. From the platform perspective all seems to be fine

Paris Pantigoso 96 Reputation points

2020-03-06T14:39:59.267+00:00

I'm sorry to insist, but this is absolutely new for me. Any clues or a link to research about how to deal with this, please?

msrini-MSFT 9,261 Reputation points Microsoft Employee

2020-03-06T14:51:15.75+00:00

Can you share me the binding config of your IIS?

Paris Pantigoso 96 Reputation points

2020-03-06T14:58:32.363+00:00

Sure! Here they are!
By the way, how is that SonarQube server on port 9000 is accessible from outside whereas neither port 80 nor port 8082 does?

Paris Pantigoso 96 Reputation points

2020-03-06T16:30:33.02+00:00

Solved! I found the following command to listen to local IP address:

netsh http add iplisten 10.0.5.4

Thank you for leading me to the solution!
Sign in to comment