Windows Server R2 - Unable to log on to WSS 3 site on the Local Server
We have recently moved a WSS 2 Content database to a new Windows Server 2008 R2 Server. We have attached and upgraded this database to WSS 3. I am unable to browse the site locally on the server. i keep getting prompted with a logon box,
I have no problems accessing Central Admin and I have full rights. DNS was set up before WSS 3 was installed and the new site name registered there. I have set up alternate internal mappings in WSS, added the domain to trusted sites in IE9
also disabled the loop back for IIS. I need to check this on the server before we update our existing public DNS entry to point to the upgraded site. We dont have an internal LAN. Has anybody any idea on why this happens?
June 27th, 2011 10:52pm
Hi raymond75,
If you can access Central Administration but can't access the sites on local server, and it seems you have set everything
you can thinkable, then normally it could be due to the loopback issue. Before we also occurred this for some times, and most of the times loopback issue is the root cause. Although you mentioned that you have disabled the loopback
for IIS, I still suggest that you go through the steps below and see whether anything was missing:
Note: Please back up the registry before any modification to it. About How to back up and restore the registry in Windows,
please review 322756 (http://support.microsoft.com/kb/322756/) for details.
A quick check and fix for this issue could be:
1.
Click
Start, click
Run, type
regedit, and then click
OK.
2.
In Registry Editor, locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
3.
Right-click
Lsa, point to
New, and then click
DWORD Value.
4.
Type
DisableLoopbackCheck, and then press ENTER.
5.
Right-click
DisableLoopbackCheck, and then click
Modify.
6.
In the
Value data box, type
1, and then click
OK.
7.
Quit Registry Editor, and then restart your computer.
If above doesn't help, then please go through this for a detailed check:
http://support.microsoft.com/kb/896861
In addition, one more thing you can check is the server's hosts file (under C:\WINDOWS\system32\drivers\etc\). Please
make sure there is no entry which attach your site name (web application's DNS name) with incorrect IP address.
Hope this help:-)
Best Regards,
Roy
Free Windows Admin Tool Kit Click here and download it now
June 28th, 2011 9:52am
Hi Roy,
Thanks for your reply!
It was me on the loopback entry, I did it such a rush I did not update the value to 1!!
Works like a charm now.
Thank you!
Ray
June 28th, 2011 12:18pm