IIS Sharepoint Configuraton

I am trying to configure IIS so that traffic to http://tpn.project-network.com goes directly to my home site.  All records have been changed to point to the new Sharepoint server so that is no problem.

The image :- http://img70.imageshack.us/img70/5443/iisscreenshotxj1.png is a picture of the message im getting.

I have set up IIS before for our Web client Helpdesk software on its own individual server, but where can I check on default directory (Where are the default webpages for sharepoint located so I can make sure that IIS is looking in the correct location.  Also if you look at the image you will see about 4 profiles (Sites) you have Default Web Site, Office Server Web Services, Sharepoint Service and my site which is Sharepoint - 2007.  When traffic comes in how does it know to open my sharepoint - 2007 site default page and not the default pages of the other sites  I just mentioned.

Any help to set IIS up would be great it is the only thing I am struggling with.  The error message I am getting is when I select browse when I right cick on the Sharepoint - 2007.

Who is Participating?
Ted BouskillConnect With a Mentor Senior Software DeveloperCommented:
Have you fully configured Sharepoint 2007?  I suspect you haven't.  Sharepoint web applications are very different than standard .NET web applications.  Manually editing IIS on a Sharepoint server is VERY risky unless you have a very high level knowledge of IIS and Sharepoint.

I don't know if you've been to this site: http://blogs.msdn.com/Sharepoint  It's full of information from the Sharepoint product team.

Many users get confused with the new layout of Sharepoint Portal Server 2007.  I'll give you some high level information that can hopefully help you.

Number one, use fully qualified domain names when configuring the farm.  DON'T use server names.  It's a nightmare to manage later.  For example, sharepoint.mydomain.com

The root of SPS 2007 is the farm administration which is managed through one mandatory Central Administration web application.  SPS 2007 web applications are really two logical components.  A web application and within the web application there must be one default site collection.  During the install you should have executed a step to create the web application then create the site collection (which generates the site).  I use port 2007 for the Central Administration site so the URL would be http://sharepoint.mydomain.com:2007

When you install Sharpoint you must designate a Farm Administrator account that should be a local administrator on all servers.

Within each farm there must be one default 'Shared Service Provider' which is also managed using one mandatory Service Provider Administration web application.  During the install you will also create a web application and site collection for this site.  I usually use port 20070 for this site which creates http://sharepoint.mydomain.com:20070

The default Shared Service provide can host many web applications (your portals).  You need to create a default 'My Site' web application and site collection.  IE: http://people.mydomain.com

After that you can create additional web applications and each must have one default site collection.

I won't get into setting up search but that is managed in combination at the farm administration level to designate the servers that host the indexing (the crawling component) and query server (the service that finds results for users).  NOTE: There is a second search setup specifically to search Sharepoint help.  I have no idea why Microsoft has it as well.

Sharepoint stores indexed content for the Sharepoint web sites in the database.  Indexed content for non Sharepoint websites is stored in the search index folders as files.

Now there is some important points about permissions that most people don't realize.  A windows account that is the local administrator on the server hosting SPS 2007 does NOT automatically have access to Sharepoint!

The designated Farm Administrator account does NOT automatically inherit permissions to manage the Shared Service Provider (yet it can give itself permission)  In fact, the Farm Administrator does NOT automatically inherit administration priviledges for any web applications other than Central Administration but it can give itself permissions.

The site collection administrator for the Shared Service Provider has permissions to fully manage shared services.  In fact, by default as you can guess the site collection administrator is the most powerful role in each web application.

I suspect that the problems you are having are because you didn't finish all the configuration steps (there are many more than SPS 2003) or you are not using the proper account to access the different sites because you assumed (like many do) that the local or farm administrator automatically inherit access.\
WecksAuthor Commented:
Ok it was down to the fact that I had not extended my site.  I ran through it with MS and they resoved it for me.  
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.