Solved

Cannot Login to Website Remoted Into the Same Server

Posted on 2008-10-29
1
301 Views
Last Modified: 2013-12-24
I have a site hosted on a Windows Server 2003 SP1 machine in IIS 6.  I can access the site by the domain from an external machine but I cannot authenticate with the site from within the same server by the domain.  I can browse to the site RDP'd into it via it's domain name but no authentication to Active Directory is working.  When I connect the same way (to the site on the hosting server) via the IP address I CAN authenticate with AD and everything works fine.

To rehash:
I can not authenticate to a domain name within the hosted server.  I can authenticate with the IP address within the hosted server.  An external machine can authenticate with the domain name and the IP address.

I have a DTSearch index spider running on the same machine as the website that needs to authenticate via Active Directory to crawl the website by domain.  The problem is that the scheduler cannot crawl the website because it gets a 401.1 error.

I have seen this problem before and we fixed it but for the life of us we can't remember what we did.  I know we found a Microsoft KB article on it but we could not find that again either.

Thanks for your help,
Dirk
0
Comment
Question by:dirq
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 
LVL 1

Accepted Solution

by:
dirq earned 0 total points
ID: 22832671
We found the answer.  When we looked in the event log there are some weird characters in the Logon Process element for the Security event log.  The fix requires a registry edit and a restart.

You receive error 401.1 when you browse a Web site that uses Integrated Authentication and is hosted on IIS 5.1 or IIS 6

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

CAUSE
This issue occurs if you install Microsoft Windows XP Service Pack 2 (SP2) or Microsoft Windows Server 2003 Service Pack 1 (SP1). Windows XP SP2 and Windows Server 2003 SP1 include a loopback check security feature that is designed to help prevent reflection attacks on your computer. Therefore, authentication fails if the FQDN or the custom host header that you use does not match the local computer name.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

While rebooting windows server 2003 server , it's showing "active directory rebuilding indices please wait" at startup. It took a little while for this process to complete and once we logged on not all the services were started so another reboot is …
When table data gets too large to manage or queries take too long to execute the solution is often to buy bigger hardware or assign more CPUs and memory resources to the machine to solve the problem. However, the best, cheapest and most effective so…
Video by: Steve
Using examples as well as descriptions, step through each of the common simple join types, explaining differences in syntax, differences in expected outputs and showing how the queries run along with the actual outputs based upon a simple set of dem…
This is a high-level webinar that covers the history of enterprise open source database use. It addresses both the advantages companies see in using open source database technologies, as well as the fears and reservations they might have. In this…

707 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question