Okay, here's the background.

Fedora Core 4, all recent updates. Using samba-3.0.14a-2. Trying to mount a remote shared folder, and sharing it for local users in my office. Using /etc/fstab to auto-mount it on bootup.

Here is the /etc/fstab line that I use to do this:
//share/ccc /gobo smbfs username=XXXXX,password=XXXXXX,uid=10395,gid=30038,fmask=770,dmask=770 0 0

I use winbind to sync with our windows domain (nt, not kerberos yet).

Here is a quick & dirty copy of my /etc/samba/smb.conf file.

[global]
        log file = /var/log/samba/log.%m
        load printers = No
        ldap ssl = no
        idmap gid = 30000-40000
        admin users = CT01\gabriel
        wins server = 172.16.64.4
        domain master = No
        show add printer wizard = No
        dns proxy = No
        password server = ANAKIN
        idmap uid = 10000-20000
        workgroup = CT01
        os level = 20
        security = domain
        max log size = 50
        log level = 1
        logon path = /home/$U
        template shell = /bin/bash

[CCC$]
        path = /gobo
        read only = no

The error I'm concerned about in the logs is this:

Oct 18 09:36:50 mithrandir smbd[8168]: [2005/10/18 09:36:50, 0] lib/util_sock.c:write_socket_data(430) Oct 18 09:36:50 mithrandir smbd[8168]: write_socket_data: write failure. Error = Connection reset by peer Oct 18 09:36:50 mithrandir smbd[8168]: [2005/10/18 09:36:50, 0] lib/util_sock.c:write_socket(455) Oct 18 09:36:50 mithrandir smbd[8168]: write_socket: Error writing 4 bytes to socket 5: ERRNO = Connection reset by peer Oct 18 09:36:50 mithrandir smbd[8168]: [2005/10/18 09:36:50, 0] lib/util_sock.c:send_smb(647) Oct 18 09:36:50 mithrandir smbd[8168]: Error writing 4 bytes to client. -1. (Connection reset by peer)

I see that when I just browse to the linux server, and not even open up a share. Just typing \\mithrandir in my explorer window causes that error to appear. The mounted shared folder works okay, except for the fact that it loses its connection every now and then and I have to remount it. Not sure if that problem is related to this error or not.

I've checked a bit online, and I have seen plenty of questions posted in various places about people asking what that error means, but I haven't ever found an answer or explanation. Could someone please shed some light on this for me? Thanks!

--

 † Gabriel
--
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