hi all At my 192.168.129.0 network, where my PDC is located, there i am able to join systems without any error, but when i am joining a system at a different subnet ie 192.168.130.0network, where my BDC is located, i am getting "Domain Does not exist or could not be contacted"
my samba version in both pdc and bdc is same ie samba 3.0.21c and openldap version is also same (pdc is master) (bdc is slave ) openldap3.0.21c and DNS (Dynamic DNS) pdc is master , bdc is slave. (bind version 9.2.4.2) Operating system RHEL ES 4.0 at both PDC and BDC. is there any wrong with by BDC configuration. or is it because there is no add machine script in BDC that's why i am not able to add system to domain. should bdc smb.conf also have add machine script. line as it's there in PDC smb.conf or the below bdc smb.conf is enough. my Samba BDC smb.conf ############################## ################################ following is the smb.conf of BDC [global] unix charset = LOCALE workgroup = msdpl.com netbios name = fosrv001 passdb backend = ldapsam:ldap://192.168.130.3 enable privileges = Yes server string = Factory Backup Domain Controller log level = 1 remote announce = 192.168.129.20 <http://192.168.129.255/> remote browse sync = 192.168.129.20 <http://192.168.129.255/> syslog = 0 log file = /usr/local/samba-fo/var/%U.%m.log max log size = 100 smb ports = 139 printcap name = cups show add printer wizard = no logon script = %u.bat logon path = logon drive = X: logon home = domain logons = yes domain master = No hide unreadable = yes deadtime = 15 wins server = 192.168.129.20 name resolve order = lmhosts wins bcast hosts socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 interfaces = eth0, lo bind interfaces only = yes hide dot files = yes dns proxy = no nt acl support = yes ldap passwd sync = yes ldap suffix = dc=msdpl,dc=com ldap admin dn = cn=foreplica,dc=msdpl,dc=com ldap group suffix = ou=Groups ldap user suffix = ou=People ldap machine suffix = ou=Computers ldap idmap suffix = ou=Idmap ldap ssl = no ldap timeout = 50 idmap backend = ldap:ldap://192.168.130.3 idmap uid = 10000-20000 idmap gid = 10000-20000 map acl inherit = yes printing = cups ######################################################[Share Definations]############### [homes] comment = Home Directories valid users = %S browseable = no read only = no nt acl support = Yes # Un-comment the following and create the netlogon directory for Domain Logons [netlogon] comment = Network Logon Service path = /netlogon/scripts guest ok = yes browseable = no write list = root #Profiles Share [profiles] comment = Profiles Share path = /profiles/%U read only = No browseable = yes writeable = yes guest ok = Yes ############################################################## Please Guide me Regards Niranjan On 5/6/06, Asier Baranguan <[EMAIL PROTECTED]> wrote:
El Sábado, 6 de Mayo de 2006 09:30, mallapadi niranjan escribió: > when i am joining win2k client to Domain, > it says "the domain does not exist or could not be contacted" > At client i have setup IP of the 192.168.130.33 with DNS pointing to > 192.168.130.3 I've a similar issue last month with samba 3.0.14a and a very similar setup. I solved it with two approaches: + First, join the machine to the _workgroup_ msdpl.com (in your case), and later adding it to the _domain_ + Upgrading to samba 3.0.22 fixed all the problems. -- Asier. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
-- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
