Saturday, March 23, 2019

Windows/Samba connection error

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?

No comments:

Post a Comment

linux - How to SSH to ec2 instance in VPC private subnet via NAT server

I have created a VPC in aws with a public subnet and a private subnet. The private subnet does not have direct access to external network. S...