I have a Linux fileserver serving up /home for linux and windows users. I was able to connect from my windows client, but not from a DC. Then suddenly I could connect from the DC too.
The linux servers run Centrify clients, and as such are part of the domain. All on same subnet.
This is what the the log.smbd says, repeatedly:
[2010/02/11 11:25:57, 0] lib/util_sock.c:read_data(534) read_data: read failure for 4 bytes to client 192.168.200.3. Error = Connection reset by peer
On Windows it appeared as an "unknown error". EDIT: the error code is "0x80004005".
We are developing a system depended on the samba share, and are worried this will appear again. It would be nice to pin point the root of this.
Any ideas what this might be? Places to look?
[Can't seem to add comment, so am creating a new answer]
Erk. Changing the port to TCP 139 is a fudge. All this is doing is forcing the client to use legacy NetBIOS over TCP/IP (NBT), as opposed to pucker SMB running on TCP 445. Like Dave suggests, check the version of Samba running, and update if poss. Also, check you Windows version on the DC, as Win2k8 R2+ (and possibly R1) require SMB signing by default. This can be turned off, but again, it's another fudge.
I would blame 'peer', he is the one who reset your connection. There seem to be a lot of theories as to why this problem happens, and how to resolve it.
smb.conf [global] smb ports = 139
Not sure what version you run, but other sites suggested that recent versions of samba resolve this problem.
User contributions licensed under CC BY-SA 3.0