Re: [Samba] PDC broke after upgrade
On Mon, Jan 17, 2011 at 5:15 AM, Mat Enders mat.end...@gmail.com wrote: On Mon, Jan 17, 2011 at 2:24 AM, Helmut Hullen hul...@t-online.de wrote: Hallo, Mat, Du meintest am 16.01.11: I upgraded from Debian Lenny (Samba 3.2.5) to Squeeze (Samba 3.5.6) and now my PDC does not work. In the past when upgrading from one release to another all of the machine trust accounts no longer worked but I was able to just rejoin then to the domain. Now however the join fails with unknown user and bad password. I have always used root and roots password what am I missing? What changed between these 2 releases? What tells testparm -s 2/dev/null | grep passdb testparm -sv 2/dev/null | grep passdb The first line tells what is defined in the smb.conf, the second tells all pre-defined options too. Samba 3.5.6 uses tdbsam, earlier versions have used smbpasswd; you should look which file (smbpasswd or passdb.tdb) your old version has used. For converting you can use pdbedit. Viele Gruesse! Helmut -- Helmut, Danke, I will check this I am sure that is the problem as I was using smbpasswd. Will pdbedit convert my smbpasswd file to tdbsam? -- Mathew E. Enders Helmut, Or did the upgrade convert smbpasswd to tdbsam and all I need to do is change my smb.conf? -- Mathew E. Enders -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] PDC broke after upgrade
Hallo, Mat, Du meintest am 17.01.11: Samba 3.5.6 uses tdbsam, earlier versions have used smbpasswd; you should look which file (smbpasswd or passdb.tdb) your old version has used. For converting you can use pdbedit. Danke, I will check this I am sure that is the problem as I was using smbpasswd. Will pdbedit convert my smbpasswd file to tdbsam? If your distribution puts smbpasswd into /etc/samba/private: pdbedit -i smbpasswd:/etc/samba/private/smbpasswd -e tdbsam:/etc/samba/private/passdb.tdb It's a very good idea to first look into the directory and look at the timestamps of source and target file ... the pdbedit command overwrites existing files. Or did the upgrade convert smbpasswd to tdbsam and all I need to do is change my smb.conf? I can't see what has happened. Which timestamp has your smbpasswd, which timestamp has your passdb.tdb? Or do you use LDAP? Then perhaps your system wants to use the LDAP crap as password backend. You can define your special backend in the [global] part of your smb.conf. Viele Gruesse! Helmut -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] PDC broke after upgrade
Thanks Helmut I will check the time stamps later. I was using smbpasswd and that is what is called for in my smb.conf file. Sent on the Sprint® Now Network from my BlackBerry® -Original Message- From: Helmut Hullen hul...@t-online.de Sender: samba-boun...@lists.samba.org Date: 17 Jan 2011 14:56:00 To: samba@lists.samba.org Reply-To: hel...@hullen.de Subject: Re: [Samba] PDC broke after upgrade Hallo, Mat, Du meintest am 17.01.11: Samba 3.5.6 uses tdbsam, earlier versions have used smbpasswd; you should look which file (smbpasswd or passdb.tdb) your old version has used. For converting you can use pdbedit. Danke, I will check this I am sure that is the problem as I was using smbpasswd. Will pdbedit convert my smbpasswd file to tdbsam? If your distribution puts smbpasswd into /etc/samba/private: pdbedit -i smbpasswd:/etc/samba/private/smbpasswd -e tdbsam:/etc/samba/private/passdb.tdb It's a very good idea to first look into the directory and look at the timestamps of source and target file ... the pdbedit command overwrites existing files. Or did the upgrade convert smbpasswd to tdbsam and all I need to do is change my smb.conf? I can't see what has happened. Which timestamp has your smbpasswd, which timestamp has your passdb.tdb? Or do you use LDAP? Then perhaps your system wants to use the LDAP crap as password backend. You can define your special backend in the [global] part of your smb.conf. Viele Gruesse! Helmut -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] PDC broke after upgrade
On Mon, Jan 17, 2011 at 9:05 AM, mat.end...@gmail.com wrote: Thanks Helmut I will check the time stamps later. I was using smbpasswd and that is what is called for in my smb.conf file. Sent on the Sprint® Now Network from my BlackBerry® -Original Message- From: Helmut Hullen hul...@t-online.de Sender: samba-boun...@lists.samba.org Date: 17 Jan 2011 14:56:00 To: samba@lists.samba.org Reply-To: hel...@hullen.de Subject: Re: [Samba] PDC broke after upgrade Hallo, Mat, Du meintest am 17.01.11: Samba 3.5.6 uses tdbsam, earlier versions have used smbpasswd; you should look which file (smbpasswd or passdb.tdb) your old version has used. For converting you can use pdbedit. Danke, I will check this I am sure that is the problem as I was using smbpasswd. Will pdbedit convert my smbpasswd file to tdbsam? If your distribution puts smbpasswd into /etc/samba/private: pdbedit -i smbpasswd:/etc/samba/private/smbpasswd -e tdbsam:/etc/samba/private/passdb.tdb It's a very good idea to first look into the directory and look at the timestamps of source and target file ... the pdbedit command overwrites existing files. Or did the upgrade convert smbpasswd to tdbsam and all I need to do is change my smb.conf? I can't see what has happened. Which timestamp has your smbpasswd, which timestamp has your passdb.tdb? Or do you use LDAP? Then perhaps your system wants to use the LDAP crap as password backend. You can define your special backend in the [global] part of your smb.conf. Viele Gruesse! Helmut -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba All seems to be working correctly now except I have to rejoin all of the machines to the domain but that happens anytime I upgrade. Also it seems that my users no longer have thier roaming profiles. Here is a copy of my smb.conf [global] smb passwd file = /etc/samba/passdb.tdb enable privileges = yes logon drive = H: domain master = yes encrypt passwords = true logon home = \\%L\%U netbios name = ARDVARC server string = Gaudior's PDC logon script = logon.bat local master = yes workgroup = GAUACA logon path = \\%L\%U\profile os level = 99 security = user add machine script = /usr/sbin/useradd -s /bin/false \-d /dev/null %u preferred master = yes domain logons = yes hide files = /desktop.ini/ guest account = nobody map to guest = bad user wins support = yes [staff] comment = staff share drive path = /home/staff/share read only = no ;valid users = [student] comment = student share by level path = /home/stdnt/share read only = no [netlogon] comment = Net Logon Service path = /home/netlogon read only = yes write list = root ;public = yes guest ok = yes browsable = no [homes] comment = Home valid users = %S read only = no browsable = no -- Mathew E. Enders -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] PDC broke after upgrade
I upgraded from Debian Lenny (Samba 3.2.5) to Squeeze (Samba 3.5.6) and now my PDC does not work. In the past when upgrading from one release to another all of the machine trust accounts no longer worked but I was able to just rejoin then to the domain. Now however the join fails with unknown user and bad password. I have always used root and roots password what am I missing? What changed between these 2 releases? -- Mathew E. Enders -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] PDC broke after upgrade
Hallo, Mat, Du meintest am 16.01.11: I upgraded from Debian Lenny (Samba 3.2.5) to Squeeze (Samba 3.5.6) and now my PDC does not work. In the past when upgrading from one release to another all of the machine trust accounts no longer worked but I was able to just rejoin then to the domain. Now however the join fails with unknown user and bad password. I have always used root and roots password what am I missing? What changed between these 2 releases? What tells testparm -s 2/dev/null | grep passdb testparm -sv 2/dev/null | grep passdb The first line tells what is defined in the smb.conf, the second tells all pre-defined options too. Samba 3.5.6 uses tdbsam, earlier versions have used smbpasswd; you should look which file (smbpasswd or passdb.tdb) your old version has used. For converting you can use pdbedit. Viele Gruesse! Helmut -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
