Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Monday, March 7, 2011 3:37 PM
I have SharePoint 2010 installed on Windows Server 2008 R2. In doing some work with SharePoint designer, I discovered I cannot access any of the site collections using "localhost" except for SharePoint Central Administration.
If I open up IIS and try to browse any of the other SharePoint sites, I get a 404 error. However, if instead of "localhost" I use "ktlp-sp" (the server's domain), I can access these sites just fine.
Been going around and around in circles trying to figure this out. I need to be able to access these sites using "localhost" in order to use some of the functionality in SharePoint Designer.
There must be something in Central Administration I need to do? Or something misconfigured with the ports? The URL that works for Central Administration is "http://localhost:12345" but if I use any other port number for the other site collections I get a 404 error.
Thanks.
Here's the sites listed in IIS:
DefaultWebSite (port 81)
SharePoint - 34978 (port 34978)
SharePoint - 6789 (port 6789)
SharePoint - 80 (port 80)
SharePoint Central Administration v4 (port 12345)
SharePointWebServices (this has a line for http (port 32843), https (port 32844), net.tcp, and net.pipe
Ed
All replies (6)
Wednesday, March 9, 2011 9:57 PM âś…Answered
If you aren't using host headers and you are working directly on the server then the problem is probably the DisableLoopBackCheck problem. In order to prevent scripting attacks Microsoft made it impossible to call a server from itself. This article explains the issue and describes a couple work arounds.
Paul Stork SharePoint Server MVP
Monday, March 7, 2011 5:02 PM
When you created the SharePoint Web Application did you specify a host header? If you did, then you must use the host header name when accessing the site. The way to check this is to look at the Bindings for the site in IIS manager. If there is a host name listed in the Bindings then you used a host header and won't be able to access the site using localhost without adding that as a hostname.Paul Stork SharePoint Server MVP
Monday, March 7, 2011 6:55 PM
Thanks.
I didn't create these applications myself, but when I check the bindings for any of them there is nothing listed under "host name"
Any other ideas?
What I don't get is why localhost:12345 works for the central admin. but if I use any other port number after localhost I get the 404. Is there some setting in central admin. that I need to change?
Tuesday, March 22, 2011 7:27 PM
Thanks for the advice.
When browsing to "localhost" I'm now getting something returned by the browser that I haven't seen before, perhaps you can tell me what the server is trying to communicate:
HTTP/1.1 200 OK Server: Microsoft-IIS/7.5 Date: Tue, 22 Mar 2011 19:25:56 GMT Connection: close
What does this indicate?
Thanks.
Monday, June 11, 2012 10:26 PM
Please add one feature in windows server where SharePoint installed called Http Logging feature. it should work. Update if resolved.
Monday, June 11, 2012 11:11 PM
Http Logging is not enable. Enable that feature from server manager. It resolved the issue.