We've been using IIS with all versions of R5 on NT4 & 2K. Its worked well &
coped easily with a switch to Active Directory.
Somewhere in the IIS configuration is a default domain for authentication
setting. If you set that appropriately and enter domainless NT login names in
the NAB Fullname field, everyone in that domain can login using just their
login without the domain\ component. This is good because many people use /
instead of \ and so fail to login but bad because (depending on the format of
your login names) you can get clashes with other Fullname values.
In our case more recent NT logins are often peoples' surname. We add the
domain\login and the bare login value to the Fullname field. This is confusing
but the real problem is that someone can be happily authenticating using their
NT login until we add a new user whose domino name causes a clash with the
existing user's NT login -then suddenly they can't login until we tell them to
use the domain prefix. ****!
We've been using IIS with all versions of R5 on NT4 & 2K. Its worked well & coped easily with a switch to Active Directory.
Somewhere in the IIS configuration is a default domain for authentication setting. If you set that appropriately and enter domainless NT login names in the NAB Fullname field, everyone in that domain can login using just their login without the domain\ component. This is good because many people use / instead of \ and so fail to login but bad because (depending on the format of your login names) you can get clashes with other Fullname values.
In our case more recent NT logins are often peoples' surname. We add the domain\login and the bare login value to the Fullname field. This is confusing but the real problem is that someone can be happily authenticating using their NT login until we add a new user whose domino name causes a clash with the existing user's NT login -then suddenly they can't login until we tell them to use the domain prefix. ****!