I've seen this as well, but it's not a Samba problem (it occurs with NFS) and it's not a Linux problem either! TCP internet traffic doesn't seem to stream data fast enough to be problematic.
Normally I get this when the connection to the server transverses a 100baseT to 10BaseT link and there are Full/Half Duplex changes. I was able to eliminate this by making the workstation connections talking to the server homogenous. I.E. Worktstation to server path either ALL 100BaseT or ALL 10BaseT. Full duplex 100BaseT to Half duplex 100BaseT is not problematic, but 100 Full to 10 Half causes collisions like crazy! 100 half to 10 Half is a little better. All of this stands to reason though, the transition point either from Full to Half or 100 to 10 represents a BIG bottle neck. The only provisions that Non Switched ethernet has to avoid the overflow is Collision detection & avoidance... So it does indeed happen. -JMS |-----Original Message----- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]] On Behalf Of Bob Puff@NLE |Sent: Thursday, October 18, 2001 2:36 AM |To: [EMAIL PROTECTED] |Subject: [expert] Excessive Collisions with Samba | | |Another question... | |On a couple of other MDK boxes, I am running a Samba server to |talk with Windows 98 |clients. It works, but when I copy files from the Windows |machines TO the Mdk boxes, it takes forever... I noticed there |are tons of collisions on the ethernet line. These collisions |occur even with only one workstation and the mdk box hooked up |to the hub! | |The same thing happens on different boxes, with different |ethernet cards and different speeds. The one common thing is |duplex: half. The collisions do not seem to occur during |normal web traffic, which goes through the boxes (Masq) |sometimes quite heavily. | |Ideas??? | |Bob | |
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
