Re: LDAP redundancy
- From: "Peter Demeyer" <pdemeyer@xxxxxxxxxx>
- Date: Thu, 15 Jun 2006 13:34:30 +0200
I think you should be able to bind to a domain name rather than to a
specific domain controller.
If it's an .asp page or a .vbs script, then it could start with something
like this:
Set objRootDSE = GetObject("LDAP://RootDSE")
strDNSDomain = objRootDSE.Get("DefaultNamingContext")
"Charlie Ting" <cting74@xxxxxxxxxxx> wrote in message
news:ucOdnVypZZPv0xLZnZ2dnUVZ_vmdnZ2d@xxxxxxxxxxxxx
Hi All,
We have a web server sitting in the DMZ. The web service queries the LDAP
off the domain controller in the trusted LAN. We created a firewall rule
to allow web server into the domain controller through port 389. We have 2
domain controllers. We like to provide LDAP redundancy. When one domain
controller goes down, the web service will automatically query the 2nd
domain controller. What's the technology that I should be looking after?
round robin? Please help.
Domain controller: Windows 2000 Server.
.
- Follow-Ups:
- Re: LDAP redundancy
- From: Charlie Ting
- Re: LDAP redundancy
- References:
- LDAP redundancy
- From: Charlie Ting
- LDAP redundancy
- Prev by Date: Re: DHCP Security breach
- Next by Date: Re: DHCP Security breach
- Previous by thread: LDAP redundancy
- Next by thread: Re: LDAP redundancy
- Index(es):
Relevant Pages
|