D
Darren Oakey
G'day -
I'm going insane trying to solve this proble, and would desperately love
some assistance:
My problem:
I am making a web site usable by both internal users and the general public.
Internal users are on a domain, but not necessarily under any known IP
structure. Throughout the web site I want extra buttons/menus enabled if
and only if the user is internal. I want the authentication of internal
users to be done with windows authentication - no logins anywhere...
So, basically, I want Windows Authentication working with the "allow
anonymous users" ticked ON - ie - is there any way of forcing IIS to do a
challenge response and then drop back to anonymous if the windows
authentication fails - at the moment it seems to just default to anonymous,
regardless of whether a user is in the domain?
I'm going insane trying to solve this proble, and would desperately love
some assistance:
My problem:
I am making a web site usable by both internal users and the general public.
Internal users are on a domain, but not necessarily under any known IP
structure. Throughout the web site I want extra buttons/menus enabled if
and only if the user is internal. I want the authentication of internal
users to be done with windows authentication - no logins anywhere...
So, basically, I want Windows Authentication working with the "allow
anonymous users" ticked ON - ie - is there any way of forcing IIS to do a
challenge response and then drop back to anonymous if the windows
authentication fails - at the moment it seems to just default to anonymous,
regardless of whether a user is in the domain?