> I've a win2003 server with 2 network cards
> 1) 192.168.1.1 (100Mbit)
> 2) 192.168.50.1 (1Gbit)
> 1) 192.168.1.2 (100Mbit)
> 2) 192.168.50.2 (1Gbit)
> When i read from a samba server and i copy into the win2003 speed is
> when i do the opposit (reading from win and writing to samba) it's
> incredibly slow.
> The Gbit network is the slow one.
> The 100Mbit network works fine.
Assuming the Samba server is running Linux -- what flavor? what
What kind of nics?
Similar issues with other protocols -- eg., FTP or HTTP? Have you
tried a quick and dirty test setting one of these up on the Samba
Examined packets for possible GigE performance issues? Ethereal runs
quite nicely on both Win and Linux.
Does ifconfig on Linux show errors? Netstat output from Linux and XP?
GigE nets can be _very_ fussy about TCP settings and your symptoms --
very slow writes to the Samba server at GigE speeds are quite common as
interrupt processing and buffers both may be easily swamped with
default settings. Packet sniffing will usually give good clues what's
If this is just a home setup, it may be easiest to run 100mb on the
GigE nics for more consistent, reliable service. Even in "commercial"
settings it is not uncommon for folks to settle for 30-40% of 1000Mbs
If you want/need the extra speed be prepared to do a good bit of
detective work to locate the bottleneck. My first guess is that the
writes are swamping the disk subsystem and kernel I/O scheduler -- with
a possible interrupt overload from the nic thrown in.
You might want to search in linux.samba ("gigabit slow" is what I just
tried) for some clues.
Till you get back with some performance data, TCP settings, clueful
packet sniffs it's _very_ near impossible to tell what your problem is.
Is it worth the problem to tackle this now -- holidays and all?
email above disabled