Hi everyone,After some struggles to get Sharepoint 3.0 up and running, I've finally got it close. I'm running a Windows 2003 r2 Server using IIS 6.0. If I type in http://localhost/default.aspx into the address bar of IE from the server, I see the Sharepoint site I set up. However, when I type in http://computername/default.aspx I get prompted for a username and password for which the default username is COMPUTERNAME\admin. I put in the admin password and it cycles through this prompt a few times and then brings up "You are not authorized to view this page" message in IE.I feel that I'm really close because I can see it using localhost. Can someone give some direction on what I need to do to get this thing running via computer name?Thanks for your time.

I encountered the same problem. For me the solution was just dropping off the computer name and using only the username. But I am currently encountering another problem of not all of the links I should have showing up. I'm not sure if this stems from the way I am logging in or some other setting. Try it though and tell me if that works.

Go to administrative tools and lunch the Sharepoint central administration site. In the application management tab you go to the site collection list under the Sharepoint Site management and you check the Site collection list created there.

Widgeon9, Was wondering about that, but I have to thank you. Looking at your problem actually gave me the clue for the solution I needed. For my missing links I have to connect using localhost instead of computer name. Must have something to do with the login credentials from the two different methods. I'll be crossing my fingers and hoping you figure yours out as well.

Mr. Cobb, My install is actually done in a workgroup w/o a domain. If you could offer further guidance as to a solution to my problem so I can use the computer name instead of localhost I would appreciate it. But I do not wish to hijack this thread. Here is my original post of the said problem: http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/43048baa-a2e7-4abf-a30e-7247bd22e0c5 Thank you for the heads-up, so far though I've just configured the search service and am reading up on what I need to do next. My goal is listed in this thread: http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/d9b17a33-3bd3-4c2b-8401-006ff6772b7d It's on page 4 so what's the policy of bumping up a thread that receives no answers?

This sounds like the loopback security check. There is a registry change you can make to specify the valid host names. Take a look at the MS KB article:You receive error 401.1 when you browse a Web site that uses Integrated Authentication and is hosted on IIS 5.1 or IIS 6If this is going to be a production server, do Method 1. Brian

Definitely not the fix here either. You _should_ have Windows Integrated Authentication.SharePoint Architect || My Blog

Two completely different settings. The one on the server allows people to connect and leverage Windows Auth. The one in your browser determines whether YOU can use it from within your browser sessions. They should both be enabled. Why would it be unchecked in IE?What you did was disable that so that it doesn't try to log you in with your Windows credentials. You then get prompted to login, which is what happens when you don't have IWA. You said you are in a workgroup and not a domain, so the credentials you log in with to your machine must not match the credentials you use to log in to SharePoint, so when it tries to auto-login using IWA, it fails.SharePoint Architect || My Blog

Strange behavior that I've never encountered in a workgroup or a domain setup. At home, I have a new SP2010 installation on W2K8R2, and it's a local workgroup. I have IWA active everywhere and am able to login from my other client machine at home with no issues (requires login, of course). On the server itself, it auto-logins each time. I'm not sure what is going on with your system.SharePoint Architect || My Blog

I appreciate the help Clayton. Thanks for taking the time to help. I'll keep digging and post back if I figure out how to get the best of both.

Ok, I realise this is thread necromancy here, but I've just run into the exact same problem, and managed to solve it. Posting here to preserve it for posterity... Solution: At least in my case, this behaviour was being caused by having a blank password! I reset the Administrator password to something non-blank, and was immediately able to access the Sharepoint page on both http://computername and http://localhost I didn't have to make any other changes to IIS or Sharepoint. I hope this helps someone, as I've just spent 2 hours tearing my hair out!