I have an umbraco website on the server here, IIS 7. It is set to port 83 while the other existing site is on 80.
The other site is accessible from outside the server but the umbraco site is not. I assume that I need to allow traffic for this port or something but I have no idea where, how or what.
Related
I have hosted a web site to Windows server 2012 r2. I've bind 83 port to this site.
When I hit site http://www.example.com it open IIS services page but when I'm hitting
http://www.example.com:83 it saying This site can’t be reached.
But after making firewall disabled, I can access this site by IP address as http://0.0.0.0:83.
Edited:
Can access by using domain name when using port 81
Assuming a Windows Server 2012 VPS:
It seems that many tutorials include the setting up of DNS Server (setup of forward lookup zones, and A record) as part of the basic steps to deploy and run an ASP.NET web application on IIS.
I'm slightly confused, because within IIS manager you can set the bindings ( IP address, URL, SSL, port) of a web application. Wouldn't this alone not suffice to correctly route incoming requests to the correct web application?
What would be the advantage to running DNS Server?
IIS Manager can only manage IIS related Windows settings, but to make a site work you need much more settings than that.
DNS settings are critical to direct web browsers to your side. Nobody uses IP addresses to access a site, so a typical URL uses domain name. That requires DNS to translate the domain name to an IP address so that browsers can send HTTP packets to the proper location.
IIS Manager could not manage that for you, as which DNS product to use or how to configure it is usually vendor specific and out of IIS's scope.
I have a window server 2008 with an IIS 7.0 and Static IP. The website www.xyz.com (with PORT: http:80 & https:443) is running well on it. Now, I deployed another website on it using same IP address but with Port http:180. The another website is working good locally but not accessible on web.
What are next steps to make website online?
Regards,
Aman
That should be it. If you can access it locally with http://localhost:180, then IIS is listening on the port and should be serving requests. If you are not able to access it remotely via http://the.site.ip.address:180, I would suspect that a firewall somewhere is preventing connections over this non-standard port.
I am trying to figure out why my web page isn't displaying when using my domain name. I have a local IIS 7 web server installed with an ASP.NET web site. When I go to http://localhost, my page displays fine. When I go to http://www.mysite.com, it doesn't display though. Doing a trace route on www.mysite.com shows that it is resolving to my IP address. My router is forwarding port 80 requests to the web server and I am browsing from my phone, which is on a separate IP address using 3G. I disabled my firewall and my anti-virus to make sure neither of those are interfering. I also looked at the IIS 7 log and my request does not appear to be hitting it.
Is there a way to trace the incoming request to find out where its getting thrown out at? I'm losing my mind trying to troubleshoot this and any help would be appreciated.
Is your ISP blocking port 80? I have seen lots of ISP's do this to home users in an attempt to have them upgrade their internet package to a business plan.
I would like to configure IIS server at (Windows server 2003) for domain name mapping.
We have purchased domain name for one of our newly created website.
I would like to know how can I configure IIS so that anybody from outside world can reach website by typing URL.
As in: http://example.com/ should redirect to my the home page of my website.
I have made website in using ASP.NET and Oracle.
How can I do this?
You need to register your domain on a DNS server, which is different (though could be the same physical box) as your IIS server. Long time since I've done this myself, as I use a hosting company for this kind of thing, but you will typically need at least two DNS Server IP addresses typically for a domain (primary and secondary DNS servers). There is a DNS Server for the windows server platform, but most people use hosting services to do this thing.
By the way, you might get a better response posting this kind of question on serverfault.com, as it's not really a developer question.