network crash using smbclient
philippe.bertin at telenet.be
Sat Dec 8 11:03:55 GMT 2007
Apparantly you loose your network ip address ? What does
/sbin/ifup eth0 (your problematic network interface is eth0, I guess ?)
give as a result when you have these network problems ? Do you get your
network capabilities back ? I can hardly imagine that samba would be at
the origin of the problems that you describe ?
I may be (quite) wrong, but from what you tell, I'd rather suspect some
problems with your network interface(/driver) which probably only shows
up whenever *sending* big files over that interface ? Are you sure you
use the correct driver for your interface? Do you have an idea if the
same problem would occur when sending over the big file using NFS ? If
using samba for sending over the file, are you sure the problem really
doesn't always occur at the *very* same place ?
Andrea Lanza wrote:
>I am facing the following problem:
>if I copy a large file (more than 8GB, i.e.) from a local linux workstation
>to a SMB server (both samba N.A.S. than windows xp /2003), I have no
>If I try to copy back the same file, after a while (1GB... 2GB, sometimes 5
>I got an error about smb server unavailable.
>At this point I have no more network on the linux pc. I tried to
>ifdown/ifup, I tried to change ip address via yast
>(I am running on an opensuse 10.2 box): no net available !!
>I also tried to uninstall anything installed (3.0.23) and install the latest
>binaries 3.027: no changes !
>I also tried both mounting locally the SMB remote via mount.cifs than using
>and using get command after: no changes !!
>The only way I have to make the pc having back the net is to reboot it
>(network light is on: ethtool see it connected: route sees the same thing
>before and after crash !! )
>If I try to ping a local net host, I get the error: Destination Host
>What can I check ? kernel: 220.127.116.11-0.7-bigsmp #1 smbclient: both 3.023 than
>thanks in advance,
More information about the smb-clients