why can't web site not accessible using port 83? - asp.net

I have hosted site to windows server 2012 r2.
I have bind site by port 81,83,2163.
It is accessible using all other port except port 83 using domain name as well as
with IP, but when I'm accessing using port 83 with domain name it is not accessible, but it is
accessible using IP with port 83.
I have disable firewall still not working, why?
Edited

From the Bindings list, select the Port 83 binding, and click "Edit." From the dialog, specify the fully-qualified domain name for the site in question as the "host name." This allows IIS to respond to the request for the website via the desired domain name reference.

Related

multiple domains on windows azure virtual machine

I have created windows azure virtual machine and opened port 80 default website that is myapp.cloudapp.net then I have pointed my custom domain www.mycustomdomain.com to myapp.cloudapp.net it is working fine. I have created another website in iis with port 81 I have checked it is working on vm but I would like to add another custom domain to the website on 81 , I don't understand how to do that because ip and dns is same , how to give custom domain to 2nd website?
Domains should be set up in IIS. You will need to define host headers for each website hosted on the server. This also means you don't have to define non-standard ports.
Configuring host headers

How to access my sites on IIS 7.5 from outside my network on Windows Server 2008

I'm new to Windows Server 2008 and IIS, so please be patient.
I want to access my sites from outside my network.
I can browse my sites from the localhost, it's working.
I've added a binding to my site, Type: http, Host Name: www.dev.com, port: 80.
I have a static IP from my ISP, and my router is forwarding http requests to my server.
If I remove the Host Name and access directly using my network IP address, I get my site, but I want to provide a host name to the site because I'm going to add another web sites.
I've added www.dev.com to the DNS with my IP address.
What should I do next?
Thanks
I found the answer to what I was looking for, I should've done this:
create virtual application www.dev.com under default website on IIS,now I can access the website using STATIC_IP_ADDRESS/www.dev.com .

How to open a website by entering its name, not the IP address of the server

I have created a website and set it up on IIS on a Windows Server 2008 R2 which is on the local network. What should I do to be able to access that website by typing its name in the browser from client machine? Right now there're only two sites: One is the Default Website and the other one is my newly created one. If I type this IP in the browser of a remote computer, which has access to the server, the default website opens. If I add https:// to the ip address I get directed to my website. This means the website opened is decided upon the protocol (http or https). What if I add another website that would require SSL?
Actually the site you browse to is not decided by the protocol, it's decided by the port. By default HTTPS is port 443, and HTTP is port 80.
So if you have an HTTPS and HTTP protocol added to a website in IIS, you've created bindings for these two ports automatically.
This is visible by going into IIS clicking "Sites" from the "Connections" section in the left pane and then looking at the "Bindings" column in the center pane.
If you create another website on the host which uses SSL you would have to assign it to a different port.
To browse to that new SSL website you would have to enter the port when browsing to it.
e.g. https://serverName:444
(You don't have to enter default ports, 80 & 443, your browser automatically infers which to use from the protocol type and adds them if no other is present)
This is inconvient for users so people get around this by registering domain names such as stackoverflow.com and pointing them to the address with the port e.g. https://stackoverflow.com:444, so users don't have to enter port numbers.
Have you added the website address to the host file which sits in the drives folder of the system32. If you add the website name against the IP in the host file you should be able to access it using the name rather than than IP address
Something like this- 10.18.20.108 test.stackoverflow.com

How to access multiple website using different bindings on IIS 7.5

How can I access different websites hosted on my local IIS 7.5 (using different bindings) from my ipv4 address?
My system32\drivers\etc\host file has my binding names mapped to 127.0.0.1
In IIS, I have the normal "Default Web Site". Its binding hostname is empty, set to all unassigned ip address and port 80. On my network, I can access this site using the server ipv4 address like so : http://192.168.2.1/mySubSite/index.html where mySubSite is a child folder of the "Default Web Site". I can also access it locally using http://localhost/mySubSite/index.html
If I setup a second website in IIS using the same binding as the "Default Web Site" but using a hostname (say "site2"), I can access it locally using http://site2/mySubSite/index.html.
How can I access this second site on my network the same way I access the "Default Web Site" using the ip address? Is it possible?
the easiest way to do this is to change the port binding on each website. This takes minimal configuration and you can place a website on any port you want (I recommend ports over 1024...to a maximum of 65000)
For example, your default site will automatically be on port 80. Place site 2 on Port 2000. Then you can access your default site like you have above, and you can access site 2 with a similar url like http://192.168.2.1:2000/mySubSite/index.html. Notice the port is specified in the url using the :[port] at the end.
Yes, you can have multiple sites on the same IP address and port. It is called binding by domain name.
Open ISS and go to your first default site (one that is functional) and then go to edit bindings. You will see by default it states "http: Port 80 IP Address *"
Notice the hostname is blank? This is where you can tie a domain name to that exact port. Fill out domain name on both your site bindings. This means when someone comes in from that exact domain name, it knows where to forward traffic too. If port 80 inbound doesn't match either of those two domain names, it will default to w/e site has no bindings such as the "default site".

Running asp.net site on Windows Server 2003 and accessing it over LAN

I want to run an ASP.Net application on Windows Server 2003 and access it over a LAN.
Like http://serverIP/sitename.com
How do I do this? What configuration changes should I make to IIS?
There are 2 scenarios (assuming you want/have to use IP's in the URL):
You site is the only web-site running on your web-server - you can set up your site with the default port 80 binding, i.e. you don't specify a host name or IP address. This means any request on port 80 will route to your site (remember to stop or delete the "Default" web site, as it normally has the default port 80 binding)
You have multiple sites running on your server - you need to assign an additional IP address for that server and specifically use that IP in the http binding for you site.

Resources