Ever since i started installing SharePoint 2007 (over 2 years ago), i have been configuring Alternate Access Mappings.
This was never a problem. Up until yesterday.
Yesterday i configured SharePoint AAM for an installation i had done earlier.
For the record: Sharepoint 2006 x64 on a Windows 2008R2 x64. I must say: it was my first experience with 2008R2
Set al the settings that needed to be set.
Computername : Sharepoint1
New “Nice” name: Intranet
I created the AAM entries, and since i was configuring the machine (contained 1 empty site collection) i also started search.
I stopped the search after 38 minutes, because that was impossibly long
I then tried to reach the sharepoint site and i the only thing a got was a blank page where access denied should have been visible.
So besides not able to login, i also was not presented the right page.
This made me start my quest for information on the internet.
I assumed it was IIS7 related. 2008R2 has some new features and installation points. example : ASP.net 3.5.1 is automatically installed.
I took me a whole lot of time and testing to find out that the problem was eventually solved using the disableloopback registry setting.
Simply settings this registry setting, then rebooting and everything works as intended.
So for every out there that has problems with AAM and Windows2008 (not sure if it’s R2 only or not)
Try the registry setting first. Here you can find more information about it
It’s a simple setting, doesn’t cost a lot of time, and can be easily removed.
Regards,
Eric
I’m having this problem too. Tried both of the items mentioned in that KB article and still having the problem though. Strange thing on mine though, as an admin I can hit the “intranet” site just fine, but as any other user I get the blank page. Any user can access it fine using the servername though. Running Windows 2008 (not R2 on this server).