SMB : creds_server_check failed, broken pipe errors

[fleecy]

XServe Intel Quad 2.8 GHz, Leopard Server 10.5.4, 4 GB RAM, Linksys Gigabit Ethernet network 24 port switch

I have setup this server to work as an OD Master and Windows PDC for the network. There are about 10 clients on the network, all new iMacs running 10.5.4 with network home directories. The only 3rd party software running here is Kerio MailServer 6.5.2, BTW.

The Mac side is running nice and fast, but I can’t say as much for the Windows side of things.

The said Macs all have a local Parallels Windows XP install. XP SP3 (with latest updates applied) is setup to authenticate to Leopard Server and is attached to the SAMBA PDC’s domain. Clients use the same account/password info to login on XP as they do on their Macs.

It’s all been working rather decently for about 2 months now, but yesterday morning none of the Windows clients could login.

Turns out that Leopard Server’s config for SMB was completely reset to factory defaults, out of nowhere. Is this normal?

Also, the SMB File Service Log has been littered with errors such as these for the past few days :

[2008/09/15 17:21:43, 0, pid=31963] /SourceCache/samba/samba-187.7/samba/source/rpc_server/srv_netlog_nt.c:_net_auth_2(527)
_net_auth2: creds_server_check failed. Rejecting auth request from client PC-102 machine account PC-102$
[2008/09/15 17:21:59, 0, pid=31987] /SourceCache/samba/samba-187.7/samba/source/lib/util_sock.c:set_socket_options(261)
Failed to set socket option SO_KEEPALIVE (Error Invalid argument)
[2008/09/15 17:21:59, 0, pid=31987] /SourceCache/samba/samba-187.7/samba/source/lib/util_sock.c:set_socket_options(261)
Failed to set socket option TCP_NODELAY (Error Invalid argument)
[2008/09/15 17:21:59, 0, pid=31987] /SourceCache/samba/samba-187.7/samba/source/lib/util_sock.c:get_peer_addr(1224)
getpeername failed. Error was Invalid argument
[2008/09/15 17:21:59, 0, pid=31987] /SourceCache/samba/samba-187.7/samba/source/lib/util_sock.c:write_data(562)
write_data: write failure in writing to client 192.168.2.122. Error Broken pipe
[2008/09/15 17:21:59, 0, pid=31987] /SourceCache/samba/samba-187.7/samba/source/lib/util_sock.c:send_smb(761)
Error writing 4 bytes to client. -1. (Broken pipe)
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.

[Author]

Posts