Hello,I am having an odd Problem...I have a Site (foo.mycompany.com), which works fine. But when a User tries to access "foo.mycompany.com/team/whatever" it fails with a HTTP 404...The IIS Log shows a "401.2 2148074254"Some futher digging revealed a strange behavior in IE...When trying to access "foo.mycompany.com" it correctly identifies the site as an Intranet site. But when browsing tofoo.mycompany.com/team/whatever it suddenly switches to "Internet", and I am getting the 404 error.Also the Site itself is working, since when i am accessing it from Webfrontend-1 it works, and Webfrontend-2 causes the error...Any help would be apprichiatedMCSD, MCIT Pro : http://www.novacapta.de

Hi, have it ever worked? Make sure the Alternate Access Mappings are the same for both WFE servers. You could also try to clean the IE cache and temp. files.. Daniel Bugday Web: http://www.sharepointforum.com/ Blog: http://www.sharepointforum.com/en-US/Blog/

Another update:I dis- and rejoined WF2 to the farm. The error still exists on WFE2.The current site works on ONE (WFE1) but Fails on the 2nd one.IE Settings have been flushed several times already. And switching the entry in the hosts file to point to WFE1 causes the URL to work, and WFE2 causes it to fail.I have cleared all IIS settin, and reregistered ASP.Netprior to rejoining WFE2 to the farm.The "Alternate access mappings" are a Global configuration, so they are identical between both WFE, since they belong to the same farm. Switching the hosts target-IP for the webserver (from Loadbalancer to WFE2 -> Fail / WFE1 -> Works) from the same client. MCSD, MCIT Pro : http://www.novacapta.de

Did you maybe configure the WFE1 server as a dedicated WFE for crawling instead of using "all" servers?Check Central Admin > Operations > Services on ServerDaniel Bugday Web: http://www.sharepointforum.com/ Blog: http://www.sharepointforum.com/en-US/Blog/

Hi Hatzi, The WFE1 works while WFE2 fails, so there should be some improper configuration on WFE2. The error code 401.2 means Access is denied due to server configuration. There are some common reasons for your information: No authentication protocol (including anonymous) is selected in IIS. At least one authentication type must be selected. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 253667 Error message: HTTP 401.2 - Unauthorized: Logon failed due to server configuration with no authentication Only Integrated authentication is enabled, and an older, non-Internet Explorer client browser tries to access the site. This happens because the client browser cannot perform Integrated authentication. To resolve this problem, use one of the following methods: Configure IIS to accept Basic authentication. This should only occur over SSL for security purposes. Use a client browser that can perform Integrated authentication. Internet Explorer and new versions of Netscape Navigator and Mozilla Firefox can perform Integrated authentication. Integrated authentication is through a proxy. This happens because the proxy doesn't maintain the NTLM-authenticated connection and thus sends an anonymous request from the client to the server. Options to resolve this problem are as follows: Configure IIS to accept Basic authentication. This should only occur over SSL for security purposes. Don't use a proxy. For more information, please refer to: Troubleshooting HTTP 401 errors in IIS (http://support.microsoft.com/kb/907273) Hope the information can be helpful. -lambertPosting is provided "AS IS" with no warranties, and confers no rights.

Did you solve this issue??? What was the reason?