Gerald (Jerry) Carter wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Izo wrote: | | Does this mean that the Samba is not reliable anymore ? | The smbpasswd is only part of my question. Of course | I could install it from the previous RPM, yet it would not | solve my problem at all.
I have no idea what you are talking about.
smbpasswd utility is missing in newest SuSE samba-3.0.4 patch for SuSE-9.1 distro (via online update) so I've just thought that this was for good. Adi (see previous posts from this thread) proposed to install it from wherever I could get it which, of course, I refused since it does not solve my main problem.
| I have recently upgraded from 3.0.2a to 3.0.4 and I have | just noticed that using the same smb.conf as with | previous version, the system just does not work anymore | for me ! Furthermore, smbpasswd utility appears to be dropped !
The smbpasswd utility has not changed its feature set in the 3.0.x releases. It's still there. Trust me. :-)
Well, shame on SuSE then ! If they've sc..wed up It is the second time after their last year's bogus cvs patch for SuSE-8.1 ...
| Anyway, browsing the samba docs I could only realize it | was rather outdated (it refered to samba 3.0, obviously not | to samba-3.0.4 and later), wasn't it ?
The docs apply to all 3.0.x releases. Thus they are written for the Samba 3.0 . Not a specific patch release.
PS: You need to look at the Samba server logs to figure out why the authentication is failing, not the smbclient output.
# smbclient -d3 -U me -L MYHOST (using username from domain the samba is joined into)
# tail -f /var/log/samba/log.smbd (default log level) [2004/12/10 11:47:48, 0] auth/auth_util.c:make_server_info_info3(1120) make_server_info_info3: pdb_init_sam failed!
# tail -f /var/log/samba/log.nmbd (default log level) (nothing to be logged)
(smbclient response, just for convenience)
lp_load: refreshing parameters
Initialising global parameters
params.c:pm_process() - Processing configuration file "/etc/samba/smb.conf"
Processing section "[global]"
added interface ip=172.22.110.137 bcast=172.22.255.255 nmask=255.255.0.0
added interface ip=192.168.74.1 bcast=192.168.74.255 nmask=255.255.255.0
Client started (version 3.0.2a-SUSE).
resolve_lmhosts: Attempting lmhosts lookup for name MYHOST<0x20>
resolve_wins: Attempting wins lookup for name MYHOST<0x20>
resolve_wins: using WINS server 172.22.0.8 and tag '*'
Got a positive name query response from 172.22.0.8 ( 192.168.74.1 172.22.110.137 )
Connecting to 172.22.110.137 at port 139
Password:
Doing spnego session setup (blob length=58)
got OID=1 3 6 1 4 1 311 2 2 10
got principal=NONE
Got challenge flags:
Got NTLMSSP neg_flags=0x60890215
NTLMSSP: Set final flags:
Got NTLMSSP neg_flags=0x60080215
NTLMSSP Sign/Seal - Initialising with flags:
Got NTLMSSP neg_flags=0x60080215
SPENGO login failed: Logon failure
session setup failed: NT_STATUS_LOGON_FAILURE
I succedeed to log-on to MYHOST using local password using extended user description: MYHOST/me_local
I succeeded to log-on to MYHOST using the pasword from the domain that my samba is not joined into but is replicating the authentication to/from the domain my samba isjoined into.
Let me point out again that the same smb.conf and passwd files worked just fine with the 3.0.2a samba version.
Izo -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
