When copying files from the Samba server to a Windows95 client or vv, the speed varies dramatically. When I try to copy the same (20MB) file 10 times some times it copies in less than 10 seconds. The next time it takes allmost a minute. And most worrying of all quite often the copying just stops halfway in the middle. The progress bar in Windows just stops. The traffic on the NIC also stops (the traffic led stops flashing). After a timeout of 1 to 2 minutes Windows says 'Cannot copy <filename>: the specified network resource is no longer available'. The Samba server then says that the client closed the connection. The server is a Pentium II 350 128M RAM with a SMC etherpower II 10/100 NIC. Running kernel 2.0.36, and epic100 driver v.1.06 The client is a Pentium 200MMX with 64 M RAM with a SMC etherpower II 10/100 NIC Running Windows95 OSR 2. The client is connected to the server by a cross cable. When I try ftp to transfer the 20M file this always goes in under 10 seconds. Around 3 MB (MegaBYtes) per second. When I use Linux and the smbclient on the client machine instead of W95 I also get high speed copying all of the time. When I use Windows NT on the server-machine instead of Linux and Samba I also get high speed copying all of the time. So it seems that the hardware on both machines is fine. In fact it looks like the setup of both the client and the server is fine. I also tried tuning the max xmit, raw write, raw read, socket options TCP_NODELAY, socket options IPTOS_LOWDELAY, and varies options in the Windows 95 properties for the Etherpower II 10/100, like line speed, rx and tx buffers, inter packet gap, and more. But all to no avail. (Changed one setting at a time and then another after setting the first back to default). I did see changes in speed, mostly a deterioration. But the problem of copying just dropping dead in the middle remains. I want to implement the server in a production environment where people work with Window 95 PC's so this just has to work reliably. Marc
Hello!> the middle. The progress bar in Windows just stops. The traffic onthe NIC> also stops (the traffic led stops flashing). After a timeout of 1 to2 minutes> Windows says 'Cannot copy <filename>: the specified network resourceis no longer> available'. The Samba server then says that the client closed theconnection. Try to increase "shared mem size" to 5-6MB. This was helpfully for me. Ciao: Fonya
Hello Marc!> minute. And most worrying of all quite often the copying just stops halfway > in the middle. The progress bar in Windows just stops. The traffic on > the NIC also stops (the traffic led stops flashing). After a timeout of > 1 to 2 minutes Windows says 'Cannot copy <filename>: the specified > network resource is no longer available'. > The Samba server then says that the client closed the connection.I have got exactly the same problem here. One specific Win98-client can't copy large files. Other Machines (1*Win95, 1*Win98, 3*linux/smbclient) don't have this problem. I am still using Samba V2.0.1, tried to install a Suse-V2.0.2-rpm, but it still reports to be V2.0.1, so I hope that this is not the reason for the problem.> MarcTschau, Lars
"Marc Remijn" <marrem@IAEhv.nl> write> When copying files from the Samba server to a Windows95 client or vv, > the speed varies dramatically. When I try to copy the same (20MB) file10> times > some times it copies in less than 10 seconds. The next time it takesallmost> a > minute. And most worrying of all quite often the copying just stopshalfway> in > the middle. The progress bar in Windows just stops. The traffic on theNIC> also > stops (the traffic led stops flashing).I have a similar problem: only with Win98. Sometimes the speed of retrieving files from the SMB server is just unbelievably high. Seconds later a client can hang for up to 15 minutes. Additionally files are being corrupted, W98 reports out of disk space on SMB volume, etc. I am running Samba 2.0.2 on 2 CPU Linux box :kernel 2.2.3; two network segments: 100BASE-TX and 10BASE-T; HP J3272A 100Base-T Hub; all network cards are 10/100 Intel EE; 17 Win98 workstations; OpenBSD firewall box; NT4 Server (soon to go, especially if I solve the problem with the Samba performance). I would appreciate any ideas, suggestions, help. Regards, Gantcho I. Mantchorov