I need to find out how to set the DefaultLogonDomain for Frontpage so
that it will authenticate to a local Domain, and not the local ACL.
Adsutils (part of IIS AdminScripts) allows me to set the
DefaultLogonDomain for FTP, but I have not yet been able to find any
documentation for Frontpage. The only way Frontpage users can login to
their domains/websites is to manually specify "Domain\Username" which
is somewhat of a problem since most users only specify their username
because that is what they are used to. Supposedly you can turn on
Basic Authentication and specify the domain, but that is a security
risk we're not willing to take. Thanks for the answer! :)

Can you see if the follwing works, and let me know the outcome?

The following taken from Microsoft 'How to Authenticate a User Against
All Trusting Domains' (Q168908)

Start the IIS Microsoft Management Console (MMC). 


Right-click the desired Web site, and then click Properties . 


On the Directory Security tab, in the Anonymous Access and
Authentication Control section, cclick Edit .


Click Edit for Default domain for basic authentication. 


In the Domain Nam e text box, type a single backslash \ . 


Click OK three times to return to the Internet Service Manager MMC.

Thanks for replying but that is not what we wish to do because Basic
Authentication sends passwords in clear text and compromises security.
Plus, I believe that only affects filesystem level protecting, not
Frontpage authentication. I've seen that Knowledge Base article
before, and unfortunately, that is as close as I've gotten to
resolving the authentication setup. Thanks for trying though, I do
appreciate it!

I dont know how to set the default logon on domain but I know you can do this.

username: domain\username
password: password

That's what we're trying to avoid, having to enter the domain
(Domain\username). On the older machines we used to have everyone on
they all authenticated to the local machine, so they did not have to
specify a domain, but now that everything uses Active Directory you
have to specify the domain so it knows to look elsewhere. We are
trying to find a way to set it somewhere that it'll know to look at
Active Directory instead. As you can imagine, having hundreds of
people not knowing that they must specify the domain can cause a lot
of frustration for both parties, so we're trying to avoid that.
Thanks!

Your only answer will be to:

A.  Use SSL with basic so that passwords are secure (Keeping in mind
that Basic Authentication is just as secure as FTP, POP3, and a
hundred other protocols that are in use all over the internet)

B.  Make the web server a domain controller (a bit drastic, but works)