My web servers that are running IIS6.0 are in located in an AD site with 2
domain controllers each DC is a DNS and GC server, and the webserves have
both servers configured for DNS DC1 is primary and DC2 is secondary. My
therory is because the connection is comming through IIS and its IIS that
needs to talk on behalf of the client making the request, IIS is now acting
similar to a proxy server, and it is keeping a persistent connection open to
one of the DC is the same site as the webserver, if this DC goes offline, i
dont think IIS is able to smart enough to look for a new DC, until the IIS o
r
other webservices are restarted. I think there may be no way around this
issue.

i like to hear your thoughts on this if you agree or disagree
thanks

"JJ" wrote:
[vbcol=seagreen]
> No Skip- We haven't solved this yet. I believe that our developers will be
> moving the session info to the SQL database (from the IIS session) and may
be
> that will solve our issue.
> I'll keep you posted.
>
> "skip" wrote:
> 

[ Post a follow-up to this message ]