Ok so I've done some of the changes... I fooled around with the settings and I got bursts of 5-10MB from WWW and FTP but then slowed down to 300KB/sec... so I am thinking a $15 NIC might be my next purchase. My line now says: >> socket options = TCP_NODELAY SO_RCVBUF=16384 SO_SNDBUF=16384 16,384 is getting me a more consistent speed over 200KB/sec (I tested many different options/powers of 2) so I'm sticking with it for the time being. -- Ryan On Sep 1, 2009, at 10:41 AM, Ryan Coleman wrote: > Robert, > > 1) Yes, but not from that machine. Other systems have not had issues > and this particular computer downloads off 8Mb cable at full > throttle in SMB over VPN, FTP, WWW and SMTP. > > 2) All connections are wired. CAT-5e and CAT-6 cables, used a > crossover when testing direct transfer, too, but that cable has been > lost since the the test in April (IIRC, I don't need a XO for > gigabit anyway). > > I'm home sick today, and I might get the strength to get out of bed > and sit at the computer soon. RDP is available but I am not that > lazy ;-) > > Thanks again, > Ryan > > On Sep 1, 2009, at 9:12 AM, Robert Nesius wrote: > >> On Tue, Sep 1, 2009 at 1:17 AM, Marc Skinner <marc at e-skinner.net> >> wrote: >> > i would also check the duplex and auto-neg setting on the samba >> server. >> > i would hard set them as well. >> >> Marc, >> >> You nailed the one thing that came to mind for me too - I've seen >> mysterious/slow through-puts before and it's always been mis- >> matched duplex settings for me. Plus, first rule of debugging >> stuff like this - "Start at the physical layer." >> >> Ryan, >> >> Have you tried other file-transfer protocols? i.e., ftp or copying >> a file using ssh or rsync? If those were fast while SMB was slow, >> then debugging service-configs would be the place to look. If >> those are slow too, look at the physical layer. I know you're >> using an airport extreme, but are you hooked up to it with physical >> cables or is everything going wireless? I suspect you have wired >> connections but if not that does change things a bit. >> >> When you tried your direct connection that failed to work, were you >> using a cross-over cable? >> >> While your description of your setup was pretty good, there are >> still points of ambiguity - if the problem still exists after your >> next round of debugging draw a picture of your network config. >> >> -Rob >> >> On Tue, Sep 1, 2009 at 1:17 AM, Marc Skinner <marc at e-skinner.net> >> wrote: >> look at the "socket options" in smb.conf i have mine set as: >> >> socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 >> >> i would also check the duplex and auto-neg setting on the samba >> server. >> i would hard set them as well. >> >> my 2 cents. >> >> On 09/01/2009 12:50 AM, Ryan Coleman wrote: >> > I'm having painfully slow transfers from my FreeBSD 6.3 ia64 >> running >> > Samba 3.3 to Vista (between 1KiBps to 15KiBps) and also to >> Windows 7 >> > (50KiBps to 250 KiBps) and I've tried all the windows corrections >> up >> > and down the board to no avail. I've finally given up on fixing >> > Windows, so it must be my Samba installation. >> > >> > I'm fairly certain I have not forgotten anything from the file >> except >> > 4 fileshares that are unrelated to the issue. Archive is a 6.4TB >> RAID5 >> > (7x1TB drives) that runs blazingly fast in local as well as >> internet >> > traffic. >> > >> > All components (Windows 7, Vista and FreeBSD) are connected >> through an >> > Airport Extreme, but this slowness was experienced even on a basic >> > 10/100 switch so it is not solely a problem with the Airport. Also >> > direct connection did not work and Firewire support was dropped in >> > Vista so there was no alternate "ethernet" option available to me. >> > File transfers from my MacBook Pro perform as expected, with speeds >> > ranging from 5MB/sec to 30MB/sec depending on the connect type. >> > >> > Any and all advice would be most appreciative. >> > >> > TIA, >> > Ryan >> > >> > smb.conf: >> > [global] >> > dns proxy = no >> > log file = /var/log/samba/log.%m >> > load printers = yes >> > server string = UnixBox2 >> > workgroup = WORKGROUP >> > os level = 20 >> > encrypt passwords = yes >> > security = share >> > max log size = 50 >> > >> > [homes] >> > comment = Home Directories >> > browseable = no >> > writable = yes >> > >> > >> > [archive] >> > delete readonly = yes >> > writeable = yes >> > path = /mount/archive >> > only user = yes >> > force directory mode = 755 >> > force group = wheel >> > force create mode = 755 >> > force user = ryan >> > public = yes >> > allow hosts = 10.0.1.0/24 >> > >> > [www] >> > writeable = yes >> > path = /usr/www >> > force directory mode = 755 >> > force group = wheel >> > force create mode = 755 >> > force user = ryan >> > valid users = ryan >> > >> > _______________________________________________ >> > TCLUG Mailing List - Minneapolis/St. Paul, Minnesota >> > tclug-list at mn-linux.org >> > http://mailman.mn-linux.org/mailman/listinfo/tclug-list >> > >> >> >> _______________________________________________ >> TCLUG Mailing List - Minneapolis/St. Paul, Minnesota >> tclug-list at mn-linux.org >> http://mailman.mn-linux.org/mailman/listinfo/tclug-list >> > > _______________________________________________ > TCLUG Mailing List - Minneapolis/St. Paul, Minnesota > tclug-list at mn-linux.org > http://mailman.mn-linux.org/mailman/listinfo/tclug-list -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.mn-linux.org/pipermail/tclug-list/attachments/20091025/d9d44c00/attachment.htm