Re: external LDAP
- From: "Bharat Suneja" <bharat@xxxxxxxxxx>
- Date: Thu, 3 Nov 2005 21:57:01 -0800
"Daniel Kaliel" <DanielKaliel@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3B69FF6E-C048-4AD6-A7FF-E21F919E76DE@xxxxxxxxxxxxxxxx
> Sorry, to be more specific. Exchange Server 2003.
>
> What the device is asking for is:
>
> Port Number
> Search Root
> Login Name (Dn)
> Password
>
> I have been using
>
> Port: 389
> Search Root: \ **try using DC=domain,DC=extension (COM, NET)**
> Login Name (Dn): ourdomain\adminacct **not sure if it wants the
> distinguishedName of the user account used to bind**
> Password: adminpass **don't need to be an admin for a simple ldap bind,
> suggest using a service account with no special privileges**
>
> "Bharat Suneja" wrote:
>
>> What version of Exchange?
>> Exchange Server 5.5 had its own LDAP DS
>> Exchange Server 200x directory moved to Windows OS in the form of Active
>> Directory, runs on Domain Controllers.
>> Default ldap port is 389.
>> --
>> Bharat Suneja
>> MCSE, MCT
>> www.zenprise.com
>> blog: www.suneja.com/blog
>> -----------------------------------------
>>
>>
>> "Daniel Kaliel" <DanielKaliel@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:FE15FC4C-0782-44DE-91BA-73B8B211AC21@xxxxxxxxxxxxxxxx
>> >I have a device that use LDAP to pull up a list of possible email
>> >address's,
>> > how do I allow it to connect to the exchange server? It is trying to
>> > use
>> > port 389?
>>
>>
>>
.
- Prev by Date: Re: strange queque
- Next by Date: Re: How Can Remote VPN Users Connect to our Exchange Server?
- Previous by thread: Re: strange queque
- Next by thread: Re: Interesting problem encountered (Restore)
- Index(es):
Relevant Pages
|
