Sorry for not being clear, yes I did test with the configuration you
suggested...

Here's the [global] that I just tested on your suggestion:

-bash-2.05b$ more /usr/local/samba/lib/smb.conf
[global]
#realm = ciswinnet.cis.uab.edu
workgroup=CISWINNET
#security = ADS # have also tried DOMAIN and SHARE, same results
security = USER
encrypt passwords = yes
#password server = snapper.cis.uab.edu
#client use spnego = yes
client use spnego = no

and this is what Samba is seeing....

-bash-2.05b$ /usr/local/samba/bin/testparm
Load smb config files from /usr/local/samba/lib/smb.conf
Loaded services file OK.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions
 
# Global parameters
[global]
        workgroup = CISWINNET
        client use spnego = No
-bash-2.05b$

...and the command I am running:

smbclient \\\\snapper\\dfs <password> -U Administrator -W CISWINNET -D
home -d1 -Tqca /tmp/junkme.tar

...and this fails in the exact same manner as when I tested with my
original smb.conf (basically, uncomment all the stuff I have commented
out in the smb.conf I posted above.)  Specifically, the failure looks
like this:

-bash-2.05b$ smbclient \\\\snapper\\dfs <password> -U Administrator -W
CISWINNET -D home -d1 -Tqca /tmp/junkme.tar
[2004/01/15 09:45:18, 1] client/client.c:do_connect(2597)
  Domain=[CISWINNET] OS=[Windows Server 2003 3790] Server=[Windows
Server 2003 5.2]

[this runs fine for 3 minutes and then...]


[2004/01/15 09:50:04, 1] libsmb/smb_signing.c:signing_good(205)
  signing_good: SMB signature check failed on seq 7!
[2004/01/15 09:50:04, 0] libsmb/clientgen.c:cli_receive_smb(121)
  SMB Signature verification failed on incoming packet!
[2004/01/15 09:50:04, 0] client/clitar.c:do_atar(698)
  Error reading file
\home\faculty\bryant\bryantback-brblt\Images\a2family2\100msdcf\Dsc00082.jpg : 
Server packet had invalid SMB signature!
[2004/01/15 09:50:04, 0] client/clitar.c:do_atar(733)
  Didn't get entire file. size=536462, nread=262080
[2004/01/15 09:50:04, 0] client/clitar.c:do_atar(654)
  Server packet had invalid SMB signature! opening remote file
\home\faculty\bryant\bryantback-brblt\Images\a2family2\100msdcf\D
(\home\faculty\bryant\bryantback-brblt\Images\a2family2\100msdcf\)
[2004/01/15 09:50:04, 0] client/clitar.c:do_atar(654)
  Server packet had invalid SMB signature! opening remote file
\home\faculty\bryant\bryantback-brblt\Images\a2family2\100msdcf\D
(\home\faculty\bryant\bryantback-brblt\Images\a2family2\100msdcf\)

[snip - same errors for the rest of the files/directories on the share]

Server packet had invalid SMB signature! listing \home\u\*
[2004/01/15 09:50:04, 0] client/clitar.c:process_tar(1433)
  tar: dumped 4441 files and directories
[2004/01/15 09:50:04, 0] client/clitar.c:process_tar(1434)
  Total bytes written: 755698176

I've shuffled around files on the share to see if it was a particular
file or directory causing the error but it still fails - the total byte
count is slightly different, but it's always in the neighborhood of
755-770MB or so.

Thanks,
Fran


On Thu, 2004-01-15 at 09:29, Stefan G. Weichinger wrote:
> Hi, Fran,
> 
> on Donnerstag, 15. Jänner 2004 at 16:13 you wrote to amanda-users:
> 
> FF> Wow...I see what you've pointed out in the man page.  This is what I
> FF> read in the HOWTO:
> 
> >>From the Official Samba-3 HOWTO (Section 6.6.3, page 80):
> 
> FF> "Windows 2003 requires SMB signing.  Client-side SMB signing has been
> FF> implemented in Samba 3.0.  Set client use spnego = yes when
> FF> communicating with a Windows 2003 server."
> 
> Yeah, but the chapter is called "I Can’t Join a Windows 2003 PDC".
> You didnŽt answer my question for the possibility to use a stand-alone
> Samba.
> 
> > However, it doesn't matter if it's set to yes or no, it's still broken.
> > :-(
> 
> ItŽs not clear to me if you tested both settings and both failed ...
-- 

Fran Fabrizio
Senior Systems Analyst
Department of Computer and Information Sciences
University of Alabama - Birmingham
fran AT cis.uab DOT edu
(205) 934-0653