I was trying to transfer over 2 folders which, in all, are about 120 gigs of hard disk space. I was using a Slackware 12.0 box and was transfering them to a windows xp pro box. I setup a share on the xp pro box. Then on the slackware box, I mounted the share and then cp -R the two folders into the share. Everything went fine, after 2 gigs downloaded into the windows xp pro box, activity on tcpdump (dst port where the connection to the share was made) stopped. I checked the cp -R konsole and it returned a File size limit exceeded message.

Why does this happen? Buffer space allowed for the tcp connection not big enough? Anyway around this? The winxp pro box is ntfs with plenty of free hd space. Both the Slackware box and the Winxp Pro Box each have 2 gigs of ram. Suprisingly download stopped after 2 gigs.

Using FAT or NTFS on the XP side?

NTFS shouldn't be a problem, and FAT32 should allow files up to 4GB (-1 byte). Google for "samba 2gb limit", it seems that there are lots of persons having this same problem. You can try to mount the volume as cifs instead of smb, however I have no personal experience with this problem because I rarely use Windows machines over samba and even then I never transfer big files.

Yeah just mounted the share as cifs

sudo mount -t cifs //computername/share /mnt/computername -o ip=192.168.1.x