Whenever I try to update gem or install a gem, it times out on:
Updating Gem source index for: http://gems.rubyforge.org.
A network trace shows a stuck window.  Everything else is fine across
this link.  We do go through a pix and fortinet (AV) box on the way
out, but I haven't see this problem before.

Any ideas out there?  Thanks, Rick

http://dsl092-150-242.wdc2.dsl.speakeasy.net/yaml.Z from
MyPC.workgroup.com
Expert: HTTP Slow Response Time (8.915957000 from packet 4), Packet 6
(66.92.150.242 -> 10.10.10.10)
Expert: TCP Low Window (6,112 of 64,512 bytes), Packet 74 (10.10.10.10
-> 66.92.150.242)
Expert: TCP Low Window (3,192 of 64,512 bytes), Packet 77 (10.10.10.10
-> 66.92.150.242)
Expert: TCP Low Window (272 of 64,512 bytes), Packet 80 (10.10.10.10 ->
66.92.150.242)
Expert: TCP Zero Window, Packet 82 (10.10.10.10 -> 66.92.150.242)
Expert: TCP Stuck Window (0 of 64,512 bytes), Packet 86 (10.10.10.10 ->
66.92.150.242)
Expert: TCP Stuck Window (0 of 64,512 bytes), Packet 88 (10.10.10.10 ->
66.92.150.242)
Expert: Low Server-to-Client Throughput (5 kBytes/second), Packet 89
(66.92.150.242 -> 10.10.10.10)
Expert: TCP Stuck Window (0 of 64,512 bytes), Packet 90 (10.10.10.10 ->
66.92.150.242)
Expert: TCP Stuck Window (0 of 64,512 bytes), Packet 92 (10.10.10.10 ->
66.92.150.242)
Expert: TCP Stuck Window (0 of 64,512 bytes), Packet 94 (10.10.10.10 ->
66.92.150.242)
Expert: TCP Stuck Window (0 of 64,512 bytes), Packet 96 (10.10.10.10 ->
66.92.150.242)
Expert: TCP Stuck Window (0 of 64,512 bytes), Packet 98 (10.10.10.10 ->
66.92.150.242)
Expert: TCP Inactive Connection Reset (39.881578700 from packet 98),
Packet 99 (66.92.150.242 -> 10.10.10.10)