Two PCs - System A and System B. Both running XP SP2. Latest drivers, all updates, as current as possible.
System A has two Marvell Yukon PCI-E onboard Gigabit adapters. Let's call them A1 and A2. A2 is connected to a Fast Ethernet Router which in turn is connected to a cable modem, and is using all of the speedguide tweaks and works fine.
System B has one Linksys EG1032 ver2.0 Gigabit adapter. Call it B1.
A1 and B1 are connected together with a Linksys 5-port Gigabit workgroup switch over Cat6 cable. The switch's indicators show the connection is 1000Mb on both sides.
When I have the MaxFrameSize on A1 and B1 set to 1514 and the TCP MTU for both adapters set to 1500, the TcpWindowSize(s) set to 513920, and Tcp1323Opts = 1, everything works fine.
Here's the problem:
I want to maximize my performance across the Gigabit using Jumbo Frames - 9014.
If I set the MaxFrameSize(s) to 9014, adapter MTUs to 9000, TcpWindowSize for the adapters to 501760, and Tcp1323Opts = 1, then things get screwy.
Printer and File Sharing only work if the data being sent/received is "small" - short directory lists or small text files to be printed. Anything larger than that and the initiator hangs up.
If I ping from System A or B to the other side, it works fine so long as the buffer size is 1476 or less. Any ping with a buffer size between 1477 and 8972 times out, and anything over 8972 gets "Packet needs to be fragmented..." - as it should.
Ex: Ping -f -l 1477 SystemA
I've been researching this for days now, and all that I can come up with is other 2K/XP users trying this seem to be having similar problems.
Am I missing something? Has anyone actually gotten Gigabit with Jumbo buffers to work on a simple Windows-to-Windows connection?
Any help with this would be greatly appreciated.
Thank you.