New website on Windows Server 2012 (IIS 7)

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?
LVL 1
badrhinoAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

kevinhsiehCommented:
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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
David Johnson, CD, MVPOwnerCommented:
did you forward the applicable port to your webserver?
0
badrhinoAuthor Commented:
Perfect. Thanks!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft IIS Web Server

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.