Problems with Samba and/or Sundance Ethernet Driver
I didn't have any luck with this on the user list, I'm hoping someone on
this list can offer some suggestions. I'd really like to spend some time
digging into this to see if I can find the real problem, but I'm not sure
where to start. Any suggestions are appreciated. Thanks,
Paul
----- Original Message -----
From: "Paul Galbraith" <paul@paulgalbraith.net>
To: <debian-user@lists.debian.org>
Sent: Wednesday, July 16, 2003 8:20 AM
Subject: Problems with Samba and/or Sundance Ehternet Driver
> I'm having a lot problems getting Samba running on my deb 3.0 machine. I
> suspect the problem is really a problem with the sundance ethernet driver,
> but that's a fairly random guess.
>
> The main diagnostic symptoms are numerous read failures in the samba log
> file, such as:
>
> [2003/07/15 15:29:33, 0] lib/util_sock.c:read_data(436)
> read_data: read failure for 4. Error = Connection reset by peer
>
> These occur whenever I try to browse or use the file share. From a WinXP
> client, I cannot even connect to the share...I just get a "cannot find
> resource" error (accompanied my many of the above read failures in the
samba
> log) after a delay of several minutes. From a WinME client, I can browse
> the share, but almost any attempt to transfer files results in an error
and
> many more of the above messages in the samba log.
>
> Here is my smb.conf:
>
> [global]
> workgroup = arda
> encrypt passwords = yes
> security = share
>
> [pub]
> path = /home/samba
> public = yes
> browseable = yes
> writable = yes
> guest ok = yes
> guest only = yes
>
> As I said, I suspect it's a problem with my ethernet driver (sundance.o)
or
> else my NIC (D-Link DFE-530TXS) is bad. (I've seen the above problems
when
> using either of the 2.2.20 or 2.4.18 kernels.) Since I haven't seen any
> other networking problems, either of these conclusions seems a little
> suspect, but I can't think what else could be the problem. Is there a
good
> way to test my network adapter and verify that it (and the driver) are
> working properly?
>
> Thanks to anyone who can offer some suggestions!
>
> Paul
>
Reply to: