I have a Xserve running Server 10.4.6 – The machine is running DNS, is an OD master and a Standalone Windows server (WorkGroup master)
We are sharing one directory via SMB to approx 50 windows users in an existing windows network
The windows users are losing connections or cannot connect
I am having problems with the windows services stopping with
Got SIGTERM: going down… (in log.nmbd)
and in log.smbd
[2006/08/23 10:47:31, 0] /SourceCache/samba/samba-92.19/samba/source/smbd/service.c:make_connection_snum(620)
‘/tmp’ does not exist or is not a directory, when connecting to [IPC$]
[2006/08/23 10:49:32, 0] /SourceCache/samba/samba-92.19/samba/source/lib/util_sock.c:get_peer_addr(1016)
getpeername failed. Error was Socket is not connected
[2006/08/23 10:49:32, 0] /SourceCache/samba/samba-92.19/samba/source/lib/util_sock.c:get_peer_addr(1016)
getpeername failed. Error was Socket is not connected
[2006/08/23 10:49:32, 0] /SourceCache/samba/samba-92.19/samba/source/lib/util_sock.c:write_socket_data(446)
write_socket_data: write failure. Error = Broken pipe
[2006/08/23 10:49:32, 0] /SourceCache/samba/samba-92.19/samba/source/lib/util_sock.c:write_socket(471)
write_socket: Error writing 4 bytes to socket 23: ERRNO = Broken pipe
[2006/08/23 10:49:32, 0] /SourceCache/samba/samba-92.19/samba/source/lib/util_sock.c:send_smb(663)
Error writing 4 bytes to client. -1. (Broken pipe)
Does anyone have any pointers or fixes as this is now becoming tiresome
Is it a PDC? To be honest I don’t trust more the 40-50 connected windows users at a time, seems to be all that one server can handle. Now I have seen where deleting the secrets.tdb file from “/var/db/samba/” and rebooting and setting up the PDC again, resolved some windows connectivity issues. Its really hard to say if this would work for your situation.
So clients are auth to a AD server and then are manually connecting to your OSX server and using another password? Or do you have your OSX server bound to AD server and clients are using the same login and password?
If it is bound to AD why not make it a Member Server of the AD server and part of Kerberos, if the server is not bound to AD it should be.
Comments are closed