Hello all,
I'm using RH 8 with all the latest updates including Samba 2.2.8a. My problem is I setup a cron job to download large files (over 300MB) at night so I don't tie up the Internet at work. Now I have the files on my server, but I need to move them over to a workstation to be burned to CD. Samba will not let me copy or move these large files. After I try, all my mapped drives on the workstation are deleted, even my Novell maps.

The log shows this:

[2003/04/17 09:13:39, 0] lib/util_sock.c:read_data(436)
read_data: read failure for 4. Error = Connection reset by peer

I've seen this problem posted before elsewhere, but it never seems to get a response. I do the same thing at home with CD ISO's and it works great. Anyone got a clue on this one?

Thanks

Okay, I'll throw in some more interesting info. My workstation at work in Win98 and cannot copy the info without the error, yet my WinXP laptop can access it and copy it just fine.

Hmmmmmmmmmmm???

The problem is most likely with Win98 and not Samba. Is each file about 300 MB or is the total 300 MB? If the later, you might have better luck copying subsets of the group. You might also try to pull the files from the Win98 machine rather than push them from Samba.

I have had terrible luck trying to push large volumes of data to my Win98 machine from Win2K and RH8. Pulling it works somewhat better but still is not 100%.

You are downloading the files at home, then sending them to a corporate server, and then to your work computer? This saves time? CD burners are pretty cheap. Putting one in your linux box would make life much more simple.

Actually what I'm doing at home and at work are totally separate. I was just passing along the info that the same thing I was doing at work and getting an error was working at home. On my home server I'm downloading 600MB ISOs, on the server at work it is archived databases. Can't install a CD writer at work for security reasons, plus it's a pretty busy server. I doubt it could finish reliably. I'm trying to pull them over to the workstation to make CD copies of the daily archive for long term storage. Trust me, it's the best method I've tried to do what I need to get done.

My home computer is XP too, so I gathered as much about the OS issues. It appears this still hasn't been addressed by MS because the previous posts I've read were from 1999. I was just hoping that someone had a work-around by now.

Ok, here's another interesting slant on this problem.

I'm running Samba 2.2.8a (Just upgraded fron 2.2.2 to try to solve this problem!), on my Solaris 8 box (An old intel P200MMX).

I share all my MP3s from this box, and one of the machines we play the MP3s from over our mini network here at home is a Windows98 box. This Win98 machine is doing *exactly* as described previously in this thread, WinAMP (Or Windows media player - doesn't matter) plays the files just fine, but will eventually cut out for several minutes after which only a few short bursts of music will make it through.

The SAMBA logs report:

[2003/07/11 11:40:41, 0] lib/util_sock.c:read_data(436)
read_data: read failure for 4. Error = Connection reset by peer
[2003/07/11 11:40:41, 1] smbd/service.c:close_cnum(677)
trident (xxx.xxx.xxx.xxx) closed connection to service public
[2003/07/11 11:41:01, 1] smbd/service.c:make_connection(636)
trident (192.168.49.16) connect to service public as user xxxxxx(uid=xxx, gid=xx) (pid 24622)

I can play the *hours* worth of MP3's from my Win2K machine with no problems at all - therefore I strongly suspect something odd about Win98 that's screwing around with the SMB protocol when transferring large files or data streams.

Sean.

Its a shame isn't it? I wish I had an answer for you by now, but as you can see, the issue still remains. I'm sure it is an issue with the Win98 TCP/IP stack implementation. With Microsoft cutting support for Win98 in the next few weeks, I'd say the only solution would be to upgrade to 2000 or XP.

Sorry

You can try upgrading the NIC drivers and do a Win98 update. You can try adding a line in the registry (I think consistent connections is what it is called).

Go to samba site and look through smb.conf documentation or type man smb.conf .

You may want to add
socket options = IPTOS_THROUGHPUT
This setting is for WAN connections. I don't know why you want to use SAMBA over the internet. To me, its very dangerous. FTP is a little safer.

You can also try large readwrite = yes in the global section. This might fix Win98.

Windows 2000 is more prone to this problem than Win98.

I don't have any problems with my Win98 system. I can copy huge files close to 4 gigabytes in size to my LINUX system and also to my Win98. Though I'm using Mandrake 9. It might be Redhat's TCP/IP settings in its kernel.

I have no problem with Win2K - its Win98 that's causing all the problems. Personally I hate it as an OS, but its not my machine...

I'm getting the exact same problem.

I'm using Xandros 1.0 and Debian's 2.2.8a-woody SAMBA packages.

However, I seem to be getting the problem at the same time on both a Win98 box AND my Win2k laptop. (They both hiccup/disconnect/whatever within 30 seconds of each other.)I've tried running the laptop without having the Win98 box connected, but not vice-versa. I'm averaging about 14 disconnects in an 8 hour shift.

To add to the pile...

I just upgraded one of our RedHat 8.0 servers which was running Samba 2.2.5 without any issues. We are now experiencing the same problem that you have all mentioned:

Error = Connection reset by peer

As well we are seeing "Oplock_break" errors. I have turned oplocks off on that share which resolved the oplock issues but the connection dying has been persisting.

Since this all occured when we did the upgrade it would appear that the kernel changes are to blame (either that or one of the other packages that was upgraded, but it seems unlikely). Currently I have booted into the old kernel 2.4.18 and it is running fine. I am wondering if there were changes made to the kernel that would have effected the sockets. Any thoughts...

Possible help...

I re-installed Xandros from scratch, used Xandros Networks to upgrade everything BUT Samba, then updated Samba from the 2.2.8a packages.

Two disconnects in four days, and one can be directly attributed to 802.11b. ;P

Apparently something in Samba 2.999 has SEVERE problems.

It may not be much help, but I know that 98 CAN copy files that large into samba shares. I've moved ISO's back and forth, but the performance isn't great (like 6 megabits a second on a 100megabit LAN).

My question is, can you copy smaller files successfully?
And the connection reset by peer "error" is fairly common on samba after version 1.9.x. Doesn't seem to affect anything as far as I can tell.

The day that MS releases the code for their tcp/ip stack will be a great day for samba indeed! (cough, cough)