Re: Outlook 2003 & 2007 clients accessing LDAP

Tech-Archive recommends: Speed Up your PC by fixing your registry



On Sep 27, 8:25 pm, "neo [mvp outlook]"
<n...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
For the outlook 2007 gpo option mentioned in the link, you would want to set
it to enabled.

For the 2003 machine that isn't working... so does this mean that the user
is logging onto the workstation in question with a domain userid/password as
well? Another cross check that you can try on this machine is to see if the
Windows Address Book can successfully query AD. No configuration necessary
since the Windows Address Book already has an LDAP address book setup for
Active Directory.

<msch...@xxxxxxxxxxx> wrote in message

news:1190937083.245355.94740@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx



On Sep 27, 6:45 pm, "neo [mvp outlook]"
<n...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
For the Outlook 2003 workstation:

Since you didn't mention how the LDAP address properties are defined, I
would suggest the following if you imported/copied the settings over from
the Windows Address Book.

* Logon to the workstation using a domain userid/password - the reason
for
this is that a Windows 2003 Active Directory domain controller does not
allow anonymous directory lookups via LDAP

* Verify that the LDAP address book configuration matches that of a
workstation that works

For Outlook 2007:
VLV browsing is disabled by default.
Seehttp://technet2.microsoft.com/Office/en-us/library/ff54b078-5bf8-4f24...
for more information.

<msch...@xxxxxxxxxxx> wrote in message

news:1190928673.639666.215070@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

My company does not have Microsoft Exchange but after research I was
able to successfully use our Windows 2003 Active Directory as a shared
address book. I am running Outlook 2003 client, and when I click on
the list, all the names and email addresses of the employees appear
from the list in the AD. I installed this on another workstation
running Outlook 2003 client and no list appears. When performing a
find, a message appears MAPI_E_CALL_FAILED. I then went to a
workstation that has Outlook 2007 client loaded on it. In this case,
the listing of names do not appear, but the find feature works. Any
help/advise on what is causing these other workstations not to show
the listing of all employees (we have less than 100 employees) would
be appreciated. Have saw some articles realting to Office service
packs, VLV hot fixes, but not sure what the next step should be.
Thanks.- Hide quoted text -

- Show quoted text -

I copied the exact settings from the workstation (Outlook 2003) that
successfully displayed the list to one that did not, and to another
one that was running Outlook 2007. I will look into the VLV browsing
parameter. To confirm, should it be set to enable or disable to
display the list (< 100 users). Thanks.- Hide quoted text -

- Show quoted text -

Just to clairfy, I tried this on two different workstations, both
running XP and Outlook 2003. One PC, mine, is able to successfully
view the list of all employees. The other PC running Outlook 2003
cannot see the list of employees and when doing a find gets a
MAPI_E_CALL_failed error. The LDAP configuration setups are exactly
the same. The Outlook 2007 client has the exact same configuration as
well, cannot see the list of employees, but can perform a find.
Thanks.

.



Relevant Pages

  • Re: Outlook 2003 & 2007 clients accessing LDAP
    ... Since you didn't mention how the LDAP address properties are defined, ... the Windows Address Book. ... Logon to the workstation using a domain userid/password - the reason for ... I am running Outlook 2003 client, ...
    (microsoft.public.outlook)
  • Outlook 2003 & 2007 clients accessing LDAP
    ... I am running Outlook 2003 client, ... workstation that has Outlook 2007 client loaded on it. ... the listing of all employees would ...
    (microsoft.public.outlook)
  • Windows 2000
    ... I am running Outlook 2000 on Windows 2000 workstation. ... When I access Outlook, it takes an extremely unusual long ...
    (microsoft.public.outlook.general)
  • Re: Access server using PP and domain account
    ... With Windows XP using the windows authentication isn't strictly the credentials you use to login to the workstation. ... user account is setup on domain in which project server resides ...
    (microsoft.public.project.pro_and_server)
  • Printer driver-related network delays
    ... I've got a Windows XP LAN comprised of several workstations and printers. ... Every time someone on a workstation tries to print to a network printer from ...
    (microsoft.public.windowsxp.print_fax)