On Sun, Jan 25, 2009 at 3:38 PM, Micheal Espinola Jr <[email protected]> wrote: > Via direct connection: Speed=131.192 MB/min, in 2:24m (meh) > Via phone-chained: Speed=36.764 MB/min, in 8:36m (asolutely horrible)
I suppose it's possible the network switch built-in to the Polycom phones just suck. > Via D-Link DGS-2205 switch: Speed=451.726, in 0:42m (WTH ?!) Where is the above switch in the topology? Were you copying between two nodes connected to the D-Link, or using the D-Link to daisy-chain to the Cisco, or what? > Everything is hard-coded for 100 Mbps / Full-Duplex. Does that include the switch ports in the Polycom phones? Ethernet flow control may also be an issue, especially if it's supported by some nodes and not others. Like everyone else said, traffic shaping of some kind (QoS, VLAN priority, etc.) seems a likely culprit. You've already said the third-party service provider has issues with response time; maybe they have issues with lack-of-clue as well. Another possibility: Do you just have a couple devices plugged into the D-Link for testing? If so, perhaps Cisco switches (being full of active equipment) are running out of resources (buffer memory, backplane bandwidth, etc.), while your D-Link switch (being mostly idle) has resources to spare. I second the suggestion of a packet sniffer. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
