IIS Website Only Accessible From Localhost (Server 2008 R2)

I have an IIS website that I can only access via the localhost (obviously on the IIS server).  None of my other networked machines can access it.  The website was a new site on port 5555.  The Default Website running on port 80 is accessible fine by all my other machines.

Any ideas?
Who is Participating?
Brad HoweConnect With a Mentor DevOps ManagerCommented:
you said WIndows7 Firewall. The fireall block is on Port 5555 on the windows 2008 R2 Server.
1. disable the firewall on the server to see if that corrects it. If it does, then turn it back on and open port 5555 outbound/inbound on the 2008 R2 Server.
Jini JoseSenior .Net DeveloperCommented:
you need access the site using the port. like http://machiname:5555 and you should enable anonnymus access on IIs
r270baAuthor Commented:
I am already trying to access it on the actual port

On the local host the following works:

On our other machines however the following does not work:

I did verify that Anonymous Authentication is enabled.
Easily Design & Build Your Next Website

Squarespace’s all-in-one platform gives you everything you need to express yourself creatively online, whether it is with a domain, website, or online store. Get started with your free trial today, and when ready, take 10% off your first purchase with offer code 'EXPERTS'.

r270baAuthor Commented:
Oh and accessing on our other machines using the ip address does not work either:
SagiEDocConnect With a Mentor Commented:
Check the following:
1. Have created a DNS entry that resolves sandbox1?
2. Have you created a hostheader for the site in iis?
3. Make sure the windows firewall is off.
r270baAuthor Commented:
1. I cannot access via the IP address either (but I did check and there is a DNS entry)
2. Take a look at the image for the screen shot of the host header
3. I turned the firewall in Windows 7 COMPLETELY off and still not dice.
Brad HoweDevOps ManagerCommented:
Try the following from your desktop.
1. Open CMD | type "telnet serverIP 5555"
     * If the screen goes black, firewall is open, If it fails you have network firewall issues.
2. Remove the IP binding and mark it as Unassigned.
You should not disable your firewall for this and DNS is not an issue either. http://severip:5555 SHOULD respond. DNS and host headers are usually changes after the basics are setup.
Let us know,
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.

All Courses

From novice to tech pro — start learning today.