|
Rievax -> RE: ISA Authintication (18.Jun.2008 9:59:49 AM)
|
darkgabeman, To me, this is going against AD high availability. Why would you like to do such a thing? AD requests to authenticate a user are not really heavy on your controllers. And what will happend if you loose this server? Nobody will be able to browse, and you will have to reboot your boxes to "fix" the hypotetical registry key hack... You could try to create a LHMOST file in "c:\WINDOWS\system32\drivers\etc\lmhosts" (sample in the c:\WINDOWS\system32\drivers\etc\lmhosts.sam) with entries for #PRE and #DOM. This could do the trick, but I am not sure is will work for ISA AD authentication... But to my opinion, the best way would be to create another subnet, put you ISA and AD server in it and create a new site and subnet in your "AD Sites and Services" MMC snap-in. This way, if the AD server dies, the ISA will talk to other AD servers in your domain... Xavier.
|
|
|
|