You can still use Integrated Windows Authentication, however you can only
use local accounts (i.e. accounts that are local to the webserver). Since
the user can't log onto their local workstation with the same account, the
auto-logon will fail, and the user will need to supply a set of credentials
the webserver accepts, namely webservername\username (and the corresponding
password).

Cheers
Ken

--
Blog: www.adopenstatic.com/cs/blogs/ken/
Web: www.adopenstatic.com


[quoted text, click to view]
: Hi everybody,
:
: I have the following scenario.
:
: - One W2K Domaincontroller hosting an AD Service (Domain "foo")
: - One W2K Webserver with IIS 5
:
: The webserver is not a member of the Domain "foo". Am I still able to use
: Integrated Authentication? If yes, how do I tell the IIS which domain to
: use. If not, are there other authentication methods that prevent the
: Username/Password popup appear in IE?
:
: Thank you very much for any help!
:
: Andreas
:
:

Hi everybody,

I have the following scenario.

- One W2K Domaincontroller hosting an AD Service (Domain "foo")
- One W2K Webserver with IIS 5

The webserver is not a member of the Domain "foo". Am I still able to use
Integrated Authentication? If yes, how do I tell the IIS which domain to
use. If not, are there other authentication methods that prevent the
Username/Password popup appear in IE?

Thank you very much for any help!

Andreas