Solved

New website on Windows Server 2012 (IIS 7)

Posted on 2014-12-10
3
223 Views
Last Modified: 2014-12-11
We have a 2012 web server that serves multiple websites.  I have been asked to add another website without a domain name, just the IP.  For instance instead of the usual binding to www.domainname.com they want to use just the IP xxx.xx.xxx.x:port#/home.htm.  

I believe I have a permission issue as I have set up the site (and I have also set up the application pool for this site.)  in IIS with the necessary bindings (also using a different port then 80), and can view the site on the local host using xxx.xx.xxx.x:port/home.html (and localhost::xxx/home.html), but I can not view the page over the web.  As soon as I try to access the site via the web, I get a waiting for xxx.xx.xxx.xx and finally the page fails.I added the IUser account to the home directory folder and have given it read and write privileges.  

However, I do not get a 403 when I try to navigate to the page.  It just says that they page can't be displayed.  Firefox indicates that the connection timed out.  The server only has one IP and uses hostnames to direct the webpages to the correct application.  This could be the problem as I'm not using a hostname (just the ip), but was hoping that the IP:port format would overcome this (I'm not an IT guy -- just wearing that hat today!).

I've been looking at articles on the web for a solution (and there's a lot), but everything that they suggest to do I've done.  I'm missing something, not sure what....Any suggestions?
0
Comment
Question by:badrhino
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
3 Comments
 
LVL 42

Accepted Solution

by:
kevinhsieh earned 500 total points
ID: 40493226
Sounds like you have a firewall issue. It could be on the server, but it is more likely to be the firewall that protects the network where your host is at. By default, a firewall should only permit inbound traffic to tcp/80 and tcp/443 from the internet. If you want to run traffic to a different port for this web site, that will need to be made explicitly clear to whomever manages the firewall.
0
 
LVL 81

Expert Comment

by:David Johnson, CD, MVP
ID: 40493325
did you forward the applicable port to your webserver?
0
 
LVL 1

Author Closing Comment

by:badrhino
ID: 40493823
Perfect. Thanks!
0

Featured Post

Does Powershell have you tied up in knots?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The following article is comprised of the pearls we have garnered deploying virtualization solutions since Virtual Server 2005 and subsequent 2008 RTM+ Hyper-V in standalone and clustered environments.
When it comes to showing a 404 error page to your visitors, you do not want that generic page to show, and you especially do not want your hosting provider’s ad error page to show either. In this article, I will show you how to enable the custom 40…
In this Micro Tutorial viewers will learn how to use Windows Server Backup to create full image of their system. Tutorial shows how to install Windows Server Backup Feature on Windows 2012R2 and how to configure scheduled Bare Metal Recovery backup.…
In this Micro Tutorial viewers will learn how to restore their server from Bare Metal Backup image created with Windows Server Backup feature. As an example Windows 2012R2 is used.

739 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question