• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2716
  • Last Modified:

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?
0
r270ba
Asked:
r270ba
2 Solutions
 
Jini Jose.Net Team LeadCommented:
you need access the site using the port. like http://machiname:5555 and you should enable anonnymus access on IIs
0
 
r270baAuthor Commented:
I am already trying to access it on the actual port

On the local host the following works:
   http://sandbox1:5555/
   http://localhost:5555/
   http://127.0.0.1:5555/

On our other machines however the following does not work:
   http://sandbox1:5555/

I did verify that Anonymous Authentication is enabled.
0
 
r270baAuthor Commented:
Oh and accessing on our other machines using the ip address does not work either:

   http://192.168.100.32:5555/
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
SagiEDocCommented:
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.
0
 
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.
8-17-2010-1-53-30-PM.png
0
 
Brad HoweCommented:
Hi,
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,
Hades666
 
0
 
Brad HoweCommented:
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.
Cheers,
Hades666
0

Featured Post

Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now