Any other recommendation?Because i dont want to setup any trust relationship
between two domain.Actually i wonder why do i encounter this problem with
isa and not with proxy 2.0.
Thanks...
From: peterjpape@xxxxxx Reply-To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx> To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx> Subject: [isalist] RE: ISA authentication problem Date: Tue, 30 Oct 2001 18:29:32 -0500
http://www.ISAserver.org
I would recommend that you create a one-way trust between the logon - domain and the ISA machine. The goal being that the Users in Domain B would then be able to authenticate against the ISA server. Then you don't have to maintain two or more security files.
"osman" <osmanfiliz@xxxxxxxxxxx> wrote:
>http://www.ISAserver.org
>
>
>Hi,
>We have got one NT 4.0 domain called domain A,on the PDC of this domain MS
>Proxy 2.0 is installed.Clients are logon to another domain called domain
>B.
>If the password of the clients are the same for the domain A and domain
>B,then MSProxy 2.0 does not ask a question for password to clients.We add
>a W2K stand alone computer to domain A,and on this machine we installed
>isa server.Clients still logon to domain B.In spite of some clients have
>the same password for two domains isa server still asks for password and
>domain name.How can i prevent from this like inthe proxy 2.0?
>
>------------------------------------------------------
>You are currently subscribed to this ISAserver.org Discussion List as: peterjpape@xxxxxx
>To unsubscribe send a blank email to $subst('Email.Unsub')
>
------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as: osmanfiliz@xxxxxxxxxxx
To unsubscribe send a blank email to $subst('Email.Unsub')
_________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
