Basic Authentication + IIS 5 + Windows 2000 + Frontpage 2002 = failure?

From: Vincent Polite (trinetgrinch@yahoo.com)
Date: 11/13/02 

From: trinetgrinch@yahoo.com (Vincent Polite)
Date: 12 Nov 2002 16:17:27 -0800

I have seen threads about this topic all over UseNet, so I wanted to
state my problem which may or may not have a unique twist.

The setup:

My web server is a Windows 2000 Server. It houses Exchange 2000 and
runs IIS5 Web Services and FTP Service. From a website perspective, I
host (for personal reasons) about 30 different websites. These
websites are differentiated using host-headers, configured through the
Internet Services Manager.

The websites are divided into 4 domains.

*.domain1.com (20)
*.domain2.com (2)
hostname1.domain3.com
hostname2.domain4.com

The last two entries are websites that I planned on hosting for some
friends. However, to avoid having all their network traffic getting
sent to my machine before the site was ready, I set up special
instances on the server.

The web server itself is behind a Netgear Home Protection System on
the tail end of an ADSL Line. I have set up port forwarding for ports
80 (HTTP), 443 (HTTPS on IIS), 25(SMTP), and the ports for my remote
control program. (I'm pretty sure FTP is set up as well)

On all of the sites I have set up the Frontpage Server Extensions
circa 2002. On the majority of the sites, I have set up Sharepoint
Team Services.

When I was using NTLM, I was able to connect to my sites and
authenticate with any password protected sites no problem. All the
sites worked perfectly, and I had nary a problem.

The problem:

I wanted to work on a friends' site using the facilities/software I
had available at the office. I was going to use Frontpage 2002 to
edit this website, but my company's proxy server will not allow NT
Challenge/Response w/untrusted domains.

Because I cannot convince the powers that be at my office to let me
use NT Challenge/Response against my web server, I felt a reasonable
alternative would be to change the authentication on the website to
"Basic Authentication."
 
Once I made this change through the Internet Services Manager, I was
unable to use Frontpage to edit the site. The problem went beyond
Frontpage, as well. In order to make sure it wasn't my company's
proxy server, I tried to edit the site running Frontpage locally on
the server itself, and I couldn't validate any of my accounts.

After perusing this newsgroup for about a week, i ran across the
following notions:

1) Make sure the accounts can log on locally to the server.
2) Make sure that when logging on, use the servername\username format
for the username password prompt.
3) Set a default domain equal to the domain of the account you are
using.
4) Set a default domain equal to '\' which signifies all trusted
domains.

Nothing works. At this point my brain is too numb to orchestrate the
test of just checking basic authentication against a protected page in
the website, but I'm pretty sure I can't get that to work as well.
Meaning, go into Explorer, remove permissions for a specific page
except for a specific user, and then try to browse to that page using
a web browser under basic authentication.

Any ideas as to how I can approach this problem at this point?
Clearly I haven't tried everything, but I feel like I've exhausted
quite a few possibilities.

Thanks,

Vincent Polite
Internet Application Specialist about to rescind his title

Relevant Pages

  • Re: Basic Authentication + IIS 5 + Windows 2000 + Frontpage 2002 = failure?
    ... By this, I mean, usually, on the basic logon screen of a server, I see ... >;) under the website in question, enabling only Basic authentication. ... > - When testing with IE or FrontPage local to the webserver for a baseline ... From a website perspective, I ...
    (microsoft.public.inetserver.iis.security)
  • RE: Basic Authentication + IIS 5 + Windows 2000 + Frontpage 2002 = failure?
    ... ;) under the website in question, enabling only Basic authentication. ... IE (and FrontPage too, if I am not mistaken) will interperate the ... lets configure the server extensions on this VDIR....select the ... From a website perspective, I ...
    (microsoft.public.inetserver.iis.security)
  • Re: frontpage intranet migration website strategy with a twist
    ... decent experience with Frontpage and publishing to third party WWW ... I have a newly integrated Small Business Server 2003 and I'm ... trying to publish a website via FrontPage. ... Opening IIS and creating a new website using server ip address, ...
    (microsoft.public.frontpage.client)
  • re: Search form website
    ... I chose "the entire website" as my option. ... the info as long as it is on the server. ... >Microsoft Indexing service wasn't installed. ... >still be configured to use the FrontPage search engine. ...
    (microsoft.public.frontpage.programming)
  • Re: Moving frontpage intranet website directory to new server
    ... decent experience with Frontpage and publishing to third party WWW ... I have a newly integrated Small Business Server 2003 and I'm ... trying to publish a website via FrontPage. ... Opening IIS and creating a new website using server ip address, ...
    (microsoft.public.inetserver.iis)