Hi, after a system upgrade (11.1 -> 11.2) all start ok on the server,
but the xp clients don’t start session, any suggestion?
VampirD
No in elenath hîlar nan hâd gîn
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
the server start ok and seems that the upgrade was all ok, but if I try
to login on a XP workstation it report that the server is down, the
machine password is wrong or the user is not valid
VampirD
Microsoft Windows is like air conditioning
Stops working when you open a window.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
Ok with the basics?
Have you checked to see if /etc/samba/smb.conf has changed, ie, /etc/samba/smb.conf.rpmnew, or /etc/samba/smb.conf.old?
How about the /etc/hosts* have they changed?
How about the server IP address, if its dynamically assigned and picked up a new IP addr?
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi, after a system upgrade (11.1 → 11.2) all start ok on the server,
> but the xp clients don’t start session, any suggestion?
>
> - –
> VampirD
> No in elenath hîlar nan hâd gîn
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.12 (GNU/Linux)
> Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkw539IACgkQJQ+0ABWtaVm/sACgpnh3rpQAzDLQLvGVxLS+OwSR
> qZAAnRHr8j1H9NbUIFA5WMfrx9uMyqf0
> =hpQP
> -----END PGP SIGNATURE-----
VampirD;
Did you do a fresh install or an update? A couple of things could have gone
wrong.
Here are some that jump to mind.
If you did a fresh install, then most likely, (certainly), you blew away the
old /etc/samba/secrets.tdb. In this case the domain SID would have changed
and you will need to rejoin the domain or restore the old SID. Did you save
the SID?
Starting with Samba 3.4.0 the default “passdb backend” changed from smbpasswd
to tdbsam. If you were using the default with 11.1 and just did an upgrade
you will need to set the backend back to smbpasswd. If you did a fresh
install you will need to redo all the joins and user passwds. If you are
using LDAP see the above paragraph.
All so check that the firewall is allowing both the Samba Server and Netbios
Server through.
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
> VampirD;
> Did you do a fresh install or an update? A couple of things could have gone
> wrong.
It was a upgrade, not fresh install of the entire system
> If you did a fresh install, then most likely, (certainly), you blew away the
> old /etc/samba/secrets.tdb. In this case the domain SID would have changed
> and you will need to rejoin the domain or restore the old SID. Did you save
> the SID?
There is a /etc backup, so the content of the /etc/samba directory must
be there
> Starting with Samba 3.4.0 the default “passdb backend” changed from smbpasswd
> to tdbsam. If you were using the default with 11.1 and just did an upgrade
> you will need to set the backend back to smbpasswd. If you did a fresh
> install you will need to redo all the joins and user passwds. If you are
> using LDAP see the above paragraph.
mmmmm… I’ll check that, but now I don’t have access to the server
> All so check that the firewall is allowing both the Samba Server and Netbios
> Server through.
Firewall is ok, and I can access the samba shares from the xp
administrator account
VampirD
Microsoft Windows is like air conditioning
Stops working when you open a window.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>> VampirD;
>> Did you do a fresh install or an update? A couple of things could have
gone
<snip>
>
>> Starting with Samba 3.4.0 the default “passdb backend” changed from
smbpasswd
>> to tdbsam. If you were using the default with 11.1 and just did an
upgrade
>> you will need to set the backend back to smbpasswd. If you did a fresh
>> install you will need to redo all the joins and user passwds. If you are
>> using LDAP see the above paragraph.
> mmmmm… I’ll check that, but now I don’t have access to the server
>
<snip>
>
> - –
> VampirD
>
> Microsoft Windows is like air conditioning
> Stops working when you open a window.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.12 (GNU/Linux)
> Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkw6V78ACgkQJQ+0ABWtaVnSOQCgi8fxFehzN4M7UQ0LGIyebzeD
> kDEAnR27vDwkHrvX1/0OYwiNEhNLGZ/7
> =JUVi
> -----END PGP SIGNATURE-----
VampirD;
If your 11.1 smb.conf did not specify the “passdb backend”, then most
certainly it was smbpasswd. You can check the current value of that
parameter with:
testparm -vs | grep passdb
This will show the current value of the parameter, including any default.
If you decide to just convert to the tdb backend you can export your current
smbpasswd file to tdbsam. First set the passdb backend parameter to
smbpasswd in /etc/samba/smb.conf.
passdb backend = smbpasswd
Restart smbd. Then execute with root authority:
pdbedit -i smbpasswd -e tdbsam
Let Samba revert to tdbsam ( just remove the passdb backend parameter and
restart smbd.
For a Domain tdbsam is much superior than smbpasswd and allows a lot more
control over user accounts.
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
and working, at least report connectes users, I’ll test it well later
when I can reach the server, and later try to change to tdbsam
VampirD
Microsoft Windows is like air conditioning
Stops working when you open a window.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
VampirD
No in elenath hîlar nan hâd gîn
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> all working ok now
>
> - –
> VampirD
> No in elenath hîlar nan hâd gîn
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.12 (GNU/Linux)
> Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkw7jMMACgkQJQ+0ABWtaVlKVwCgqyPXFljt6uRi0XUNConS0x30
> U1oAoKj1sxGGyicXOta3nG0QlmNx7+xx
> =7jSa
> -----END PGP SIGNATURE-----
VampirD;
Glad to see you have it working now. If you ever do a fresh install or change
PDC’s you will need to restore your existing domain SID. It’s easiest to get
from a running PDC. I would recommend that you execute the following
command:
net getlocalsid <your domain>
If you redirect the output to a text file and back that up, then if needed you
can restore the sid on a new PDC with:
net setlocalsid <your domain sid>
–
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
Ok, thanks again PV, I’ll write that to remember it.
VampirD
No in elenath hîlar nan hâd gîn
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/