Re: ADAM and Windows Address Book

Yeah, I remember something came up with WAB.
Questions:
Which port is your WAB configured to talk to: LDAP or SSL?
Are you trying to bind with Windows credentials or ADAM user credentials?
Is "logon using secure password authentication" checkbox on or off?
When connecting from domain-joined workstation -- please try to logon as a
local admin (non-domain user), and check if it still works.

--
Dmitri Gavrilov
SDE, Active Directory team

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

"Rich Raffenetti" <raffenetti@xxxxxxxxxxx> wrote in message
news:eGVZUP00GHA.2636@xxxxxxxxxxxxxxxxxxxxxxx
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?



.

Relevant Pages

  • Re: ADAM and Windows Address Book
    ... Which port is your WAB configured to talk to: LDAP or SSL? ... I've tried from a local admin account on the ADAM server. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Installing ISA Server for first time
    ... Please note that though correct for HTTP SSL on non standard ports I'm not ... the ISA 2004 can only allow SSL 443 port go through it. ... Microsoft is providing this information as aconvenience to you. ...
    (microsoft.public.windows.server.sbs)
  • Re: Self Signed Certificates
    ... RWW works fine using SSL port 443. ... My config for the site is using port 444, windows authentication, SSL is ...
    (microsoft.public.windows.server.sbs)
  • Re: Installing ISA Server for first time
    ... the ISA 2004 can only allow SSL 443 port go through it. ... Microsoft is providing this information as aconvenience to you. ...
    (microsoft.public.windows.server.sbs)
  • Re: running an ssl webserver
    ... >> My machine is only listening for port 80 connections This is through ... >> How do i open an ssl port on this internal webserver. ... SSLRandomSeed startup builtin ...
    (comp.os.linux.security)