I haven't seen this on-list, so apologies if it's a duplicate On Tuesday 05 February 2008 09:31:17 you wrote: > On Thursday 31 January 2008 18:12, Jeremy Allison wrote: > > On Thu, Jan 31, 2008 at 01:04:21PM +0000, Anne Wilson wrote: > > > I'm having problems connecting from my laptop, and the logs show > > > > > > lib/util_sock.c:send_smb(769) Error writing 116 bytes to client. -1. > > > (Broken pipe) : 1 Time(s) > > > lib/util_sock.c:write_data(562) write_data: write failure in writing > > > to client 192.168.0.91. Error Broken pipe : 1 Time(s) > > > libsmb/smb_signing.c:srv_check_incoming_message(737) > > > srv_check_incoming_message: BAD SIG: seq 2 wanted SMB signature of : 6 > > > Time(s) > > > libsmb/smb_signing.c:srv_check_incoming_message(741) > > > srv_check_incoming_message: BAD SIG: seq 2 got SMB signature of : 6 > > > Time(s) > > > > > > Could someone please give me some idea of where to look for the > > > problem? smb.conf looks fine, and users and groups are identical by > > > name and ID. > > > > What version of Samba are you using ? > > 3.0.25b-1.el5_1.4 > > I don't know whether it's relevant, but I had been having problems getting > my laptop to collect my korganizer from the server. I've been away for a > few days, so I haven't a long test to confirm it, but it looks as though > that has been cured by removing 'read only = no' and substituting > 'writeable = yes'. I did use the laptop last night, after returning home, > and there are no such messages in the log this morning. > I realise now that I had made a change to selinux, so that's probably what improved matters. It looks as though the old 'either way works' still holds.
Anne
pgpVDY5a4MYxF.pgp
Description: PGP signature
-- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
