I am running centos 5.5 using samba3x as a pdc. I migrated to samba3x so that I could join Windows 7 machines to the domain. It is a new setup using a tried and true configuration from a different box. I have used this configuration in the past to joing Windows XP Pro machines. And I havn't found anyting helpful on the error with google. I can ping the server name and the server can ping the windows 7 box. I can access smaba shares on the server but I cannot join the domain.
I have applied the reg settings to win7 and when I try to join I get this error.
An Active Directory Domain Controller (AD DC) for domain admin could not be contacted.
Ensure that the domain name is typed correctly.
If the name is correct, click Details for troubleshooting information.
The details read:
Note: This information is intended for a network administrator. If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\Windows\debug\dcdiag.txt. The domain name "admin" might be a NetBIOS domain name. If this is the case, verify that the domain name is properly registered with WINS. If you are certain that the name is not a NetBIOS domain name, then the following information can help you troubleshoot your DNS configuration. The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain "admin": The error was: "DNS name does not exist." (error code 0x0000232B RCODE_NAME_ERROR) The query was for the SRV record for _ldap._tcp.dc._msdcs.admin Common causes of this error include the following: - The DNS SRV records required to locate a AD DC for the domain are not registered in DNS. These records are registered with a DNS server automatically when a AD DC is added to a domain. They are updated by the AD DC at set intervals. This computer is configured to use DNS servers with the following IP addresses: 192.168.4.1 - One or more of the following zones do not include delegation to its child zone: admin . (the root zone)
I seem to have a DNS problem but I don't even know what it should be doing so that I know where to start to troubleshoot.
Thanks for any help!
Doug
On Wed, 2010-07-07 at 20:40 -0500, Doug Coats wrote:
I am running centos 5.5 using samba3x as a pdc. I migrated to samba3x so that I could join Windows 7 machines to the domain. It is a new setup using a tried and true configuration from a different box. I have used this configuration in the past to joing Windows XP Pro machines. And I havn't found anyting helpful on the error with google. I can ping the server name and the server can ping the windows 7 box. I can access smaba shares on the server but I cannot join the domain.
I have applied the reg settings to win7 and when I try to join I get this error.
An Active Directory Domain Controller (AD DC) for domain admin could not be contacted.
Ensure that the domain name is typed correctly.
If the name is correct, click Details for troubleshooting information.
The details read:
Note: This information is intended for a network administrator. If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\Windows\debug\dcdiag.txt. The domain name "admin" might be a NetBIOS domain name. If this is the case, verify that the domain name is properly registered with WINS. If you are certain that the name is not a NetBIOS domain name, then the following information can help you troubleshoot your DNS configuration. The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain "admin": The error was: "DNS name does not exist." (error code 0x0000232B RCODE_NAME_ERROR) The query was for the SRV record for _ldap._tcp.dc._msdcs.admin Common causes of this error include the following:
- The DNS SRV records required to locate a AD DC for the domain are
not registered in DNS. These records are registered with a DNS server automatically when a AD DC is added to a domain. They are updated by the AD DC at set intervals. This computer is configured to use DNS servers with the following IP addresses: 192.168.4.1
- One or more of the following zones do not include delegation to its
child zone: admin . (the root zone)
I seem to have a DNS problem but I don't even know what it should be doing so that I know where to start to troubleshoot.
Thanks for any help!
---- Samba 3.x cannot provide AD and thus the error about AD & DNS name does not exist is not meaningful
You probably want to use Sernet Samba packages at this point if you want to use Windows 7 clients but see this page...
http://wiki.samba.org/index.php/Windows7
Craig
I am not using Samba 3.x. I am using Samba3x-3.3.8. As I understand it, RHEL provided this branch so that Windows 7 could join a Samba domain.
That aside, It does not seems to me that the error message indicates that it cannot resolve where the PDC is. What method is Windows 7 trying to use that is differnent for Windows XP to find the PDC?
Samba 3.x cannot provide AD and thus the error about AD & DNS name does not exist is not meaningful
You probably want to use Sernet Samba packages at this point if you want to use Windows 7 clients but see this page...
http://wiki.samba.org/index.php/Windows7
Craig
-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Thu, 2010-07-08 at 08:13 -0500, Doug Coats wrote:
I am not using Samba 3.x. I am using Samba3x-3.3.8. As I understand it, RHEL provided this branch so that Windows 7 could join a Samba domain.
That aside, It does not seems to me that the error message indicates that it cannot resolve where the PDC is. What method is Windows 7 trying to use that is differnent for Windows XP to find the PDC?
---- I think as long as persist in chasing pointless ends, you will continue to fail.
DNS & AD are not at issue here. Samba 3 cannot provide AD services.
If resolution is a problem, it may be that you don't have nmb running on your Samba server and you probably want it to be a wins server if it is a Domain Controller.
Craig
I think as long as persist in chasing pointless ends, you will continue to fail.
DNS & AD are not at issue here. Samba 3 cannot provide AD services.
If resolution is a problem, it may be that you don't have nmb running on your Samba server and you probably want it to be a wins server if it is a Domain Controller.
Craig
Craig,
Thanks for you interest in my problem. I don't think I am trying to get Samba to do something that it was not intended to do. All I am saying is that using the same config on Samba 3.0 as a PDC with windows XP machines behaves different than Samba3x with Windows 7 and windows XP machines.
I just now tried to join an XP machine to the network and got a similar error. Maybe this is a Samba3x.3.3.8 issue?
I don't expect Samba to provide AD services. I simply want single sign-on on my network.
Has anyone been able to get Samba3x.3.3.8 to work as a PDC?
On Thu, 2010-07-08 at 10:34 -0500, Doug Coats wrote:
I think as long as persist in chasing pointless ends, you will continue to fail. DNS & AD are not at issue here. Samba 3 cannot provide AD services. If resolution is a problem, it may be that you don't have nmb running on your Samba server and you probably want it to be a wins server if it is a Domain Controller. CraigCraig,
Thanks for you interest in my problem. I don't think I am trying to get Samba to do something that it was not intended to do. All I am saying is that using the same config on Samba 3.0 as a PDC with windows XP machines behaves different than Samba3x with Windows 7 and windows XP machines.
I just now tried to join an XP machine to the network and got a similar error. Maybe this is a Samba3x.3.3.8 issue?
I don't expect Samba to provide AD services. I simply want single sign-on on my network.
Has anyone been able to get Samba3x.3.3.8 to work as a PDC?
---- I think you are being vague (similar error).
What is the exact error?
What is the output of 'testparm -sv' ?
Craig
I think you are being vague (similar error).
What is the exact error?
What is the output of 'testparm -sv' ?
Craig
Sorry for being to vague.
Here is the XP Pro error I get when I try to join the domain.
A domian controller for the domain admin could not be contacted.
Esure that the domain name is typed correctly.
If the name is correct, click on the Details for troubleshooting information.
Details:
Note: This information is intended for a network administrator. If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\WINDOWS\debug\dcdiag.txt. The domain name admin might be a NetBIOS domain name. If this is the case, verify that the domain name is properly registered with WINS. If you are certain that the name is not a NetBIOS domain name, then the following information can help you troubleshoot your DNS configuration. An error occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain admin. The error was: "No records found for given DNS query." (error code 0x0000251D DNS_INFO_NO_RECORDS) The query was for the SRV record for _ldap._tcp.dc._msdcs.admin For more information, click Help.
Here is the testparm -sv you requested.
For a short explaination of the IP's listed. We have two domains. One served by 192.168.6.1 and one by 192.168.5.1. I am currantly upgrading the 192.168.6. network to Windows 7. Or atleast trying. 192.168.4.1 is our gatway and the two servers listed above act as file servers and routers for their domains. I hope that makes sence.
Load smb config files from /etc/samba/smb.conf Processing section "[homes]" Processing section "[netlogon]" WARNING: The "share modes" option is deprecated Processing section "[admin]" Processing section "[staff]" Processing section "[ElemTeachers]" Processing section "[SecTeachers]" Processing section "[it]" Processing section "[office]" Processing section "[finance]" Processing section "[backup]" Processing section "[www]" Processing section "[scribeshare]" Processing section "[sosub]" Loaded services file OK. Server role: ROLE_DOMAIN_PDC [global] dos charset = CP850 unix charset = UTF-8 display charset = LOCALE workgroup = ADMIN realm = netbios name = HERITAGE3 netbios aliases = netbios scope = server string = Administration Samba Server interfaces = 192.168.4.3, 192.168.6.1, 127.0.0.1 bind interfaces only = No config backend = file security = USER auth methods = encrypt passwords = Yes update encrypted = No client schannel = Auto server schannel = Auto allow trusted domains = Yes map to guest = Never null passwords = No obey pam restrictions = No password server = * smb passwd file = /etc/samba/smbpasswd private dir = /var/lib/samba/private passdb backend = smbpasswd algorithmic rid base = 1000 root directory = guest account = nobody enable privileges = Yes pam password change = No passwd program = passwd chat = *new*password* %n\n *new*password* %n\n *changed* passwd chat debug = No passwd chat timeout = 2 check password script = username map = password level = 0 username level = 0 unix password sync = No restrict anonymous = 0 lanman auth = No ntlm auth = Yes client NTLMv2 auth = No client lanman auth = No client plaintext auth = No preload modules = use kerberos keytab = No log level = 1 syslog = 1 syslog only = No log file = /var/log/samba/%m.log max log size = 50 debug timestamp = Yes debug prefix timestamp = No debug hires timestamp = No debug pid = No debug uid = No debug class = No enable core files = Yes smb ports = 445 139 large readwrite = Yes max protocol = NT1 min protocol = CORE min receivefile size = 0 read raw = Yes write raw = Yes disable netbios = No reset on zero vc = No acl compatibility = auto defer sharing violations = Yes nt pipe support = Yes nt status support = Yes announce version = 4.9 announce as = NT max mux = 50 max xmit = 16644 name resolve order = hosts wins lmhosts bcast max ttl = 259200 max wins ttl = 518400 min wins ttl = 21600 time server = Yes unix extensions = Yes use spnego = Yes client signing = auto server signing = No client use spnego = Yes client ldap sasl wrapping = plain enable asu support = No svcctl list = deadtime = 0 getwd cache = Yes keepalive = 300 lpq cache time = 30 max smbd processes = 0 paranoid server security = Yes max disk size = 0 max open files = 10000 socket options = TCP_NODELAY use mmap = Yes hostname lookups = No name cache timeout = 660 ctdbd socket = cluster addresses = clustering = No load printers = Yes printcap cache time = 750 printcap name = cups server = cups connection timeout = 30 iprint server = disable spoolss = No addport command = enumports command = addprinter command = deleteprinter command = show add printer wizard = Yes os2 driver map = mangling method = hash2 mangle prefix = 1 max stat cache size = 256 stat cache = Yes machine password timeout = 604800 add user script = rename user script = delete user script = add group script = delete group script = add user to group script = delete user from group script = set primary group script = add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u shutdown script = abort shutdown script = username map script = logon script = %U.bat logon path = logon drive = logon home = domain logons = Yes init logon delayed hosts = init logon delay = 100 os level = 20 lm announce = Auto lm interval = 60 preferred master = No local master = Yes domain master = Yes browse list = Yes enhanced browsing = Yes dns proxy = Yes wins proxy = Yes wins server = 192.168.4.1 wins support = No wins hook = kernel oplocks = Yes lock spin time = 200 oplock break wait time = 0 ldap admin dn = ldap delete dn = No ldap group suffix = ldap idmap suffix = ldap machine suffix = ldap passwd sync = no ldap replication sleep = 1000 ldap suffix = ldap ssl = start tls ldap ssl ads = No ldap timeout = 15 ldap connection timeout = 2 ldap page size = 1024 ldap user suffix = ldap debug level = 0 ldap debug threshold = 10 eventlog list = add share command = change share command = delete share command = config file = preload = lock directory = /var/lib/samba pid directory = /var/run utmp directory = wtmp directory = utmp = No default service = message command = get quota command = set quota command = remote announce = 192.168.5.255 192.168.4.255 192.168.0.255 remote browse sync = socket address = 0.0.0.0 homedir map = auto.home afs username map = afs token lifetime = 604800 log nt token command = time offset = 0 NIS homedir = No registry shares = No usershare allow guests = No usershare max shares = 0 usershare owner only = Yes usershare path = /var/lib/samba/usershares usershare prefix allow list = usershare prefix deny list = usershare template share = panic action = host msdfs = Yes passdb expand explicit = No idmap backend = tdb idmap alloc backend = idmap cache time = 604800 idmap negative cache time = 120 idmap uid = idmap gid = template homedir = /home/%D/%U template shell = /bin/false winbind separator = \ winbind cache time = 300 winbind reconnect delay = 30 winbind enum users = No winbind enum groups = No winbind use default domain = No winbind trusted domains only = No winbind nested groups = Yes winbind expand groups = 1 winbind nss info = template winbind refresh tickets = No winbind offline logon = No winbind normalize names = No winbind rpc only = No comment = path = username = invalid users = valid users = admin users = read list = write list = printer admin = force user = force group = read only = Yes acl check permissions = Yes acl group control = No acl map full control = Yes create mask = 0744 force create mode = 00 security mask = 0777 force security mode = 00 directory mask = 0755 force directory mode = 00 directory security mask = 0777 force directory security mode = 00 force unknown acl user = No inherit permissions = No inherit acls = No inherit owner = No guest only = No administrative share = No guest ok = No only user = No hosts allow = 192.168.4., 192.168.5., 192.168.6., 192.168.1., 127. hosts deny = allocation roundup size = 1048576 aio read size = 0 aio write size = 0 aio write behind = ea support = No nt acl support = Yes profile acls = No map acl inherit = No afs share = No smb encrypt = auto block size = 1024 change notify = Yes directory name cache size = 100 kernel change notify = Yes max connections = 0 min print space = 0 strict allocate = No strict sync = No sync always = No use sendfile = No write cache size = 0 max reported print jobs = 0 max print jobs = 1000 printable = No printing = cups cups options = print command = lpq command = %p lprm command = lppause command = lpresume command = queuepause command = queueresume command = printer name = use client driver = No default devmode = Yes force printername = No printjob username = %U default case = lower case sensitive = Auto preserve case = Yes short preserve case = Yes mangling char = ~ hide dot files = Yes hide special files = No hide unreadable = No hide unwriteable files = No delete veto files = No veto files = hide files = veto oplock files = map archive = Yes map hidden = No map system = No map readonly = yes mangled names = Yes store dos attributes = No dmapi support = No browseable = Yes blocking locks = Yes csc policy = manual fake oplocks = No locking = Yes oplocks = Yes level2 oplocks = Yes oplock contention limit = 2 posix locking = Yes strict locking = Auto share modes = Yes dfree cache time = 0 dfree command = copy = include = preexec = preexec close = No postexec = root preexec = root preexec close = No root postexec = available = Yes volume = fstype = NTFS set directory = No wide links = Yes follow symlinks = Yes dont descend = magic script = magic output = delete readonly = No dos filemode = No dos filetimes = Yes dos filetime resolution = No fake directory create times = No vfs objects = msdfs root = No msdfs proxy =
Followed by a list of shares.
Thanks again for your help!
Sorry for being to vague.
Here is the XP Pro error I get when I try to join the domain. A domian controller for the domain admin could not be contacted. Esure that the domain name is typed correctly. If the name is correct, click on the Details for troubleshooting information.
Details:
Note: This information is intended for a network administrator. If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\WINDOWS\debug\dcdiag.txt. The domain name admin might be a NetBIOS domain name. If this is the case, verify that the domain name is properly registered with WINS. If you are certain that the name is not a NetBIOS domain name, then the following information can help you troubleshoot your DNS configuration. An error occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain admin. The error was: "No records found for given DNS query." (error code 0x0000251D DNS_INFO_NO_RECORDS) The query was for the SRV record for _ldap._tcp.dc._msdcs.admin For more information, click Help.
Here is the testparm -sv you requested.
For a short explaination of the IP's listed. We have two domains. One served by 192.168.6.1 and one by 192.168.5.1. I am currantly upgrading the 192.168.6. network to Windows 7. Or atleast trying. 192.168.4.1 is our gatway and the two servers listed above act as file servers and routers for their domains. I hope that makes sence.
It seems, that the samba domain controller 192.168.6.1 fails to register with the WINS server - 192.168.4.1, and the XP station cannot locate it. You'd better post your smb.conf file and verify if the domain controller registers with WINS server.
Best regards, Alexander.
On Thu, 2010-07-08 at 12:03 -0500, Doug Coats wrote:
I think you are being vague (similar error). What is the exact error? What is the output of 'testparm -sv' ? CraigSorry for being to vague.
Here is the XP Pro error I get when I try to join the domain.
A domian controller for the domain admin could not be contacted.
Esure that the domain name is typed correctly.
If the name is correct, click on the Details for troubleshooting information.
Details:
Note: This information is intended for a network administrator. If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\WINDOWS\debug\dcdiag.txt. The domain name admin might be a NetBIOS domain name. If this is the case, verify that the domain name is properly registered with WINS. If you are certain that the name is not a NetBIOS domain name, then the following information can help you troubleshoot your DNS configuration. An error occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain admin. The error was: "No records found for given DNS query." (error code 0x0000251D DNS_INFO_NO_RECORDS) The query was for the SRV record for _ldap._tcp.dc._msdcs.admin For more information, click Help.
Here is the testparm -sv you requested.
For a short explaination of the IP's listed. We have two domains. One served by 192.168.6.1 and one by 192.168.5.1. I am currantly upgrading the 192.168.6. network to Windows 7. Or atleast trying. 192.168.4.1 is our gatway and the two servers listed above act as file servers and routers for their domains. I hope that makes sence.
Load smb config files from /etc/samba/smb.conf Processing section "[homes]" Processing section "[netlogon]" WARNING: The "share modes" option is deprecated Processing section "[admin]" Processing section "[staff]" Processing section "[ElemTeachers]" Processing section "[SecTeachers]" Processing section "[it]" Processing section "[office]" Processing section "[finance]" Processing section "[backup]" Processing section "[www]" Processing section "[scribeshare]" Processing section "[sosub]" Loaded services file OK. Server role: ROLE_DOMAIN_PDC [global] dos charset = CP850 unix charset = UTF-8 display charset = LOCALE workgroup = ADMIN realm = netbios name = HERITAGE3 netbios aliases = netbios scope = server string = Administration Samba Server interfaces = 192.168.4.3, 192.168.6.1, 127.0.0.1 bind interfaces only = No config backend = file security = USER auth methods = encrypt passwords = Yes update encrypted = No client schannel = Auto server schannel = Auto allow trusted domains = Yes map to guest = Never null passwords = No obey pam restrictions = No password server = * smb passwd file = /etc/samba/smbpasswd private dir = /var/lib/samba/private passdb backend = smbpasswd algorithmic rid base = 1000 root directory = guest account = nobody enable privileges = Yes pam password change = No passwd program = passwd chat = *new*password* %n\n *new*password* %n\n *changed* passwd chat debug = No passwd chat timeout = 2 check password script = username map = password level = 0 username level = 0 unix password sync = No restrict anonymous = 0 lanman auth = No ntlm auth = Yes client NTLMv2 auth = No client lanman auth = No client plaintext auth = No preload modules = use kerberos keytab = No log level = 1 syslog = 1 syslog only = No log file = /var/log/samba/%m.log max log size = 50 debug timestamp = Yes debug prefix timestamp = No debug hires timestamp = No debug pid = No debug uid = No debug class = No enable core files = Yes smb ports = 445 139 large readwrite = Yes max protocol = NT1 min protocol = CORE min receivefile size = 0 read raw = Yes write raw = Yes disable netbios = No reset on zero vc = No acl compatibility = auto defer sharing violations = Yes nt pipe support = Yes nt status support = Yes announce version = 4.9 announce as = NT max mux = 50 max xmit = 16644 name resolve order = hosts wins lmhosts bcast max ttl = 259200 max wins ttl = 518400 min wins ttl = 21600 time server = Yes unix extensions = Yes use spnego = Yes client signing = auto server signing = No client use spnego = Yes client ldap sasl wrapping = plain enable asu support = No svcctl list = deadtime = 0 getwd cache = Yes keepalive = 300 lpq cache time = 30 max smbd processes = 0 paranoid server security = Yes max disk size = 0 max open files = 10000 socket options = TCP_NODELAY use mmap = Yes hostname lookups = No name cache timeout = 660 ctdbd socket = cluster addresses = clustering = No load printers = Yes printcap cache time = 750 printcap name = cups server = cups connection timeout = 30 iprint server = disable spoolss = No addport command = enumports command = addprinter command = deleteprinter command = show add printer wizard = Yes os2 driver map = mangling method = hash2 mangle prefix = 1 max stat cache size = 256 stat cache = Yes machine password timeout = 604800 add user script = rename user script = delete user script = add group script = delete group script = add user to group script = delete user from group script = set primary group script = add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u shutdown script = abort shutdown script = username map script = logon script = %U.bat logon path = logon drive = logon home = domain logons = Yes init logon delayed hosts = init logon delay = 100 os level = 20 lm announce = Auto lm interval = 60 preferred master = No local master = Yes domain master = Yes browse list = Yes enhanced browsing = Yes dns proxy = Yes wins proxy = Yes wins server = 192.168.4.1 wins support = No wins hook = kernel oplocks = Yes lock spin time = 200 oplock break wait time = 0 ldap admin dn = ldap delete dn = No ldap group suffix = ldap idmap suffix = ldap machine suffix = ldap passwd sync = no ldap replication sleep = 1000 ldap suffix = ldap ssl = start tls ldap ssl ads = No ldap timeout = 15 ldap connection timeout = 2 ldap page size = 1024 ldap user suffix = ldap debug level = 0 ldap debug threshold = 10 eventlog list = add share command = change share command = delete share command = config file = preload = lock directory = /var/lib/samba pid directory = /var/run utmp directory = wtmp directory = utmp = No default service = message command = get quota command = set quota command = remote announce = 192.168.5.255 192.168.4.255 192.168.0.255 remote browse sync = socket address = 0.0.0.0 homedir map = auto.home afs username map = afs token lifetime = 604800 log nt token command = time offset = 0 NIS homedir = No registry shares = No usershare allow guests = No usershare max shares = 0 usershare owner only = Yes usershare path = /var/lib/samba/usershares usershare prefix allow list = usershare prefix deny list = usershare template share = panic action = host msdfs = Yes passdb expand explicit = No idmap backend = tdb idmap alloc backend = idmap cache time = 604800 idmap negative cache time = 120 idmap uid = idmap gid = template homedir = /home/%D/%U template shell = /bin/false winbind separator = \ winbind cache time = 300 winbind reconnect delay = 30 winbind enum users = No winbind enum groups = No winbind use default domain = No winbind trusted domains only = No winbind nested groups = Yes winbind expand groups = 1 winbind nss info = template winbind refresh tickets = No winbind offline logon = No winbind normalize names = No winbind rpc only = No comment = path = username = invalid users = valid users = admin users = read list = write list = printer admin = force user = force group = read only = Yes acl check permissions = Yes acl group control = No acl map full control = Yes create mask = 0744 force create mode = 00 security mask = 0777 force security mode = 00 directory mask = 0755 force directory mode = 00 directory security mask = 0777 force directory security mode = 00 force unknown acl user = No inherit permissions = No inherit acls = No inherit owner = No guest only = No administrative share = No guest ok = No only user = No hosts allow = 192.168.4., 192.168.5., 192.168.6., 192.168.1., 127. hosts deny = allocation roundup size = 1048576 aio read size = 0 aio write size = 0 aio write behind = ea support = No nt acl support = Yes profile acls = No map acl inherit = No afs share = No smb encrypt = auto block size = 1024 change notify = Yes directory name cache size = 100 kernel change notify = Yes max connections = 0 min print space = 0 strict allocate = No strict sync = No sync always = No use sendfile = No write cache size = 0 max reported print jobs = 0 max print jobs = 1000 printable = No printing = cups cups options = print command = lpq command = %p lprm command = lppause command = lpresume command = queuepause command = queueresume command = printer name = use client driver = No default devmode = Yes force printername = No printjob username = %U default case = lower case sensitive = Auto preserve case = Yes short preserve case = Yes mangling char = ~ hide dot files = Yes hide special files = No hide unreadable = No hide unwriteable files = No delete veto files = No veto files = hide files = veto oplock files = map archive = Yes map hidden = No map system = No map readonly = yes mangled names = Yes store dos attributes = No dmapi support = No browseable = Yes blocking locks = Yes csc policy = manual fake oplocks = No locking = Yes oplocks = Yes level2 oplocks = Yes oplock contention limit = 2 posix locking = Yes strict locking = Auto share modes = Yes dfree cache time = 0 dfree command = copy = include = preexec = preexec close = No postexec = root preexec = root preexec close = No root postexec = available = Yes volume = fstype = NTFS set directory = No wide links = Yes follow symlinks = Yes dont descend = magic script = magic output = delete readonly = No dos filemode = No dos filetimes = Yes dos filetime resolution = No fake directory create times = No vfs objects = msdfs root = No msdfs proxy =
---- If you want domain logins - you have to have a PDC and this system should:
preferred master = yes remote announce = 192.168.5.255 192.168.4.255 192.168.0.255 remove this ========== ^^^^^^^^^^^^^
but it would appear that your WINS server 192.168.4.1 may not actually be a wins server or not the dmb (domain master browser) and not winning the elections so it's hard to figure out which computer is the PDC.
What is output of 'nmblookup -A 192.168.4.1' ?
I think this is where your problem is.
Personally, I would make the PDC system the WINS server
wins support = true and comment out the line pointing it to another wins server
set 'os level = 64' so that it wins all the elections and is the WINS server for all networks it is on.
Also FWIW - It would seem that you have a lot of users/networks and I would not use smbpasswd as the passdb - but would suggest using the tdb as it is more robust/versatile and really recommend that you get into LDAP instead (of course this has nothing to do with your problem).
Craig
On Thu, 2010-07-08 at 12:03 -0500, Doug Coats wrote:
Here is the testparm -sv you requested.
For a short explaination of the IP's listed. We have two domains. One served by 192.168.6.1 and one by 192.168.5.1. I am currantly upgrading the 192.168.6. network to Windows 7. Or atleast trying. 192.168.4.1 is our gatway and the two servers listed above act as file servers and routers for their domains. I hope that makes sence.
Load smb config files from /etc/samba/smb.conf
--- To be truth full I think you have an out right mess going on here. One thing your smb config is 10 miles long.
Start over on a fresh install test machine and try joining the W7 machine to it. Then take your changes and merg into your current working machine config. Life will be a lot easier. One change at a time.
John
On Thu, 2010-07-08 at 13:44 -0400, JohnS wrote:
On Thu, 2010-07-08 at 12:03 -0500, Doug Coats wrote:
Here is the testparm -sv you requested.
For a short explaination of the IP's listed. We have two domains. One served by 192.168.6.1 and one by 192.168.5.1. I am currantly upgrading the 192.168.6. network to Windows 7. Or atleast trying. 192.168.4.1 is our gatway and the two servers listed above act as file servers and routers for their domains. I hope that makes sence.
Load smb config files from /etc/samba/smb.conf
To be truth full I think you have an out right mess going on here. One thing your smb config is 10 miles long.
Start over on a fresh install test machine and try joining the W7 machine to it. Then take your changes and merg into your current working machine config. Life will be a lot easier. One change at a time.
---- the reason the smb.conf is 10 miles long is that I told him to output 'testparm -sv' which includes all specific settings and all assumed defaults.
His problem is WINS resolution doesn't tell the workstations which computer is the domain controller and that is what he needs to fix (first by designating a domain controller and then by making sure that WINS is functioning well).
Craig
His problem is WINS resolution doesn't tell the workstations which computer is the domain controller and that is what he needs to fix (first by designating a domain controller and then by making sure that WINS is functioning well).
Craig
Thanks for all the help. I agree that WINS seems to be the issue, or atleast it is a place that we can start with to help track down the issue.
Currently 192.168.4.1 is the WINS server. This is necessary because I need cross subnet brownsing between 192.168.6. and 192.168.5. According to the man page for smb.conf only one computer on your network can be a WINS server and this is the computer that all other computers have access to.
That being said 192.168.6. and 192.168.5. are both PDC's for their subnet. All I have done is moved the 192.168.6.1 configuration to a new machine. Replaced that machine. Removed Samba 3.0 and Installed Samba3x.
How do I make sure that 192.168.4.1 recognizes 192.168.6.1 as the ADMIN PDC so that WINS traffic is directed correctly?
On Thu, 2010-07-08 at 12:58 -0500, Doug Coats wrote:
His problem is WINS resolution doesn't tell the workstations which computer is the domain controller and that is what he needs to fix (first by designating a domain controller and then by making sure that WINS is functioning well). CraigThanks for all the help. I agree that WINS seems to be the issue, or atleast it is a place that we can start with to help track down the issue.
Currently 192.168.4.1 is the WINS server. This is necessary because I need cross subnet brownsing between 192.168.6. and 192.168.5. According to the man page for smb.conf only one computer on your network can be a WINS server and this is the computer that all other computers have access to.
That being said 192.168.6. and 192.168.5. are both PDC's for their subnet. All I have done is moved the 192.168.6.1 configuration to a new machine. Replaced that machine. Removed Samba 3.0 and Installed Samba3x.
How do I make sure that 192.168.4.1 recognizes 192.168.6.1 as the ADMIN PDC so that WINS traffic is directed correctly?
---- a 'network' is 192.168.x assuming that you are using class C subnet masks (255.255.255.0) and so you should have a WINS server on EACH network (192.168.4, 192.168.5, 192.168.6, etc.)
Cross network browsing is somewhat of a hit or miss and not reliable... for a number of reasons such as the default firewall settings for Windows systems will only allow network traffic to the immediate network that it is on (i.e. 192.168.6)
The important thing is to get the WINS working on EACH network. It's also easiest to have your PDC be the WINS server - period.
Also, a PDC must necessarily have...
domain master = yes preferred master = yes domain logins = yes security = user
Craig
a 'network' is 192.168.x assuming that you are using class C subnet
masks (255.255.255.0) and so you should have a WINS server on EACH network (192.168.4, 192.168.5, 192.168.6, etc.)
Cross network browsing is somewhat of a hit or miss and not reliable... for a number of reasons such as the default firewall settings for Windows systems will only allow network traffic to the immediate network that it is on (i.e. 192.168.6)
The important thing is to get the WINS working on EACH network. It's also easiest to have your PDC be the WINS server - period.
Also, a PDC must necessarily have...
domain master = yes preferred master = yes domain logins = yes security = user
Craig
I agree that preferred master should have been set to yes. I made that change with but still no joy.
I don't mean to be contrary but our cross subnet browsing has been working since 2003 when we set up this network. It has been very reliable and I depend on it to work. And I believe it is because of have our WINS servers the way that they are.
I do think that I have hit upon an issue. The WINS data for samba is kept in /var/cache/samba.dat but it is updated dynamically with nmdb. It has dated data. When I moved the server I changed the server name slightly and so the WINS data points to the old name at the current IP. In fact with this network rebuild I changed most of my computer names and they are all incorrect. I think I need to shut down all three instances of samba clear the wins data and then start them all again so that they populate from scratch.
Doug
I do think that I have hit upon an issue. The WINS data for samba is kept in /var/cache/samba.dat but it is updated dynamically with nmdb. It has dated data. When I moved the server I changed the server name slightly and so the WINS data points to the old name at the current IP. In fact with this network rebuild I changed most of my computer names and they are all incorrect. I think I need to shut down all three instances of samba clear the wins data and then start them all again so that they populate from scratch.
Correction to that. Only the WINS server has data in this location.
Doug Coats wrote:
I do think that I have hit upon an issue. The WINS data for samba is kept in /var/cache/samba.dat but it is updated dynamically with nmdb.
It has
dated data. When I moved the server I changed the server name slightly and so the WINS data points to the old name at the current IP. In fact
with
this network rebuild I changed most of my computer names and they are all incorrect. I think I need to shut down all three instances of samba clear the wins data and then start them all again so that they populate
from
scratch.
Correction to that. Only the WINS server has data in this location.
Um, does a timing issue come into play here? If the local clock is not within a few seconds, we can't connect to AD (we are going through kerborous). Is there time data in the cache?
mark
Um, does a timing issue come into play here? If the local clock is not within a few seconds, we can't connect to AD (we are going through kerborous). Is there time data in the cache?
mark
Both the XP box and the Windows 7 use the PDC server as their time server so they are set to the same time.
Doug
Doug Coats wrote:
mark wrote:
Um, does a timing issue come into play here? If the local clock is not within a few seconds, we can't connect to AD (we are going through kerborous). Is there time data in the cache?
Both the XP box and the Windows 7 use the PDC server as their time server so they are set to the same time.
How 'bout with the server that's supposed to be the master, above the two other PDCs?
mark
On Thu, 2010-07-08 at 13:41 -0500, Doug Coats wrote:
I agree that preferred master should have been set to yes. I made that change with but still no joy.
I don't mean to be contrary but our cross subnet browsing has been working since 2003 when we set up this network. It has been very reliable and I depend on it to work. And I believe it is because of have our WINS servers the way that they are.
Contrary? Well I had to ask. Because it has to work like that for your SNMs. NP
I do think that I have hit upon an issue. The WINS data for samba is kept in /var/cache/samba.dat but it is updated dynamically with nmdb. It has dated data. When I moved the server I changed the server name slightly and so the WINS data points to the old name at the current IP. In fact with this network rebuild I changed most of my computer names and they are all incorrect. I think I need to shut down all three instances of samba clear the wins data and then start them all again so that they populate from scratch.
Doug
--- Ok since you say the interdomain networking is functioning (triangle routing) have a read at this: http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/domain-member.htm...
John
all else that fails put that machine on another known working Subnet and have a go at that.
Ok since you say the interdomain networking is functioning (triangle routing) have a read at this:
http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/domain-member.htm...
John
all else that fails put that machine on another known working Subnet and have a go at that.
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
As I said in another post I changed the machine name to an entirely different format and I didn't copy any domain information from the prior machine(meaning I didn't try to migrate the information placed in the smbpasswd). Since all the machines were being switched to Windows 7 I wanted a clean start.
On Thu, 2010-07-08 at 14:12 -0500, Doug Coats wrote:
As I said in another post I changed the machine name to an entirely different format and I didn't copy any domain information from the prior machine(meaning I didn't try to migrate the information placed in the smbpasswd). Since all the machines were being switched to Windows 7 I wanted a clean start.
--- I see now. I went back and read your whole thread. Just like Craig has said to you in the last mail it will not work as you expect. There has to be a helper or Wins server on each of the SNs to contact the Master Browser. That's is the only I am aware of doing it the right way also.
You could pass them off of a DHCP Helper server but I suspect that's beyond what you want. The thing is the network is a Ad-Hoc Network and there hard to deal with with out proper prior planing.
John
On 7/8/2010 1:15 PM, Craig White wrote:
a 'network' is 192.168.x assuming that you are using class C subnet masks (255.255.255.0) and so you should have a WINS server on EACH network (192.168.4, 192.168.5, 192.168.6, etc.)
I thought the point of WINS was to have a single address that would collate the names/addresses from all your networks.
The important thing is to get the WINS working on EACH network. It's also easiest to have your PDC be the WINS server - period.
But PDC's aren't limited to one subnet either.
With the WINS data cleared. for the past 20 min. (I did it before I wrote about it) Neither PDC has reported to WINS. So no wonder my PC's can't find their domain.
So how do I make sure that 192.168.6.1 is added to wins.dat. I could do it manually but I would rather it communicate the way that it was intended to just so I know that the network is configured and working correctly.
Doug
On 7/8/2010 1:52 PM, Doug Coats wrote:
With the WINS data cleared. for the past 20 min. (I did it before I wrote about it) Neither PDC has reported to WINS. So no wonder my PC's can't find their domain. So how do I make sure that 192.168.6.1 is added to wins.dat. I could do it manually but I would rather it communicate the way that it was intended to just so I know that the network is configured and working correctly.
Is the wins server address configured in the PDCs? I thought the way this was supposed to work was that the master browsers on each subnet would update their addresses to the wins server - and that a pdc would always be the master browser on its subnet. If the wins address is configured, are there firewalls between them?
On Thu, 2010-07-08 at 13:52 -0500, Doug Coats wrote:
With the WINS data cleared. for the past 20 min. (I did it before I wrote about it) Neither PDC has reported to WINS. So no wonder my PC's can't find their domain.
So how do I make sure that 192.168.6.1 is added to wins.dat. I could do it manually but I would rather it communicate the way that it was intended to just so I know that the network is configured and working correctly.
---- the truth is you can't if the PDC's do not have an interface on 192.168.6 network - you can create static entries in WINS files on each hosts but that defeats the purpose. You can however, distribute NETBIOS server information via DHCP.
What you really want is a WINS server on each subnet. If it's workstation professional, you might be able to install WINS on one of them if you don't have any samba server on that particular subnet.
Craig
I just did a checkconfig on the PDC in question 192.168.6.1. And I noticed something that might be nothing but it puzzles me. The nmb service is set to "off" at all run levels. If I check the nmb status it says that it is stopped. Doesn't Samba need that for net-bios support? I am probably showing my ignorace here but what is the connection between net-bios names and WINS?
On Thu, 2010-07-08 at 14:36 -0500, Doug Coats wrote:
I just did a checkconfig on the PDC in question 192.168.6.1. And I noticed something that might be nothing but it puzzles me. The nmb service is set to "off" at all run levels. If I check the nmb status it says that it is stopped. Doesn't Samba need that for net-bios support? I am probably showing my ignorace here but what is the connection between net-bios names and WINS?
---- man nmbd
it has EVERYTHING to do with netbios
Craig
On Thu, 2010-07-08 at 14:36 -0500, Doug Coats wrote:
I just did a checkconfig on the PDC in question 192.168.6.1. And I noticed something that might be nothing but it puzzles me. The nmb service is set to "off" at all run levels. If I check the nmb status it says that it is stopped. Doesn't Samba need that for net-bios support? I am probably showing my ignorace here but what is the connection between net-bios names and WINS?
--- i need to come and PULL YOUR HAIR OUT I not being an asshole but we have what is call "man" to find info on various applications including samba.
man nmbd
John
On 7/8/2010 2:36 PM, Doug Coats wrote:
I just did a checkconfig on the PDC in question 192.168.6.1. And I noticed something that might be nothing but it puzzles me. The nmb service is set to "off" at all run levels. If I check the nmb status it says that it is stopped. Doesn't Samba need that for net-bios support? I am probably showing my ignorace here but what is the connection between net-bios names and WINS?
Netbios can use multiple network transports, some of which only have broadcasts to support name resolution. Each subnet will elect a master browser to collect the names and respond to queries. As an extension for the IP protocol which is routeable, the WINS service accepts the lists from multiple master browsers at a pre-configured IP address. For it to work, the master browser that happens to be elected on any subnet must be configured to use the same WINS address and must have IP protocol working - and the clients need the address to query as part of their configuration, either from DHCP or manually entered if they have a static IP.
Netbios can use multiple network transports, some of which only have broadcasts to support name resolution. Each subnet will elect a master browser to collect the names and respond to queries. As an extension for the IP protocol which is routeable, the WINS service accepts the lists from multiple master browsers at a pre-configured IP address. For it to work, the master browser that happens to be elected on any subnet must be configured to use the same WINS address and must have IP protocol working - and the clients need the address to query as part of their configuration, either from DHCP or manually entered if they have a static IP.
-- Les Mikesell lesmikesell@gmail.com
Thank you Les for not killing me off like some of the other people who have been trying to help.
As a response to others, YES, I should have read the man but I might have posed the question all the same. Sometimes my eyes glaze over after about he 3rd sentence when trying to make sense of them.
I turned on nmb and that solved my problem.
Sometimes my life serves as a warning to others and now all they have to do is read my posts and learn from my mistakes.
Thanks for your patience!!!!
On Thu, 2010-07-08 at 13:43 -0500, Les Mikesell wrote:
On 7/8/2010 1:15 PM, Craig White wrote:
a 'network' is 192.168.x assuming that you are using class C subnet masks (255.255.255.0) and so you should have a WINS server on EACH network (192.168.4, 192.168.5, 192.168.6, etc.)
I thought the point of WINS was to have a single address that would collate the names/addresses from all your networks.
The important thing is to get the WINS working on EACH network. It's also easiest to have your PDC be the WINS server - period.
But PDC's aren't limited to one subnet either.
---- WINS is a broadcast based protocol and thus it only works on the local network and each subnet/network MUST necessarily have master browser elections. The WINS server on each subnet would serve as a clearing house for name resolution for each subnet/network. That is clearly not working for him just from that error message.
Samba machines are not limited to one subnet either by multiple network addresses or via routers but their ability to identify their presence on other subnets/networks is limited at best (remote announce).
The concept was that computers just find each other on a subnet via network browsing. When you have a server involved, you want to 'rig' the browser elections so you have entirely predictable location for retrieving the current workgroup members instead of the haphazard method employed by default. This means you put a WINS server on each subnet and specifically instruct each client (whether a Windows workstation or a samba server) to specifically interrogate that WINS server for the latest browse list.
Craig
On 7/8/2010 2:12 PM, Craig White wrote:
I thought the point of WINS was to have a single address that would collate the names/addresses from all your networks.
The important thing is to get the WINS working on EACH network. It's also easiest to have your PDC be the WINS server - period.
But PDC's aren't limited to one subnet either.
WINS is a broadcast based protocol and thus it only works on the local network and each subnet/network MUST necessarily have master browser elections. The WINS server on each subnet would serve as a clearing house for name resolution for each subnet/network. That is clearly not working for him just from that error message.
Errr, no. WINS is a server at a specified and routable IP address where the subnet master browsers send their lists periodically. Normally you'd have your DHCP server hand out the wins server address and manually configure it on machines with static IPs. The point of using WINS is to have one server that knows all of your windows name/address mappings.
Samba machines are not limited to one subnet either by multiple network addresses or via routers but their ability to identify their presence on other subnets/networks is limited at best (remote announce).
The concept was that computers just find each other on a subnet via network browsing. When you have a server involved, you want to 'rig' the browser elections so you have entirely predictable location for retrieving the current workgroup members instead of the haphazard method employed by default. This means you put a WINS server on each subnet and specifically instruct each client (whether a Windows workstation or a samba server) to specifically interrogate that WINS server for the latest browse list.
You are partly right there, but you really want to end up with one server that knows all the names, not a separate incomplete set on every subnet. How do you manage VPN connections that might be point-to-point with nothing else on the same subnet at all?
On Thu, 2010-07-08 at 14:29 -0500, Les Mikesell wrote:
WINS is a broadcast based protocol and thus it only works on the local network and each subnet/network MUST necessarily have master browser elections. The WINS server on each subnet would serve as a clearing house for name resolution for each subnet/network. That is clearly not working for him just from that error message.
Errr, no. WINS is a server at a specified and routable IP address where the subnet master browsers send their lists periodically. Normally you'd have your DHCP server hand out the wins server address and manually configure it on machines with static IPs. The point of using WINS is to have one server that knows all of your windows name/address mappings.
--- Correct and Not Correct... How about that? There really is no right or wrong in either of you twos answer. The right way is Wins on every SN to pass to the MB. That's my opinion.
DHCP is the HACKING Way to pass off wins clients. My Opinion. But his topology will require prolly a DHCP helper client because of the subnets. In essence it is a bad designed network that is the problem.
John
On 7/8/2010 2:43 PM, JohnS wrote:
WINS is a broadcast based protocol and thus it only works on the local network and each subnet/network MUST necessarily have master browser elections. The WINS server on each subnet would serve as a clearing house for name resolution for each subnet/network. That is clearly not working for him just from that error message.
Errr, no. WINS is a server at a specified and routable IP address where the subnet master browsers send their lists periodically. Normally you'd have your DHCP server hand out the wins server address and manually configure it on machines with static IPs. The point of using WINS is to have one server that knows all of your windows name/address mappings.
Correct and Not Correct... How about that? There really is no right or wrong in either of you twos answer. The right way is Wins on every SN to pass to the MB. That's my opinion.
So what do you do on a VPN connection that is configured to not be on the same subnet as any server? Or subnets where there is no windows-related service at all but you might plug in a client?
On Thu, 2010-07-08 at 14:55 -0500, Les Mikesell wrote:
Correct and Not Correct... How about that? There really is no right or wrong in either of you twos answer. The right way is Wins on every SN to pass to the MB. That's my opinion.
So what do you do on a VPN connection that is configured to not be on the same subnet as any server? Or subnets where there is no windows-related service at all but you might plug in a client?
--- And your getting at what? How does this relate to the OPs problem?
You seen to have a little knowledge of ip. So why not pass the proper routing info to the vpn client. If perhaps it was configured right the first time there would not be no what do I do now.
Windows related servvce problem? Slap a dhcp helper to pass the connections to the main dhcp server then to the wins server. It can be any Unix variant dhcp helper and server. There's two words for this: 'Network Aware". That's all it takes.
Don't make so complicated you can't control.
John
On 7/8/2010 3:11 PM, JohnS wrote:
On Thu, 2010-07-08 at 14:55 -0500, Les Mikesell wrote:
Correct and Not Correct... How about that? There really is no right or wrong in either of you twos answer. The right way is Wins on every SN to pass to the MB. That's my opinion.
So what do you do on a VPN connection that is configured to not be on the same subnet as any server? Or subnets where there is no windows-related service at all but you might plug in a client?
And your getting at what? How does this relate to the OPs problem?
I'm getting at your assertion that a Wins server on every subnet is "right" being impractical in most networks. And like the OPs problem it has to do with a windows client being able to resolve a windows name on a different subnet.
You seen to have a little knowledge of ip. So why not pass the proper routing info to the vpn client. If perhaps it was configured right the first time there would not be no what do I do now.
Windows name resolution has next to nothing to do with ip routing. If your routing works you can make windows name resolution work over it, but it isn't automatic.
Windows related servvce problem? Slap a dhcp helper to pass the connections to the main dhcp server then to the wins server. It can be any Unix variant dhcp helper and server. There's two words for this: 'Network Aware". That's all it takes.
DHCP service also doesn't have much to do with name resolution other than being able to hand out the address of the resolver.
Don't make so complicated you can't control.
Agreed, but putting a wins server on every subnet would be complicated - and unnecessary.
On Thu, 2010-07-08 at 15:31 -0500, Les Mikesell wrote:
And your getting at what? How does this relate to the OPs problem?
I'm getting at your assertion that a Wins server on every subnet is "right" being impractical in most networks. And like the OPs problem it has to do with a windows client being able to resolve a windows name on a different subnet.
Ahh yea I know that. But times you have to suffice one or the other but not both.
You seen to have a little knowledge of ip. So why not pass the proper routing info to the vpn client. If perhaps it was configured right the first time there would not be no what do I do now.
Windows name resolution has next to nothing to do with ip routing. If your routing works you can make windows name resolution work over it, but it isn't automatic.
If it does not work then it want happen as in getting routed to the wins server. You agree on that right? If routing don't work then there is no wins resolution in effect. In other words we have to know where to go.
Windows related servvce problem? Slap a dhcp helper to pass the connections to the main dhcp server then to the wins server. It can be any Unix variant dhcp helper and server. There's two words for this: 'Network Aware". That's all it takes.
DHCP service also doesn't have much to do with name resolution other than being able to hand out the address of the resolver.
lol no not much but come in needy in some situations. Pass off the wins addy indeed though.
Don't make so complicated you can't control.
Agreed, but putting a wins server on every subnet would be complicated - and unnecessary.
Yea could be a PITA. You know umm Winblows Serve, WINS Services can umm do multi SNs I do think. Now I may not me totally correct on that.
John
On 7/8/2010 4:00 PM, JohnS wrote:
Windows name resolution has next to nothing to do with ip routing. If your routing works you can make windows name resolution work over it, but it isn't automatic.
If it does not work then it want happen as in getting routed to the wins server. You agree on that right? If routing don't work then there is no wins resolution in effect. In other words we have to know where to go.
Yes, if your routing is broken or you firewall needed services between subnets, lots of things will break.
Agreed, but putting a wins server on every subnet would be complicated - and unnecessary.
Yea could be a PITA. You know umm Winblows Serve, WINS Services can umm do multi SNs I do think. Now I may not me totally correct on that.
That's the whole point of using a WINS server. If you only have or care about one subnet you can let broadcasts and the ad-hoc master browser election do their thing. Current windows versions will also use DNS for most name lookups but I don't know if you can use it to find a PDC. Active Directory sort of hides the difference between netbios and DNS names by combining them - and things get weird if don't put them on the same server.
After a little bit of research I feel a little vindicated. It seems that Samba3x seporated out nmb. On Samba 3.0 the nmb service does not show up in the chkconfig. It simply starts and stops with smb.
On Samba3x it seporates out nmb and it does not start by itself. So based on my experience I never needed to start nmb seporately so just like all of you it didn't enter my mind as the culperate.
On Thu, 2010-07-08 at 18:10 -0500, Doug Coats wrote:
After a little bit of research I feel a little vindicated. It seems that Samba3x seporated out nmb. On Samba 3.0 the nmb service does not show up in the chkconfig. It simply starts and stops with smb.
On Samba3x it seporates out nmb and it does not start by itself. So based on my experience I never needed to start nmb seporately so just like all of you it didn't enter my mind as the culperate.
---- yeah - Fedora packaging separated the 2 several releases ago and I gather that all of the new packages are now doing that but RHEL releases aren't likely to change.
I thought the name calling was rather rude/harsh and uncalled for and think you did a pretty good job of tracking down the problem.
Generally though, in your setup I would probably discourage cross subnet browse lists because they can get large and slow and generate excessive traffic. I would probably segregate student computers and teacher computers and not display teacher computers to students, etc.
Craig
On 07/08/10 1:31 PM, Les Mikesell wrote:
I'm getting at your assertion that a Wins server on every subnet is "right" being impractical in most networks. And like the OPs problem it has to do with a windows client being able to resolve a windows name on a different subnet.
I've never HEARD of using multiple wins servers, one per network segment. each SMB client can find the WINS server if you put it in the right DHCP option, or if you manually configure the client to know where the WINS server is. I've never used more than 2 of them enterprise-wide, and nowdays, you don't need WINS at all, Windows uses DNS as its primary locator service with Active Directory, and WINS is heavily deprecated.
but, this whole discussion really has nothing to do with CentOS specifically, it would better be addressed on a Samba list, I'm sure.
On Thu, 2010-07-08 at 17:07 -0700, John R Pierce wrote:
On 07/08/10 1:31 PM, Les Mikesell wrote:
I'm getting at your assertion that a Wins server on every subnet is "right" being impractical in most networks. And like the OPs problem it has to do with a windows client being able to resolve a windows name on a different subnet.
I've never HEARD of using multiple wins servers, one per network segment. each SMB client can find the WINS server if you put it in the right DHCP option, or if you manually configure the client to know where the WINS server is. I've never used more than 2 of them enterprise-wide, and nowdays, you don't need WINS at all, Windows uses DNS as its primary locator service with Active Directory, and WINS is heavily deprecated.
but, this whole discussion really has nothing to do with CentOS specifically, it would better be addressed on a Samba list, I'm sure.
---- Actually, Microsoft always recommended multiple WINS servers and using WINS replication.
I quoted the Samba documentation regarding using a separate Samba based WINS server on each subnet.
It's not that WINS is deprecated in favor of DNS but where active directory is used, it must use DNS and not WINS but a Samba 3.x server is still in a NT type Domain and WINS is the methodology.
Craig
On Thu, 2010-07-08 at 14:29 -0500, Les Mikesell wrote:
On 7/8/2010 2:12 PM, Craig White wrote:
I thought the point of WINS was to have a single address that would collate the names/addresses from all your networks.
The important thing is to get the WINS working on EACH network. It's also easiest to have your PDC be the WINS server - period.
But PDC's aren't limited to one subnet either.
WINS is a broadcast based protocol and thus it only works on the local network and each subnet/network MUST necessarily have master browser elections. The WINS server on each subnet would serve as a clearing house for name resolution for each subnet/network. That is clearly not working for him just from that error message.
Errr, no. WINS is a server at a specified and routable IP address where the subnet master browsers send their lists periodically. Normally you'd have your DHCP server hand out the wins server address and manually configure it on machines with static IPs. The point of using WINS is to have one server that knows all of your windows name/address mappings.
Samba machines are not limited to one subnet either by multiple network addresses or via routers but their ability to identify their presence on other subnets/networks is limited at best (remote announce).
The concept was that computers just find each other on a subnet via network browsing. When you have a server involved, you want to 'rig' the browser elections so you have entirely predictable location for retrieving the current workgroup members instead of the haphazard method employed by default. This means you put a WINS server on each subnet and specifically instruct each client (whether a Windows workstation or a samba server) to specifically interrogate that WINS server for the latest browse list.
You are partly right there, but you really want to end up with one server that knows all the names, not a separate incomplete set on every subnet. How do you manage VPN connections that might be point-to-point with nothing else on the same subnet at all?
---- I'm not going to argue with you but I will point out the Samba documentation that covers this...
http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/NetworkBrowsing.h...
from which I quote...
"Right now Samba WINS does not support MS-WINS replication. This means that when setting up Samba as a WINS server, there must only be one nmbd configured as a WINS server on the network. Some sites have used multiple Samba WINS servers for redundancy (one server per subnet) and then used remote browse sync and remote announce to effect browse list collation across all segments."
Craig
On Thu, 2010-07-08 at 10:50 -0700, Craig White wrote:
On Thu, 2010-07-08 at 13:44 -0400, JohnS wrote:
On Thu, 2010-07-08 at 12:03 -0500, Doug Coats wrote:
Here is the testparm -sv you requested.
For a short explaination of the IP's listed. We have two domains. One served by 192.168.6.1 and one by 192.168.5.1. I am currantly upgrading the 192.168.6. network to Windows 7. Or atleast trying. 192.168.4.1 is our gatway and the two servers listed above act as file servers and routers for their domains. I hope that makes sence.
Load smb config files from /etc/samba/smb.conf
To be truth full I think you have an out right mess going on here. One thing your smb config is 10 miles long.
Start over on a fresh install test machine and try joining the W7 machine to it. Then take your changes and merg into your current working machine config. Life will be a lot easier. One change at a time.
<snip>
His problem is WINS resolution doesn't tell the workstations which computer is the domain controller and that is what he needs to fix (first by designating a domain controller and then by making sure that WINS is functioning well).
Craig
--- Exactly why I said start at the bottom and work your way up. And another problem is I think he said he has multi netowked smbd domains? How is he routing network calls. Triangle Topology? It's best to lab learn first no matter what your experience is.
John
On 07/08/2010 05:34 PM, Doug Coats wrote: ...
Has anyone been able to get Samba3x.3.3.8 to work as a PDC?
It worked for me in a test setup I had a month ago:
Made a copy of our main CentOS 5 server, replace samba with samba3x, and I was able to join XP and W7 (with registry patch) to the domain.
The samba server was set up as a WINS server.
I think there was a problem that the default location of some of the samba files have been moved going from samba to samba3x (smbpasswd maybe?).
Mogens
-
Alexander Georgiev -
Craig White -
Doug Coats -
John R Pierce -
JohnS -
Les Mikesell -
m.roth＠5-cent.us -
Mogens Kjaer