Tell me more ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.
up vote 5 down vote favorite
1

I want to create a web application tied to a domain name within my server. Following are the steps I followed:

  • Modified the server host file for www.xyz.com to resolve to localhost
  • I am able to ping www.xyz.com which does resolve to localhost
  • Create a web applicaiton with host header www.xyz.com
  • Created a site collection

But I can't login to that site for reason. When I visit http://www.xyz.com through the browser, I get prompted for credentials but it doesnt accept my credentials even though I assigned myself as the site collection admin. Did I miss step above? With 2007, I followed the same steps and it works.

Any help will be appreciated.

Thanks.

share|improve this question

1 Answer

up vote 11 down vote accepted

Are you now running on Windows Server 2008 or 2008 R2? In Windows Server 2008 they implemented a security check called the "Loopback Check" to restrict doing just what you are trying to do :)

Check out the following KB article for a registry work-around. This will only happen when you try to browse to the host header from the server that hosts the site. If you browse to the site from another computer, this should not be a problem.

If you are on a non-production server, the easiest option is the #2, add "DisableLoopbackCheck" to the appropriate registry key.

http://support.microsoft.com/kb/896861

share|improve this answer
1  
It would be also usefull to just try accessing the site from another PC. – Clayton Firth May 24 '11 at 22:26
It is also possible it is an Kerberos issue, but only if Kerberos is the selected auth schema. – Marco Scheel May 25 '11 at 6:05
The loopback check was introduced in windows server 2003 (a service pack), although it does ship with 2008. – Benjamin J Athawes May 25 '11 at 7:17
Yes it is windows 2008 R2. – Emon May 25 '11 at 16:21
3  
The linked KB article gives you both answers. For non-production, Method #2 is easiest "DisableLoopbackCheck". For production servers, use Method #1 and the BackConnectionHostNames option with the specific host headers to allow. Method #1 is more secure. – Chris Beckett May 25 '11 at 18:20
show 2 more comments

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.