Hi - I created a new (a 2nd one) site collection and am unable to access it directly from the server, I am able to pull on the original site collection. Current setup is pretty simple: Running Sharepoint 2007 on single server, small farm installation. Have a site collection users access at http://insightshare. Want to develop a brand new intranet to eventually replace the old one. Here's what I've done: Created brand new web application using host header 'insightnet' using port 80 Created site collection Added A record in DNS for insightnet. Happy to report it seems to be working on client computers - however on the actual server when I try to pull up the new site I get a login box that refuses admin credentials. Any ideas? TIA

Hello, It sounds like the old Loopbackcheck issue. Look at these: http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=107 http://support.microsoft.com/kb/896861/en-us Chris Caravajal MCTS SharePoint Help

I tried the registry fix but it didn't work. I wonder if that's the issue as it never did create an event in the security log (as illustrated in the Microsoft article). Any other ideas?

Did you tyr the disableloopbackfix setting, or specific URLs - if specific URLs tyr the generic disable.Chris McNulty MCSE/MCTS/MSA/MVTS http://www.kma-llc.net | blog http://blogs.kma-llc.net/microknowledge | twitter @cmcnulty2000

I tried the first method, specifying the hostname - I put 'insightnet' - should I have put the FQDN? I just tried the disableloopback and that did work - however it wasn't the recommended fix. I assume no loopback testing would ever work?

At least we know now that this is the cause. Try using the FQDN. To be honest, and even though it is not the "recommended" fix, I see the disableloopback solution performed more often than not.Chris Caravajal MCTS SharePoint Help