I appologize if this has been answered previously or if the answer is obvious. I have done the best I could searching through the mailing list archives and through google to see if I can find an answer to my problem. With that said, the problem is that whenever I use my connection to samba (3.0.23c on FBSD 5.4) from my Windows XP (Professional, SP2) machine I receive these errors: Sep 11 09:02:59 gateway smbd[48491]: [2006/09/11 09:02:59, 0] lib/util_sock.c:get_peer_addr(1229) Sep 11 09:02:59 gateway smbd[48491]: getpeername failed. Error was Socket is not connected Sep 11 09:02:59 gateway smbd[48491]: [2006/09/11 09:02:59, 0] lib/access.c:check_access(327) Sep 11 09:02:59 gateway smbd[48491]: [2006/09/11 09:02:59, 0] lib/util_sock.c:get_peer_addr(1229) Sep 11 09:02:59 gateway smbd[48491]: getpeername failed. Error was Socket is not connected
Sep 11 09:02:59 gateway smbd[48491]:   Denied connection from  (0.0.0.0)
Sep 11 09:02:59 gateway smbd[48491]: [2006/09/11 09:02:59, 0] lib/util_sock.c:get_peer_addr(1229) Sep 11 09:02:59 gateway smbd[48491]: getpeername failed. Error was Socket is not connected
Sep 11 09:02:59 gateway smbd[48491]:   Connection denied from 0.0.0.0
Sep 11 09:02:59 gateway smbd[48491]: [2006/09/11 09:02:59, 0] lib/util_sock.c:write_data(562) Sep 11 09:02:59 gateway smbd[48491]: write_data: write failure in writing to client 172.30.10.10. Error Broken pipe Sep 11 09:02:59 gateway smbd[48491]: [2006/09/11 09:02:59, 0] lib/util_sock.c:send_smb(769) Sep 11 09:02:59 gateway smbd[48491]: Error writing 5 bytes to client. -1. (Broken pipe) Sep 11 09:15:51 gateway smbd[48618]: [2006/09/11 09:15:51, 0] lib/util_sock.c:read_data(534) Sep 11 09:15:51 gateway smbd[48618]: read_data: read failure for 4 bytes to client 172.30.10.10. Error = Connection reset by peer Sep 11 14:43:45 gateway smbd[51542]: [2006/09/11 14:43:45, 0] lib/util_sock.c:read_data(534) Sep 11 14:43:45 gateway smbd[51542]: read_data: read failure for 4 bytes to client 172.30.10.10. Error = Connection reset by peer Sep 11 14:54:04 gateway smbd[51665]: [2006/09/11 14:54:04, 0] lib/util_sock.c:read_data(534) Sep 11 14:54:04 gateway smbd[51665]: read_data: read failure for 4 bytes to client 172.30.10.10. Error = Connection reset by peer Sep 11 15:08:55 gateway smbd[51814]: [2006/09/11 15:08:55, 0] lib/util_sock.c:read_data(534) Sep 11 15:08:55 gateway smbd[51814]: read_data: read failure for 4 bytes to client 172.30.10.10. Error = Connection reset by peer Sep 11 16:08:03 gateway smbd[52373]: [2006/09/11 16:08:03, 0] lib/util_sock.c:read_data(534) Sep 11 16:08:03 gateway smbd[52373]: read_data: read failure for 4 bytes to client 172.30.10.10. Error = Connection reset by peer

Now, from my research the best guess I could gather was that it was a hardware issue. So to test that theory, I decided to run a ping all night and see what the results were (command was `ping -p ff00ab -s 10240 -f 172.30.10.10) these are the results from that test:

--- 172.30.10.10 ping statistics ---
40707632 packets transmitted, 40694228 packets received, +4362 duplicates,
0% packet loss
round-trip min/avg/max/stddev = 2.241/2.967/310.331/2.502 ms

Now, as you can see, there really doesn't appear to be enough packetloss to warrant those errors every single time I connect to samba from the WinXP machine. There's also a Win98se machine on my LAN that does not get those errors. I can still use the shares as if there were nothing wrong. However, I would like to get to the bottom of this and see if it can't be fixed.

For comparison, here are ping statistics from the Win98se machine, though this didn't run as long:

--- 172.30.10.11 ping statistics ---
123660 packets transmitted, 123433 packets received, +72 duplicates,
0% packet loss
round-trip min/avg/max/stddev = 2.435/4.071/104.016/3.783 ms

I appreciate any help that I can get from this list. Let me know if there's any other information you need to solve this case.

Thanks
-D Jaquays
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

Reply via email to