First, our setup:
RHEL5b
BackuPC 3.0 b1
smbclient Version 3.0.23a-3
perl v5.8.8
Full backups work fine, but it appears that the password is not properly passed when connecting.
Debug level 3 for the transaction gives:
Getting files newer than Thu Sep 28 15:00:08 2006
lp_load: refreshing parameters
Initialising global parameters
params.c:pm_process() - Processing configuration file "/etc/samba/smb.conf"
Processing section "[global]"
added interface ip=10.1.25.55 bcast=10.1.255.255 nmask=255.255.0.0
Client started (version 3.0.23a-3).
Connecting to 10.205.25.2 at port 445
Doing spnego session setup (blob length=107)
got OID=1 2 840 48018 1 2 2
got OID=1 2 840 113554 1 2 2
got OID=1 2 840 113554 1 2 2 3
got OID=1 3 6 1 4 1 311 2 2 10
got [EMAIL PROTECTED]
Got challenge flags:
Got NTLMSSP neg_flags=0x62890 215
NTLMSSP: Set final flags:
Got NTLMSSP neg_flags=0x60080215
NTLMSSP Sign/Seal - Initialising with flags:
Got NTLMSSP neg_flags=0x60080215
SPNEGO login failed: Logon failure
session setup failed: NT_STATUS_LOGON_FAILURE
Connecting to 10.205.25.2 at port 445
Doing spnego session setup (blob length=107)
got OID=1 2 840 48018 1 2 2
got OID=1 2 840 113554 1 2 2
got OID=1 2 840 113554 1 2 2 3
got OID=1 3 6 1 4 1 311 2 2 10
got [EMAIL PROTECTED]
Got challenge flags:
Got NTLMSSP neg_flags=0x62890215
NTLMSSP: Set final flags:
Got NTLMSSP neg_flags=0x60080215
NTLMSSP Sign/Seal - Initialising with flags:
Got NTLMSSP neg_flags=0x60080215
SPNEGO login failed: Logon failure
session setup failed: NT_STATUS_LOGON_FAILURE
BTW, the same symptoms occur when a full backup is attempted on anything other than the root of a share (ie. if you try to specify BackupFilesOnly it will fail with NT_STATUS_LOGON_FAILURE too). I believe the system is not passing credentials properly for some reason when any parameters are added to the -T flag as is required to do BackupFilesOnly and NewerThan...
This message was rejected by the backuppc-devel list so it must be something I'm doing (although all 8 of our backuppc 2.2 servers are doing fine and have been for years)
It must be something really dumb that I'm doing. Can anyone shed any light?
--
Kevin Heneveld
Systems Administrator
Fairbanks North Star Borough School District
907-452-2000 x375
RHEL5b
BackuPC 3.0 b1
smbclient Version 3.0.23a-3
perl v5.8.8
Full backups work fine, but it appears that the password is not properly passed when connecting.
Debug level 3 for the transaction gives:
Getting files newer than Thu Sep 28 15:00:08 2006
lp_load: refreshing parameters
Initialising global parameters
params.c:pm_process() - Processing configuration file "/etc/samba/smb.conf"
Processing section "[global]"
added interface ip=10.1.25.55 bcast=10.1.255.255 nmask=255.255.0.0
Client started (version 3.0.23a-3).
Connecting to 10.205.25.2 at port 445
Doing spnego session setup (blob length=107)
got OID=1 2 840 48018 1 2 2
got OID=1 2 840 113554 1 2 2
got OID=1 2 840 113554 1 2 2 3
got OID=1 3 6 1 4 1 311 2 2 10
got [EMAIL PROTECTED]
Got challenge flags:
Got NTLMSSP neg_flags=0x62890 215
NTLMSSP: Set final flags:
Got NTLMSSP neg_flags=0x60080215
NTLMSSP Sign/Seal - Initialising with flags:
Got NTLMSSP neg_flags=0x60080215
SPNEGO login failed: Logon failure
session setup failed: NT_STATUS_LOGON_FAILURE
Connecting to 10.205.25.2 at port 445
Doing spnego session setup (blob length=107)
got OID=1 2 840 48018 1 2 2
got OID=1 2 840 113554 1 2 2
got OID=1 2 840 113554 1 2 2 3
got OID=1 3 6 1 4 1 311 2 2 10
got [EMAIL PROTECTED]
Got challenge flags:
Got NTLMSSP neg_flags=0x62890215
NTLMSSP: Set final flags:
Got NTLMSSP neg_flags=0x60080215
NTLMSSP Sign/Seal - Initialising with flags:
Got NTLMSSP neg_flags=0x60080215
SPNEGO login failed: Logon failure
session setup failed: NT_STATUS_LOGON_FAILURE
BTW, the same symptoms occur when a full backup is attempted on anything other than the root of a share (ie. if you try to specify BackupFilesOnly it will fail with NT_STATUS_LOGON_FAILURE too). I believe the system is not passing credentials properly for some reason when any parameters are added to the -T flag as is required to do BackupFilesOnly and NewerThan...
This message was rejected by the backuppc-devel list so it must be something I'm doing (although all 8 of our backuppc 2.2 servers are doing fine and have been for years)
It must be something really dumb that I'm doing. Can anyone shed any light?
--
Kevin Heneveld
Systems Administrator
Fairbanks North Star Borough School District
907-452-2000 x375
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ BackupPC-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
