I currently have some Linux systems using NIS as a directory service and I have been tasked with evaluating LDAP then moving all the Linux workstations (and Solaris servers) to an LDAP domain. Currently we have several NIS domains spanning 4 sites (each site has its own). We would like to combine them this year into 1 LDAP domain with the possibility of single sign on with AD next year.

Currently there is an AD domain called company.com existing on site. All 4 sites have Windows2k workstations which are part of this domain. This leaves me with several questions which I was hoping somebody might have some experience with:

1. Can you have an LDAP directory service called company.com if there is already an AD domain called company.com?
2. If you can are there any issues with having both called company.com?
3. Will it make integration with AD easier in the future if both are called company.com or is it fairly easy to rename the LDAP directory?

Anything else you might add would be appreciated.

Thanks all.

I think AD names and LDAP names should be uniq since AD is LDAP at its core. But if they are on different servers it might work. I found a nice OpenSource product called pGina that allows me to get rid of AD though. I install pGina on all my 2000/XP boxed and can authenticate my windows 2000/XP users against a OpenLdap server (Linux). The Linux LDAP server is much less complicated and reliable than the AD servers were. I also found a mailserver called Bynari Insight Server that rids me of Exchange server, god what a nightmare those were, but no more. You can, using Insight Server and pGina, authenticate users and mail users against the Insight OpenLDAP server, really cheap and reliable compared to any Microsoft solution.

Regards

Doug P

AD domain and LDAP are in no way related. I dont see a problem using the same suffix (dc=domain,dc=com) as your AD domain. You might want to explore the idea of using unix auth schemas inside of AD.....I havent tried this but AD is an ldap server. You might be able to store your unix authentication stuff inside of AD. I can foresee problems with storing hashes and such....but its worth a try.