RE: [Samba] PDC connect problem
First simplify your smb.conf file so you can elimanate anything else that may conflict. Start with the bare minimum needed for a pdc. Try adding wins support = yes to have it act as a wins server. Hope this helps. -Original Message- From: [EMAIL PROTECTED] [mailto:samba-admin;lists.samba.org]On Behalf Of Richard Fox Sent: Thursday, October 31, 2002 11:32 AM To: [EMAIL PROTECTED] Subject: [Samba] PDC connect problem This is my second attempt to get some help.. maybe my first post was too complex, so I will simplify it and if you need more information you will ask me. I am quite stuck so I would really appreciate some help. I am trying to connect an NT box, mercury, to a RedHat 7.3 PDC, thor. When I try to logon to the domain from mercury I get an error msg on my NT box which says the domain controller for this domain cannot be located. My smb.conf global section is: [global] workgroup = MYGROUP netbios name = THOR server string = Samba PDC %v %h max log size = 50 security = user smb passwd file = /etc/samba/smbpasswd encrypt passwords = Yes unix password sync = yes passwd program = /usr/bin/passwd %u passwd chat = *New*password* %n\n *Please*retype*new*password* %n\n *password*successfully*updated* os level = 65 domain master = yes preferred master = yes domain logons = yes logon home = \\%L\%u logon drive = H: logon script = netlogon.bat logon path = \\%L\Profiles\%u hosts allow = 192.168.1., 127. Mercury and thor are on their own private network, all other machines here are on 192.168.0. I cannot pinpoint the problem. When I try to log in from mercury, the samba log files on thor do not even register the attempt. It should be something simple, but I have been tweaking for 3 days and no success Help! -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] PDC connect problem
On Thursday 31 October 2002 4:31 pm, Richard Fox wrote: This is my second attempt to get some help.. maybe my first post was too complex, so I will simplify it and if you need more information you will ask me. I am quite stuck so I would really appreciate some help. I am trying to connect an NT box, mercury, to a RedHat 7.3 PDC, thor. When I try to logon to the domain from mercury I get an error msg on my NT box which says the domain controller for this domain cannot be located. My smb.conf global section is: ... Help! If this is a multi-homed machine then you might try interfaces = xxx.xxx.xxx.xxx bind interfaces only = yes I only guess at this because your other internal network is 192.168.0.1 and you are only allowing 192.168.1. Which makes me think that maybe your machine has two interfaces and samba's trying to bind to both. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] PDC connect problem
If this is a multi-homed machine then you might try interfaces = xxx.xxx.xxx.xxx bind interfaces only = yes I tried this an it had no effect on the problem, which is that the domain controller for this domain cannot be located. In order to eliminate any possible problem of multiple networks I deleted the other network device, eth1, which was inactive anyway, from my PDC machine. Also all other hosts on the 192.168.0. network have been removed from my /etc/hosts file. Now I just have eth0 set to 192.168.1.10 and localhost, thor (RH 7.3 PDC) , and mercury 192.168.1.7 (NT) in my /etc/hosts. I also tried wins support = yes and this also had no effect. I do believe, from what I have read, that I have a minimal smb.conf file for a PDC. Here it is again: [global] workgroup = MYGROUP netbios name = THOR os level = 64 domain master = yes preferred master = yes local master = yes security = user encrypt passwords = yes domain logons = yes logon path = \\%L\Profiles\%u logon drive = H: logon home = \\%L\%u logon script = netlogon.bat [homes] comment = Home Directories path = %H writeable = Yes valid users = %S create mode = 0664 directory mode = 0775 [netlogon] comment = Network Logon Services path = /home/samba/netlogon read only = yes # list of all possible users who I could imagine would try to connect during testing. # All have samba passwords = Unix passwords (or NT in case of Administrator) write list = Administrator, rfox, root [Profiles] path = /home/samba/profiles browseable = No I am very surprised that the log file shows no attempt to connect when I try to join the domain MYGROUP from mercury. The log file does show that samba initialized ok and is waiting for connections. I don't know how to simplify things any further. My network is 2 machines only, no additional interfaces. I did remove the DNS server IPs and gateway IP from mercury's TCP/IP settings but this also made no difference so I put them back. Keep these ideas coming, I am completely stumped. Thanks, Rich -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] PDC connect problem
This is all you should need for a bare minimum PDC to work. [global] domain logons = yes domain master = yes security = user workgroup = YOURDOMAIN encrypt passwords = yes [netlogon] path=/usr/local/netlogon writeable = no guest ok = no Make sure netlogon directory exists and then run the tesparm utility with this config. -Original Message- From: [EMAIL PROTECTED] [mailto:samba-admin;lists.samba.org]On Behalf Of Richard Fox Sent: Thursday, October 31, 2002 2:14 PM To: [EMAIL PROTECTED] Subject: Re: [Samba] PDC connect problem If this is a multi-homed machine then you might try interfaces = xxx.xxx.xxx.xxx bind interfaces only = yes I tried this an it had no effect on the problem, which is that the domain controller for this domain cannot be located. In order to eliminate any possible problem of multiple networks I deleted the other network device, eth1, which was inactive anyway, from my PDC machine. Also all other hosts on the 192.168.0. network have been removed from my /etc/hosts file. Now I just have eth0 set to 192.168.1.10 and localhost, thor (RH 7.3 PDC) , and mercury 192.168.1.7 (NT) in my /etc/hosts. I also tried wins support = yes and this also had no effect. I do believe, from what I have read, that I have a minimal smb.conf file for a PDC. Here it is again: [global] workgroup = MYGROUP netbios name = THOR os level = 64 domain master = yes preferred master = yes local master = yes security = user encrypt passwords = yes domain logons = yes logon path = \\%L\Profiles\%u logon drive = H: logon home = \\%L\%u logon script = netlogon.bat [homes] comment = Home Directories path = %H writeable = Yes valid users = %S create mode = 0664 directory mode = 0775 [netlogon] comment = Network Logon Services path = /home/samba/netlogon read only = yes # list of all possible users who I could imagine would try to connect during testing. # All have samba passwords = Unix passwords (or NT in case of Administrator) write list = Administrator, rfox, root [Profiles] path = /home/samba/profiles browseable = No I am very surprised that the log file shows no attempt to connect when I try to join the domain MYGROUP from mercury. The log file does show that samba initialized ok and is waiting for connections. I don't know how to simplify things any further. My network is 2 machines only, no additional interfaces. I did remove the DNS server IPs and gateway IP from mercury's TCP/IP settings but this also made no difference so I put them back. Keep these ideas coming, I am completely stumped. Thanks, Rich -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] PDC connect problem: II
This is all you should need for a bare minimum PDC to work. snip I tried this, it didn't work, I then found out about DIAGNOSTICS.txt in the samba distribution and started going through it step by step. I failed Step 5, which reads: TEST 5: --- run the command nmblookup -B ACLIENT '*' You should get the PCs IP address back. If you don't then the client software on the PC isn't installed correctly, or isn't started, or you got the name of the PC wrong. If ACLIENT doesn't resolve via DNS then use the IP address of the client in the above test. * When I run nmblookup -B mercury '*' I get: [rootthor etc]# nmblookup -B MERCURY '*' querying * on 192.168.1.7 name_query failed to find name * The address to mercury is resolved fine, but the lookup failed. This means that the TCP/IP setup on the mercury NT box is wrong, no? Any ideas what this could be? -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
