Weird Samba misbehaviour.

From: Adam Funk (a24061_at_yahoo.com)
Date: 07/17/04

  • Next message: Frederik Dannemare: "Re: NETGEAR MA311 802.11b Wireless PCI Network Adapter Card" 
    Date: Sat, 17 Jul 2004 09:19:15 GMT
To: debian-user@lists.debian.org

    I routinely run the Windows backup utility to create the backup file on
    a network drive which is really a Samba share on my Debian box. Today
    it doesn't work: Windows backup says "Q:\w2k.bkf" is not accessible.
    But at the same time, I can create, edit, save and rename a text file
    on the Q: drive. Backup alone thinks Q is inaccessible.

    Here are the tails of the Samba logs (192.168.123.2 and bobmoose are the
    same machine.

    /var/log/samba $ tail log.192.168.123.2
    [2004/07/08 19:02:48, 1] smbd/service.c:close_cnum(887)
      192.168.123.2 (192.168.123.2) closed connection to service shared
    [2004/07/17 10:08:37, 1] smbd/service.c:make_connection_snum(619)
      192.168.123.2 (192.168.123.2) connect to service shared initially as
    user nobody (uid=65534, gid=65534) (pid 20353)
    [2004/07/17 10:08:41, 1] smbd/service.c:make_connection_snum(619)
      192.168.123.2 (192.168.123.2) connect to service shared initially as
    user nobody (uid=65534, gid=65534) (pid 20353)
    [2004/07/17 10:11:06, 1] smbd/service.c:close_cnum(801)
      192.168.123.2 (192.168.123.2) closed connection to service shared
    [2004/07/17 10:11:06, 1] smbd/service.c:close_cnum(801)
      192.168.123.2 (192.168.123.2) closed connection to service shared

    /var/log/samba $ tail -20 log.bobmoose
    [2004/07/17 08:59:55, 1] smbd/service.c:close_cnum(801)
      bobmoose (192.168.123.2) closed connection to service shared
    [2004/07/17 09:05:11, 1] smbd/service.c:make_connection_snum(619)
      bobmoose (192.168.123.2) connect to service shared initially as user
    nobody (uid=65534, gid=65534) (pid 1226)
    [2004/07/17 09:05:52, 1] smbd/service.c:close_cnum(801)
      bobmoose (192.168.123.2) closed connection to service shared
    [2004/07/17 09:21:33, 1] smbd/service.c:close_cnum(801)
      bobmoose (192.168.123.2) closed connection to service shared
    [2004/07/17 10:01:16, 1] smbd/service.c:make_connection_snum(619)
      bobmoose (192.168.123.2) connect to service shared initially as user
    nobody (uid=65534, gid=65534) (pid 1226)
    [2004/07/17 10:01:16, 1] smbd/service.c:make_connection_snum(619)
      bobmoose (192.168.123.2) connect to service shared initially as user
    nobody (uid=65534, gid=65534) (pid 1226)
    [2004/07/17 10:01:58, 1] smbd/service.c:close_cnum(801)
      bobmoose (192.168.123.2) closed connection to service shared
    [2004/07/17 10:10:26, 0] lib/util_sock.c:read_socket_data(367)
      read_socket_data: recv failure for 4. Error = Connection reset by peer
    [2004/07/17 10:10:26, 1] smbd/service.c:close_cnum(801)
      bobmoose (192.168.123.2) closed connection to service shared
    [2004/07/17 10:15:31, 1] smbd/service.c:make_connection_snum(619)
      bobmoose (192.168.123.2) connect to service shared initially as user
    nobody (uid=65534, gid=65534) (pid 20374)

    Any idea what is causing the "read_socket_data: recv failure for 4.
    Error = Connection reset by peer" error?

    Thanks,
    Adam 

    -- 
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
  • Next message: Frederik Dannemare: "Re: NETGEAR MA311 802.11b Wireless PCI Network Adapter Card"