"davelj" <davelj@discussions.microsoft.com> wrote in message
news:7D7DFC4B-27BA-4233-A4C0-02D53DEFDF67@microsoft.com...
>I have a W2000 server running IIS 5 for my local intranet and a help desk
> website. We use basic authentication and I have set the default domain to
> my
> local domain name. When a user attempts to login the login is rejected
> unless
> the user enters his login as domain\username. When the user only enters
> username, I get an event log entry showing that the server is attempting
> to
> authenticate the user against the local server instead of the domain.
>
> I have tried resetting the default domain through the Internet Services
> Manager both at the server and at the website level with no change. I
> installed Metaedit and searched for defaultlogondomain and found that all
> of
> the entries were pointing at the domain name and not the server name so I
> can't figure out why this is happening.
>
> I'm running out or ideas on this one. When should I go from here?

"Roger Abell [MVP]" wrote:

> Is Windows integrated authentication also enabled ?
> For the default domain to be used you must force use of
> the clear text (basic) login.
>
> "davelj" <davelj@discussions.microsoft.com> wrote in message
> news:7D7DFC4B-27BA-4233-A4C0-02D53DEFDF67@microsoft.com...
> >I have a W2000 server running IIS 5 for my local intranet and a help desk
> > website. We use basic authentication and I have set the default domain to
> > my
> > local domain name. When a user attempts to login the login is rejected
> > unless
> > the user enters his login as domain\username. When the user only enters
> > username, I get an event log entry showing that the server is attempting
> > to
> > authenticate the user against the local server instead of the domain.
> >
> > I have tried resetting the default domain through the Internet Services
> > Manager both at the server and at the website level with no change. I
> > installed Metaedit and searched for defaultlogondomain and found that all
> > of
> > the entries were pointing at the domain name and not the server name so I
> > can't figure out why this is happening.
> >
> > I'm running out or ideas on this one. When should I go from here?
>
>