On Monday 01 September 2003 08:10 pm, Michael Viron wrote:
First I apologize for not reporting what I found yesterday. I had already tried the top two things to no avail yesterday. I tried removing the above key and it made no difference at all. As we speak I'm transferring 285MB of data from the Linux box to the XP box and it has been 8 minutes so far and my guess is that it will take another 9 - 10 minutes. If I do it from my linux server and copy it to the xp box, it will blast over in about 2 minutes or less!!Seems like this is related to the stuff discussed in http://support.microsoft.com/default.aspx?scid=kb;en-us;321169 and possibly in http://support.microsoft.com/default.aspx?scid=kb;en-us;321098 .
You may also want to try running regedit to do the following:
go to "HKEY_LOCAL_MACHINE/Software/Microsoft/Windows/Current Version/Explorer/RemoteComputer/NameSpace" in the registry
remove {D6277990-4C6A-11CF-8D87-00AA0060F5BF} .
This illustrates my point perfectly. When you initiated the transfer on the Linux box it took around two minutes to do the transfer, and you called it fast (blast). I repeated that behavior in my own setup. I got the same results when initiating the transfer on my Mandrake box using Konqueror and command line (cp). I call it slow because when I initiate the transfer on the Win2000 box, using Windows Explorer, I get the same transfer done in under a minute. Why the huge difference in speed?
A two minute transfer for a file that size may be fast compared to a totally broken setup, but it is still half as fast as it should be. The question is: what needs to be done to have file transfers initiated in Linux get the same transfer speed experienced when they are initiated by Windows?
The same thing can be said for transfers between Linux and Linux. It experiences the same crippled transfer speed. The common thread being the transfer is initiated on a Linux box.
http://directory.google.com/Top/Computers/Software/Operating_Systems/Windows/Windows_XP/?tc=1 , which includes about a hundred windows xp relatedThe above key instructs windows to look for scheduled tasks on the pc in question (which may slow done browsing by at least 30s).
Also take a look at
sites of tips / tweaks / guides and howtos.Thanks a bunch Michael. I've started looking them over. As you know, it is somewhat like looking for a needle in a haystack. I'm home sick today, so I'll do some more "googling" to see if someone has come up with a "fix" for this.
Just some thoughts,
If I forgot to mention, SP1 does NOT make a difference for my particular problem. Also, I'm using mdk 9.1 with out of the box Samba. Nothing "special". I'm running 100Bt Half duplex hub. XP to XP fast. XP to ME fast. Linux to XP fast. XP to Linux slooooowwwww. ??? This one has me stumped. What is interesting.... is I swear when I was running older versions of Mandrake I don't recall this slowness. So even though I've bashed XP, perhaps it has been premature. I just thought of this.
Michael
-- Michael Viron Core Systems Group Simple End User Linux
At 04:30 PM 9/1/2003 -0700, you wrote:
On Monday 01 September 2003 03:48 pm, Brant Fitzsimmons wrote:no
Greg Meyer wrote:I would agree from smb to smb, but I really don't believe this is an
On Monday 01 September 2003 03:13 pm, Brant Fitzsimmons wrote:Windows to Samba was only half of my comment. An incorrect Windows
I think the op of this thread had the slowness going the other way. Samba to XP is fast, while XP to samba is fast. In any case, itI was the one who asked the question about slow transfers using Samba. I asked on this list and on the newbie list. Still have not received any answers resolving the issue.
When a transfer to or from a Samba box is initiated from a Win2000 box
it flies. When the same transfer is initiated from a Samba box to
either another Samba box, or to a Win2000 box, it crawls at around 1/3
the speed of the Win2000 initiated transfer. Is this expected
behavior?
always seems to be a problem with the configuration of the windows
machines, not the samba machines.
configuration doesn't explain a slow Samba to Samba transfer.
"incorrect windows configuration" issue. There is a fundamental issue that
I believe Microsoft has done to deliberately break or slow samba. I may
be wrong, but I've not seen a solution yet. I did read somewhere that you
now
longer need netbios resolution for XP to work, but I don't think this is the problem. If anything that would help without a wins server. ??
-- Brant Fitzsimmons [EMAIL PROTECTED] ___________________________________________________________________
Linux user #322847 | Linux machine #207465 | http://counter.li.org/ AMD Duron 1.3GHz | Mandrake 9.1 | Kernel 2.4.21-0.16mm-mdk KDE 3.1.3 | Mozilla 1.4 Mail Client Uptime: 13:30:00 up 4 days, 18:31, 1 user, load average: 0.71, 0.47, 0.29 ___________________________________________________________________
"All truth passes through three stages. First, it is ridiculed.
Second, it is violently opposed. Third, it is accepted as being
self-evident."
-Arthur Schopenhauer (1788-1860)Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
