Newsroom Update

Beginning in May, a special Today at Apple series titled “Made for Business” will offer small business owners and entrepreneurs free opportunities to learn how Apple products and services can support their growth and success. Learn more >

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

User profile for user: Blutech
Blutech Author
User level: Level 1
0 points

Samba Errors

I am stuck, please help!

I have a PC running Windows XP Professional Media Center. It has been connected to the network for about a year. No update to the server has been done since 8/4/07 and this service stopped working correctly last week. Our mapped network drives are no longer accessible. I have confirmed that all the setting are correct with the PC and with the Windows Service on the Mac XServe. While looking into the log files for the Windows Service I noticed these entries:

[2007/08/23 18:36:54, 0] pdb ods.c:odssamgetsampwnam(2329)
odssam_getsampwnam: [0]get sam_recordattributes dsRecTypeStandard:Users no account for 'BLUFISHDESIGN'!
[2007/08/23 18:46:22, 0] /SourceCache/samba/samba-100.9/samba/source/lib/util sock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/08/23 18:46:22, 0] /SourceCache/samba/samba-100.9/samba/source/lib/util sock.c:write_socketdata(446)
write socketdata: write failure. Error = Broken pipe
[2007/08/23 18:46:22, 0] /SourceCache/samba/samba-100.9/samba/source/lib/util sock.c:writesocket(471)
write_socket: Error writing 4 bytes to socket 6: ERRNO = Broken pipe
[2007/08/23 18:46:22, 0] /SourceCache/samba/samba-100.9/samba/source/lib/util sock.c:sendsmb(663)
Error writing 4 bytes to client. -1. (Broken pipe)
[2007/08/23 19:22:36, 0] /SourceCache/samba/samba-100.9/samba/source/lib/util sock.c:read_socketdata(400)
read socketdata: recv failure for 4. Error = Connection reset by peer
[2007/08/23 19:28:39, 0] /SourceCache/samba/samba-100.9/samba/source/lib/util sock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/08/23 19:28:39, 0] /SourceCache/samba/samba-100.9/samba/source/lib/util sock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/08/23 19:28:39, 0] /SourceCache/samba/samba-100.9/samba/source/lib/util sock.c:write_socketdata(446)
write socketdata: write failure. Error = Broken pipe
[2007/08/23 19:28:39, 0] /SourceCache/samba/samba-100.9/samba/source/lib/util sock.c:writesocket(471)
write_socket: Error writing 4 bytes to socket 23: ERRNO = Broken pipe
[2007/08/23 19:28:39, 0] /SourceCache/samba/samba-100.9/samba/source/lib/util sock.c:sendsmb(663)
Error writing 4 bytes to client. -1. (Broken pipe)
[2007/08/24 10:50:46, 1] /SourceCache/samba/samba-100.9/samba/source/smbd/server.c:open socketssmbd(359)
Reloading services after SIGHUP
[2007/08/24 10:59:40, 0] /SourceCache/samba/samba-100.9/samba/source/lib/util sock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/08/24 10:59:40, 0] /SourceCache/samba/samba-100.9/samba/source/lib/util sock.c:write_socketdata(446)
write socketdata: write failure. Error = Broken pipe
[2007/08/24 10:59:40, 0] /SourceCache/samba/samba-100.9/samba/source/lib/util sock.c:writesocket(471)
write_socket: Error writing 4 bytes to socket 6: ERRNO = Broken pipe
[2007/08/24 10:59:40, 0] /SourceCache/samba/samba-100.9/samba/source/lib/util sock.c:sendsmb(663)
Error writing 4 bytes to client. -1. (Broken pipe)
[2007/08/24 11:32:24, 0] /SourceCache/samba/samba-100.9/samba/source/lib/util sock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/08/24 11:32:24, 0] /SourceCache/samba/samba-100.9/samba/source/lib/util sock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/08/24 11:32:24, 0] /SourceCache/samba/samba-100.9/samba/source/lib/util sock.c:write_socketdata(446)
write socketdata: write failure. Error = Broken pipe
[2007/08/24 11:32:24, 0] /SourceCache/samba/samba-100.9/samba/source/lib/util sock.c:writesocket(471)
write_socket: Error writing 4 bytes to socket 23: ERRNO = Broken pipe
[2007/08/24 11:32:24, 0] /SourceCache/samba/samba-100.9/samba/source/lib/util sock.c:sendsmb(663)
Error writing 4 bytes to client. -1. (Broken pipe)
[2007/08/24 12:04:59, 0] /SourceCache/samba/samba-100.9/samba/source/lib/util sock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/08/24 12:04:59, 0] /SourceCache/samba/samba-100.9/samba/source/lib/util sock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/08/24 12:04:59, 0] /SourceCache/samba/samba-100.9/samba/source/lib/util sock.c:write_socketdata(446)
write socketdata: write failure. Error = Broken pipe
[2007/08/24 12:04:59, 0] /SourceCache/samba/samba-100.9/samba/source/lib/util sock.c:writesocket(471)
write_socket: Error writing 4 bytes to socket 6: ERRNO = Broken pipe
[2007/08/24 12:04:59, 0] /SourceCache/samba/samba-100.9/samba/source/lib/util sock.c:sendsmb(663)
Error writing 4 bytes to client. -1. (Broken pipe)

XServe G5, Mac OS X (10.4.10), XServe RAID 5

Posted on Aug 24, 2007 12:20 PM

Reply
5 replies
User profile for user: jmca
jmca
User level: Level 2
160 points

Sep 10, 2007 11:39 PM in response to Blutech

I'm getting these errors too:

[2007/09/11 00:10:22, 0]
/SourceCache/samba/samba-92.9/samba/source/lib/util sock.c:sendsmb(663)
Error writing 4 bytes to client. -1. (Broken pipe)
[2007/09/11 00:10:22, 0]
/SourceCache/samba/samba-92.9/samba/source/lib/util sock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/09/11 00:10:22, 0]
/SourceCache/samba/samba-92.9/samba/source/lib/util sock.c:write_socketdata(446)
write socketdata: write failure. Error = Broken pipe
[2007/09/11 00:10:22, 0]
/SourceCache/samba/samba-92.9/samba/source/lib/util sock.c:writesocket(471)
write_socket: Error writing 4 bytes to socket 23: ERRNO = Broken pipe

Have no idea what is causing them. I have 4 Windows XP clients connecting to an XServe. Performance was soo slow that I reinstalled everything. Performance is better but these errors have me worried.

Funny thing is that AFP and NFS are both working great.

Please keep this thread alive....
Reply
User profile for user: jmca
jmca
User level: Level 2
160 points

Sep 12, 2007 11:38 PM in response to Blutech

I was unable to resolve the errors. I did a complete reinstall of the OS and that helped my speed issues but I'm still seeing a lot of broken pipes in the Samba log. One post suggested editing the samba.conf file global section and adding keepAlive = 0. I tried that but it didn't help.

I think this has something to do with the way the windows clients are authenticating but I don't know what. I have the server set up as a stand alone windows server, only responsible for the workgroup. I wonder if XP Professional is trying to authenticate to the domain, which I believe uses kerberos. The client fails on it's first method of authentication generating a few broken pipe sockets and then succeeds on it's second attempt to authenticate. This makes opening files write a lot of errors to the log because lookupd is constantly checking permissions...

That's the theory. I'm not on that site anymore and I won't be back unless the speed goes down. I'm still curious what is causing these errors.
Reply

Samba Errors

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.
Learn more Sign up