Louis,
There are numerous changes (adds, deletes, and defaults) to smb.conf
between the two versions you have listed.
The one that may be causing your smbpasswd problem is the default passdb
backend has changed.
If you wish to continue using smbpasswd instead of the default tdb, you
have to explicitly declare
passdb backend = smbpasswd
Check here for changelogs: http://www.samba.org/samba/history/
Dale
On 10/06/2011 10:36 PM, Louis Kabo wrote:> Hello,
>
> having a problem upgrading a samba installation version 3.0.28 on a
> FreeBSD 7.x server. I use samba as a PDC with roaming profiles and user
> shares.
>
> I have to upgrade it to allow Windows 7 Pro workstations to join the
> domain.
>
> I was able to build the binaries sucessfully and install them, everything
> ran OK, but....
>
> I noticed that my smbpasswd file had I guess been relocated and I had to
> readd the PC's and users to the smbpasswd file (smbpasswd -a username,
> smbpassword -ma machinename), etc.
>
> I noticed that I had to have the PC's un-join and re-join the domain in
> order for them to work.
>
> I noticed that none of the local profiles loaded, instead creating a new
> roaming profile username.V2 in the profiles directory. (windows XP
> workstation continued to complain about using a local profile as the
> server copy was unavailable)
>
> In addition to this on the Windows 7 workstation I could not access the
> user share that I was logged into.
>
> So I undid my changes and went back to Samba 3.0.28 until I can figure
> these problems out.I have to figure out how not to have to re-add all of
> my users and PC's into smbpasswd, why roaming profiles wont work and
what
> the access denined problem was about.
>
> My smb.conf file did seem to translate OK because all of my shares were
> available. What am I missing, did the smbpasswd directory change? is the
> old smbpasswd file from 3.0.28 not compatible with 3.6.0? what can I do? I
> dont want everyone to have to recreate their roaming profiles... there are
> about 50 users........... permissions problem? build/source/binary
> location problem? any suggestions welcome.
>
> help please,
>
> Thanks
>
>
>