Hi -- I'm connecting 64bit win 7 professional to an SGI tezro running samba 3.5.8. I connect fine, and everything works except, I cannot read or copy large (40 Mb) files. This used to work when I ran win XP and samba 2. I had to upgrade to version 3 for win 7 to connect. Any clues would be appreciated. Ellis Golub -- ============================================================Ellis Golub Phone: (215) 898-4629 Biochemistry Department FAX: (215) 898-3695 School of Dental Medicine ellis at biochem.dental.upenn.edu University of Pennsylvania 240 South 40th Street Philadelphia, PA 19104-6030 Home: http://biochem.dental.upenn.edu/~ellis/ PGP: http://biochem.dental.upenn.edu/~ellis/public_key.html ==============================================================
On Tue, Mar 15, 2011 at 02:45:58PM -0400, Ellis Golub wrote:> Hi -- > > I'm connecting 64bit win 7 professional to an SGI tezro running samba 3.5.8. > > I connect fine, and everything works except, I cannot read or copy large (40 > Mb) files. This used to work when I ran win XP and samba 2. I had to upgrade > to version 3 for win 7 to connect. > > Any clues would be appreciated.What is the symptom when the copy fails ? What error message do you get ? Jeremy.
On Tue, Mar 15, 2011 at 08:54:19PM -0400, Ellis Golub wrote:> Jeremy -- > > On file open or copy, the progress bar pop-up comes up and and the green bar > begins to move. Somewhere between 1/4 and 3/4 done, the bar stops. If I wait > long enough, I sometimes get an error message saying that the folder containing > the file being opened is not available. After some more time elapses, windows > explorer closes, or the open file dialog box closes. > > File opeations are otherwise completely normal. > > The file size which freezes is not absolute. 5mb files mostly copy and open > normally. A 10 Mb powerpoint file freezes, but a 12 Mb tif image opens. > > I upgraded to samba 3.5.8 today in hopes that things would work better, but no > joy. > > Any help would be appreciated.Re-CC:ing the list so others can help. Please capture a wireshark trace on port 445, and also log at debug level 10 - the last part of the log should show what is going wrong. Jeremy.