S
Wed Jul 12 04:48:58 CDT 2006
Do nothing. Seriously. Any Active Directory domain controller and ADAM
(Active Directory Application Mode) server provides stock standard LDAP
interface. The UNIX guys will have to configure connection strings etc.
What helps with that is a LDAP browser. There are many for UNIX/Linux, or
you can use Microsoft ADSI edit, or better yet Softerra LDAP browser
(
http://www.ldapadministrator.com). Also you can use MS NetMon or WireShark
to analyse traffic between LDAP client and server. The combo was sufficient
for me to test and configure all cross-platform LDAP connections to date.
--
Svyatoslav Pidgorny, MS MVP - Security, MCSE
-= F1 is the key =-
"Mrunyon" <Mrunyon@discussions.microsoft.com> wrote in message
news:13B1CCFC-AD6C-4CA3-B4E5-F25ABD0E1443@microsoft.com...
> O.k.,
>
> So as not to confuse anyone, I'm gonna start a new thread on this subject.
> What I've been requested to do is setup an Active Directory server to
> allow
> secure LDAP communication between our "Unix" guys "Jabber" server and our
> Active Directory Services. They tell me they have their end set and ready
> to
> go, but they need a server from A.D. listen on a port for LDAP requests.
> Hand
> on the buzzer, if anyone knows what they are talking about? I'm not sure
> what
> they mean? I thought like previous statements that as long as I gave them
> an
> ID in A.D., they could configure their stuff fine, but I don't think that
> is
> what they mean?
>
> Thanks for the thoughts...
> --
> Matty