Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.


lchiu7

6521 posts

Uber Geek
+1 received by user: 543

Trusted

#207917 19-Jan-2017 13:16
Send private message

Helping a friend with a project where he wants to host a simple site in Azure using IIS (2012R2).

 

Got the server up and running and IIS installed and running. If we point our browser to the Microsoft provided DNS, it shows the default IIS page

 

 

 

 

My friend wants to deploy a different site which he's built already on the server but with a different port.

 

It shows up okay on the server with localhost:777

 

but we can't work out how to get external access. I have created a network security group to route port 777 to the server (I did it for 80 and 443 also and I see 3380 was on by default of course).

 

Our external DNS is <name>.australiasoutheast.cloudapp.azure.com

 

What I have done also is look at IIS binding and try to bind port 777 to the internal IP and use the above as the host name but I get an error invalid host name. If I leave the host name blank it saves but external access doesn't work.

 

Have I missed out something fundamental?

 

Thanks





Staying in Wellington. Check out my AirBnB in the Wellington CBD.  https://www.airbnb.co.nz/h/wellycbd  PM me and mention GZ to get a 15% discount and no AirBnB charges.


Create new topic
Killerkiwi2005
374 posts

Ultimate Geek
+1 received by user: 85

Trusted

  #1705810 19-Jan-2017 14:45
Send private message

  • Check the IIS site binding is on the correct IP (not just 127.0.0.1)
  • Check the windows firewall on the VM is allowing the port
  • Double check the azure firewall



Inphinity
2780 posts

Uber Geek
+1 received by user: 1184


  #1705818 19-Jan-2017 14:55
Send private message

You will have to browse to <name>.australiasoutheast.cloudapp.azure.com:777 , I presume you are doing so


lchiu7

6521 posts

Uber Geek
+1 received by user: 543

Trusted

  #1705900 19-Jan-2017 15:50
Send private message

Thanks. Both good suggestions. I hadn't considered that the internal firewall might stop inbound traffic on port 777 but had considered the external Azure security group rule.

 

We are using the full DNS:777 for the URL.

 

Not sure what is meant by the correct internal IP? The default is * but I also tried the actual internal IP (as on the adapter) and that didn't work either.

 

Do I need the host name in the Bindings as I could not work out what that host name would be.





Staying in Wellington. Check out my AirBnB in the Wellington CBD.  https://www.airbnb.co.nz/h/wellycbd  PM me and mention GZ to get a 15% discount and no AirBnB charges.




lchiu7

6521 posts

Uber Geek
+1 received by user: 543

Trusted

  #1705932 19-Jan-2017 17:30
Send private message

Firewall rule change fixed it. Thanks





Staying in Wellington. Check out my AirBnB in the Wellington CBD.  https://www.airbnb.co.nz/h/wellycbd  PM me and mention GZ to get a 15% discount and no AirBnB charges.


Create new topic








Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.