iis 8 website not opening - iis

I have create new web site in IIS 8. I have configured my web site like this
http://ip:8080/
When I browse it from any public network it is not opening. But If I open is locally it works fine. http://localhost:8080 it is working fine. What I tried I stop all other sites, Default Web site and assign 80 port to my site then it is working fine in locally as well as publically. I don't know what is the issue.

Clearly you have a firewall or other network routing issue. Check all configured firewalls on your server/housing machine, as well as along your network path (router, or other perimeter network devices)
Also if trying to connect through your internet side IP you will want to check any port forward rules on your router (If behind NAT, like most connections are)

My problem is solved. I have opened a 8080 port on Azure management portal. And on VM I have create new rule which points to this port.

Related

IIS site binding issues

I have a site that I can run locally, but it's not accessible from my URL.
Here are the steps I've taken.
I have an A record created to my external IP.
My firewall has an access rule to allow the port I designated to be allowed in to the network from the WAN interface
I have a NAT rule to send any traffic on that port to the IIS server running the site.
I have disabled the Windows Firewall.
When I try and a get to the site via the URL + the port I get an error. See the image below.
What have I missed??

IIS 10 new website with custom port number can't be accessed from Internet

So I deployed a new website in IIS 10 with port number 8888 (the Default Web Site uses port 80).
I can successfully browse the website locally on the server. However, I can't visit it from another PC using Internet. The browser complains 'Hmmm.. can't reach this page'.
The firewall on server has been manually shut down.
I also checked that port 8888 is listening on my server.
Did I miss any steps here?
All right, I got it work... Turns out the cloud service that I use shut down accesses to almost all ports except port 80 by default... After I open port 8888 on the cloud settings, everything works.
Actually #NJUHOBBY is right, I use Google Cloud and I had to go over
Google Cloud Console -> VPC Networks -> Firewall Rules -> Create Firewall Rule
...to create a new rule. Please be aware that Firewall Rules are applied to VM through TAGS, so if you choose to use https-server tag this rule will apply to all your VM's (this is tag is assigned to all server instances by default). In my case I set a custom tag and then I added this tag to my VM like this:
Compute Engines-> VM Instances.
Then I clicked my server's vm name and clicked Edit then I added the custom tag in the appropriate field. After saving VM's properties, the port was successfully opened.

Unable to access my .net website from internet

I am new to networking and routing.
I have hosted my website (enabled https) in azure vm having firewall settings. Have opened the ports for the websites.
But still unable to access my website from internet.
I have 2 sites running. the main website which is running on port 443. To access this site , it is directed to openid oauth2 identity site running on port 44300. Both the ports are opened. The site is running perfect when i access from the hosted server and also other servers.
I am trying to access this main site from my home internet. It is not working.I want to access this site from internet as well.
additional info:
Main website hosted in server which is connected to internet with a Connection which has got a IPv4 Default Gateway - eg; A
My own pc connected to internet with a different connection with different IPv4 Default Gateway.
With this above setup, it is possible to achieve my requirement?
Can anyone help what has to be done to access my website from outside world?
Thanks

Azure Virtual Machine / Windows Server 2012 and "This web page is not available" error

I have just created an azure virtual server 2012 and made a simple html page.
I installed IIS on it, and added an endpoint to my portal, called it web and set it to tsp, 80, 80, no load balanced.
But when I try to go to my domain, I get an error saying page not available.
I can login to my virtual server and run the page inside. So it works.
But it's blocking outside access.
There is also a firewall rule on the server allowing incoming traffic on port 80.
I am probably missing a step somewhere, but I could not find any instructions on how to do it. It is mostly guess work on my side.
Can anyone help?
Most probably you have forgotten to allow port 80 for incoming connection on the local Firewall of your Windows Server.
UPDATE
Have you correctly mapped "your domain" to the couldapp.net domain of the VM instance? Or are you using the yourname.cloudapp.net directly?

Can't connect to Default Web Site in IIS 6.0

I can't connect to the default web site in IIS 6.0 using localhost or 127.0.0.1 or by server name. When I telnet to port 80 with one of these names, there's no connection.
However other web sites are running and I can telnet using any of the ip addresses.
I can ping to localhost where 127.0.0.1 is responding.
The default web site is running. It's not stopped.
check the windows firewall, that has a habit of blocking IIS on a local machine
Is the default site bound to a specific IP address? By default it would display "all unassigned" for the IP, but if you've linked all sites to a specific IP address, then the local IP would no longer be configured on the server and would not answer.
httpcfg.exe did it.
Stop all the sites under IIS, restart IIS and start the one you're interested in.
If this fails delete all the sites under IIS and create from scratch. If this fails, the problem is not with IIS and you'll need to look at what other services are running and start turning them off.
A firewall may prevent some content of your website/website itself from being accessible, so if you have problems with accessing content then check that your firewall is not rejecting content from your site.
The easiest way to ensure that your firewall is not blocking your access to your site services is to use your firewall control panel to allow data from *.(your site url).

Resources