ADAM and Windows Address Book
- From: "Rich Raffenetti" <raffenetti@xxxxxxxxxxx>
- Date: Fri, 8 Sep 2006 07:39:33 -0500
I have implemented a domain-based ADAM and have the following problem
accessing it from Windows Address Book in only certain circumstances. I am
doing all of these tests with SSL (port 636). The SSL cert is from a
commercial CA (Entrust) and the root certificate is found in all Windows
systems - as long as they update Root Certificates.
WAB accesses ADAM from a client XP Pro workstation in the domain just fine.
However, WAB does NOT access the same ADAM from a client XP Pro workstation
that is not in the domain.
LDP connects and binds to the same ADAM fine from the same workstations,
whether or not the XP Pro client workstation is in the domain. The LDP
experiments were also with SSL to port 636.
I found a thread on this issue from May 2006. There was no solution nor was
there any confirmation of this problem. I find the same behavior as was
reported then.
I get the same result when I use port 389 (no SSL).
This seems to be a WAB issue. Any ideas?
.
- Follow-Ups:
- Re: ADAM and Windows Address Book
- From: Dmitri Gavrilov [MSFT]
- Re: ADAM and Windows Address Book
- From: Rich Raffenetti
- Re: ADAM and Windows Address Book
- Prev by Date: Re: Same logonserver even though a few DC's
- Next by Date: Re: Permissions assigned to an AD object
- Previous by thread: Re: Add 2003 server R2 X64 to Mixed 2000 domain
- Next by thread: Re: ADAM and Windows Address Book
- Index(es):
Relevant Pages
|