Page 1 of 1

Slow Transfer rates

Posted: Tue Feb 28, 2012 4:45 pm
by tigerknight
I'm using AndSMB 1.8 on a Xoom and a Samsung Epic 4g (not 4g Touch). Everything works fine in general - connecting, browsing, etc. But when I try to actually grab a file the transfer rates are very slow - the best I've seen is just over 400KB/s. This isn't too bad for small amounts of data, but if I'm trying to transfer even 50mb or so it makes it very slow and tedious.

This is NOT a problem with my wireless AP since the slowness has persisted through two different pieces of hardware on my network (Airlink and now Netgear wireless devices), and also persists across two separate client devices (my Epic and Xoom both do this). I can do internet speed tests on both client devices and get upwards of 20Mbit/s without issue, which should work out to at least 1.5MB/s.

Then today transferring a 150MB file I got this error at about 40% through. Please advise on how to get better transfer rates.

Misc other info: the Xoom runs ICS, the Epic runs Gingerbread. The physical network they connect to is all gigabit (including the wireless AP). Transfers over wireless to PC clients to the same share is 15MB/s or better rather than 400KB/s. Testing was done both at short and medium range on wireless.

--edit--
NOTE: The following error appears to be related to sleeping when screen goes dark. The option is set to prevent sleep while transfers are active but it apparently still happens on ICS in AndSMB .8

Code: Select all

Download Failed: jcifs.d.a.d: Transport1 timedout waiting for response to SmbComReadAndX[command=SMB_COM_READ_ANDX,
received=fase,errorCode=0,flags=0x0018,flags2=0xC803,signSeq=0,tid=28672,pid=23635,uid=30723,mid=16521,wordCount=12,
byteCounte=0,andxCommand=0xFF,andxOffset=0,fid=49281,offset=67571902,maxCount=3906,minCount=3906,
openTimeout=-1remaining=0,offset=67571902

Re: Slow Transfer rates

Posted: Sun Mar 04, 2012 7:39 pm
by support
You're not the first one to report such issue. It means to be related to some devices only. It works on most and we cannot reproduce the problem here.