Samba/two Win2K machines

[Ted Mittelstaedt]

> -----Original Message-----
> From: owner-freebsd-questions at freebsd.org
> [mailto:owner-freebsd-questions at freebsd.org]On Behalf Of Martin Hepworth
> Sent: Thursday, December 09, 2004 1:03 AM
> To: Patrick Lindholm
> Cc: freebsd-questions at freebsd.org
> Subject: Re: Samba/two Win2K machines
> 
> 
> Patrick
> 
> doing this over a 10mbs half duplex network will give lots of collisions 
> (a half duplex network uses one set of wires to communicate both ways - 
> hence you get collisions as both machines try to talk at the same time.
> 

So what.  Collisions are normal on a half-duplex ethernet network.
Are you one of those people who think that just because the word
collision is used that they are bad?  What do you think people did
before switches were invented?

> Also the smb protocal isn't very efficient so a long time like this 
> isn't unexpected even if running 100mbs!
> 

This isn't true either.  For starters he already said that speed 
between the BSD box and the w2k system was fine, and that only
speed between the 2 w2k boxes was slow.  Since each of those
connections use the SMB protocol, how can it be fine between
bsd and windows and not fine between windows and windows?  If
the protocol was as slow as your claiming, it would be slow
between the bsd box and the w2k box.

> Prob best way if to spend a few (insert local currency) and buy a small 
> 100mbs switch which will help esp if you're network cards can run 100mbs.
> 

That may help but not because it's a switch and not because its fast
ethernet.  It may help because it is possible that his problem is that
the network adapter cards aren't correctly sending and receiving data
between themselves and his existing hub.  These kinds of incompatabilities
sometimes happen espically between older 10baset non-autonegotiating 
dumb hubs, and new 10/100 autonegotiating cards.

It also may help because one of the symptoms of a failing hub is
that it gets -really slow- when passing a lot of data, and his hub
could be failing.

But this also could be the result of some misconfiguration on his
windows sytems.  That should be eliminated before throwing money
at hardware.

Ted