"Ken Schaefer" wrote:

> There should be no problems (that I'm aware of) in creating a new site in
> IIS, and then extending this using the Sharepoint Administration website.
> Within the Sharepoint Admin website you then need to configure permissions
> to access the site, and you probably want to check the NTFS permissions of
> the content as well.
>
> Furthermore, I don't really know about the "subdomain" restriction you speak
> of - a website in IIS can answer to any arbitrary host name - it doesn't
> even need to have any relationship to the Windows domain that the box is in
> whatsoever.
>
> Cheers
> Ken
>
>
> "Cranky Pants" <CrankyPants@discussions.microsoft.com> wrote in message
> news:50745462-C00A-455F-96F9-FFA54243FA88@microsoft.com...
> > Since we moved to a new Dell server with SBS 2003, I have had no end of
> > problems setting things up the way we want them. I am trying to set up a
> > Sharepoint Site that we can access via the Internet - sounds pretty simple
> > (it is in Server 2003)
> >
> > I can get as far as setting up the DNS, setting up the sites in IIS, and
> > when I go to the FrontPage server Extensions 2002 Server Administration
> > page, I can click on the Default Web Site, and then it takes me to the
> > administration page, but when I click on the other one site I set up, I
> > get
> > the Administrator login.... when I enter the DOMAIN/Administrator followed
> > by
> > the password (which I know is correct), it allows three tries and then I
> > get
> > an IIS error.
> >
> > I know it is security in SBS because I found out (by mistake), that my
> > domain is not accessible at all but if I delete the configuration I did,
> > the
> > domain becomes assessible to the internet.
> >
> > I don't know what it's doing, but in Server 2000, I had no problem setting
> > this up. I've researched that subdomains are not allowed in SBS2003,
> > which I
> > can live with, but having no outside access for clients to a Sharepoint
> > Site
> > seems a little restrictive. I've been told that my permissions are messed
> > up, but I configured SBS 2003 as an OEM install on a new Dell server - I
> > didn't really do anything other than use the configuration wizards.
> >
> > Any words of wisdom would be awesome... right now I've got a pricey
> > Exchange
> > Server.....
> >
> > --
> > Cranky Pants (not really - but my kids call me this!)
>
>