The default 2k3 companyweb website functions correctly. We want to create a 
virtual directory under http://companyweb/our_domain_name. The directory is 
located under  C:\Inetpub\Intranet\our_domain_name. The directory is set for 
internet sharing under Companyweb.On IIS it is listed under Companyweb with 
Application Name  4\our_domain_name and starting point 
<companyweb>\our_domain_name.

Directory browsing is allowed and under documents the default content page 
is added and placed first. It is plain html and the site has no ASP or other 
scripts. All very basic. Still it throws 404 not found errors. I tried 
adding a managed path under SharePoint administration but no change.

Help appreciated for setting up an Intranet site in SBS2003 and/or setting 
up a site under companyweb.

TIA,

Fred 

Fred B. wrote:

>
>The default 2k3 companyweb website functions correctly. We want to create 
>a virtual directory under http://companyweb/our_domain_name. The directory 
>is located under  C:\Inetpub\Intranet\our_domain_name. The directory is 
>set for internet sharing under Companyweb.On IIS it is listed under 
>Companyweb with Application Name  4\our_domain_name and starting point 
><companyweb>\our_domain_name.
>
>Directory browsing is allowed and under documents the default content page 
>is added and placed first. It is plain html and the site has no ASP or 
>other scripts. All very basic. Still it throws 404 not found errors. I 
>tried adding a managed path under SharePoint administration but no change.
>
>Help appreciated for setting up an Intranet site in SBS2003 and/or setting 
>up a site under companyweb.

I wouldn't try creating additional web "stuff" inside Companyweb - it's 
managed by Sharepoint, and that's going to make things complicated.

If you desperately need basic web site stuff, I'd build it under the 
Default Web Site (so it's accessible on port 80) if possible. If you're 
really worried about breaking any of SBS functionality, the other option 
would be a whole new Web Site at the top level, and use Host Headers (like 
Companyweb does) or a different port.

Of course, the obvious question is why not just use Companyweb for your 
intranet - that _is_ why it's there...

-- 
Steve Foster
------------
Please reply only to the newsgroups.
For SSL Certificates, Domains, etc, visit.: https://netshop.virtual-isp.net

Hi Steve,

We are using conpanyweb. It do however not understand why we are not able to 
add some  static non-SharePoint html pages under 
http://companyweb/our_domain_name. They are there, specified the correct 
physical path and virtual path but we still get a 404 not found error.

For example http://companyweb/subsite/index.html page is there, virtual 
directory set, result however 404.

TIA,

Fred

-- 
..
"Steve Foster" <steve.foster@picamar.co.uk> wrote in message 
news:xn0gq89a9w4g5me01t@msnews.microsoft.com...
> Fred B. wrote:
>
>>
>>The default 2k3 companyweb website functions correctly. We want to create 
>>a virtual directory under http://companyweb/our_domain_name. The directory 
>>is located under  C:\Inetpub\Intranet\our_domain_name. The directory is 
>>set for internet sharing under Companyweb.On IIS it is listed under 
>>Companyweb with Application Name  4\our_domain_name and starting point 
>><companyweb>\our_domain_name.
>>
>>Directory browsing is allowed and under documents the default content page 
>>is added and placed first. It is plain html and the site has no ASP or 
>>other scripts. All very basic. Still it throws 404 not found errors. I 
>>tried adding a managed path under SharePoint administration but no change.
>>
>>Help appreciated for setting up an Intranet site in SBS2003 and/or setting 
>>up a site under companyweb.
>
> I wouldn't try creating additional web "stuff" inside Companyweb - it's 
> managed by Sharepoint, and that's going to make things complicated.
>
> If you desperately need basic web site stuff, I'd build it under the 
> Default Web Site (so it's accessible on port 80) if possible. If you're 
> really worried about breaking any of SBS functionality, the other option 
> would be a whole new Web Site at the top level, and use Host Headers (like 
> Companyweb does) or a different port.
>
> Of course, the obvious question is why not just use Companyweb for your 
> intranet - that _is_ why it's there...
>
> -- 
> Steve Foster
> ------------
> Please reply only to the newsgroups.
> For SSL Certificates, Domains, etc, visit.: 
> https://netshop.virtual-isp.net 

Fred B. wrote:

>Hi Steve,
>
>We are using conpanyweb. It do however not understand why we are not able 
>to add some  static non-SharePoint html pages under 
>http://companyweb/our_domain_name. They are there, specified the correct 
>physical path and virtual path but we still get a 404 not found error.
>
>For example http://companyweb/subsite/index.html page is there, virtual 
>directory set, result however 404.
>

Because that's not how Sharepoint works.

Basically, IIS hands over processing of requests within a Sharepoint 
website to Sharepoint. Normal IIS processing doesn't apply.

You should be able to use the FrontPage licence that comes with SBS2003 to 
modify the design of Companyweb, which would let you incorporate your 
static pages into Sharepoint "the Sharepoint way" (they just become Custom 
Pages, IIRC).

-- 
Steve Foster
------------
Please reply only to the newsgroups.
For SSL Certificates, Domains, etc, visit.: https://netshop.virtual-isp.net