We've found a solution for this and it turns out to be a setting at the Windows end:
If you add the value AllowGuestAuthWhenSigningRequired = 1 to the registry key HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanWorkstation\Param eters and then reboot the machine it all seems to work. Apparently this is new behaviour in Windows 2008: http://social.msdn.microsoft.com/Forums/en/os_fileservices/thread/832d395b-6 e6f-4658-8dbb-120138a4cd7c David -----Original Message----- From: Jeremy Allison [mailto:[email protected]] Sent: 15 December 2011 18:06 To: Hilton, David Cc: Jeremy Allison; [email protected] Subject: Re: [Samba] "getpeername failed" error when signed communications policy enabled On Thu, Dec 15, 2011 at 09:10:11AM +0000, Hilton, David wrote: > No, the only error that we see is the "getpeername failed" error in the Samba log for the client machine that is trying to print the job. Then I doubt it's a signing issue (which makes it strange). What does a debug level 10 say ? Jeremy.
smime.p7s
Description: S/MIME cryptographic signature
-- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
