Why do I keep seeing the error message 'lib/util_sock.c:get_peer_addr(1000) getpeername failed. Error was Transport endpoint is not connected (0.0.0.0)' in my Samba logs and what does it mean?

Solution Verified - Updated -

Issue

There are error messages in the /var/log/message.

Mar  7 11:59:35 hostname smbd[6280]: [2010/03/07 11:59:35, 0] lib/util_sock.c:get_peer_addr(1224)
Mar  7 11:59:35 hostname smbd[6280]:   getpeername failed. Error was Transport endpoint is not connected
Mar  7 11:59:35 hostname smbd[13882]: [2010/03/07 11:59:35, 0] lib/util_sock.c:get_peer_addr(1224)
Mar  7 11:59:35 hostname smbd[13882]:   getpeername failed. Error was Transport endpoint is not connected
Mar  7 11:59:35 hostname smbd[13882]: [2010/03/07 11:59:35, 0] lib/util_sock.c:write_data(562)
Mar  7 11:59:35 hostname smbd[13882]:   write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer
Mar  7 11:59:35 hostname smbd[13882]: [2010/03/07 11:59:35, 0] lib/util_sock.c:send_smb(761)
Mar  7 11:59:35 hostname smbd[13882]:   Error writing 4 bytes to client. -1. (Connection reset by peer)

Environment

Red Hat Enterprise Linux 4, 5 and 6

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.