The sage continues... They benchmark and test with UDP-only, but with that is that the problem is with *TCP* traffic. They refused to even acknowledge anything until I showed it to someone *in person*. Until then it was, "theoretically, that's not possible". My response, "I don't care about the theory behind it. It doesn't work, and your tests are not comparing apples-to-apples."
They are back to theorizing in their lab. The issues I see it definitely seems to be duplex-related. I recently brought a Linksys 10/100 switch from home to the office to test with. This switch, unlike the D-Link, has Duplex indicator lights. With the Linksys desktop switch daisy-chained to my PC, the uplink port is not showing a full duplex connection. And my throughput tests show speeds as bad and worse than when daisy-chained through the phone. But if you remember, the D-Link desktop switch had throughput *twice* as fast as when connected directly to the core switch. WTH? Notes: The vendor is STS Telcom, in Pembroke Pines, FL. They, like many vendors around here, have poor customer service that exudes lots of attitude. I'll give them this, that they do have (1) good customer service tech rep (Amer Khan). Even the NOC Manager is horrible, and tried to blow off the issue with lies followed by backpedaling. I can see why many companies down here try to hire or contract out-of-state. I had heard many horror stories before-hand, and so far all of them are true. -- ME2 On Wed, Jan 28, 2009 at 12:59 PM, Micheal Espinola Jr <michealespin...@gmail.com> wrote: > Hmm. It was going to forced 100/full that brought me to the > realization that there was an issue at the phone. We were previously > auto-everywhere until I started to get a picture of performance issues > on the network. > > Which VoIP solution are you using? > > -- > ME2 > > > > On Wed, Jan 28, 2009 at 12:31 PM, Rutis, Cameron > <cameron.ru...@ci.portland.or.us> wrote: >> right. auto/auto on the switch port, auto/auto on the phone's switch, >> auto/auto on the PC. >> >> -----Original Message----- >> From: Micheal Espinola Jr [mailto:michealespin...@gmail.com] >> Sent: Wednesday, January 28, 2009 8:48 AM >> To: NT System Admin Issues >> Subject: Re: Need help making sense out of odd network performance >> >> so you corrected your problems by going to auto-negotiate? >> >> -- >> ME2 >> >> >> >> On Wed, Jan 28, 2009 at 11:31 AM, Rutis, Cameron >> <cameron.ru...@ci.portland.or.us> wrote: >>> +1 duplex mismatch >>> >>> We use different IP phones but had problems until we went auto/auto in >>> the whole chain. (Even though the phones supposedly "require" forced >>> 100/full) >>> >>> cr >>> >>> -----Original Message----- >>> From: Ben Scott [mailto:mailvor...@gmail.com] >>> Sent: Monday, January 26, 2009 7:41 PM >>> To: NT System Admin Issues >>> Subject: Re: Need help making sense out of odd network performance >>> >>> On Mon, Jan 26, 2009 at 5:51 PM, Micheal Espinola Jr >>> <michealespin...@gmail.com> wrote: >>>> Using the D-Link to daisy-chain only my workstation, ala: >>>> Desktop -> D-Link -> Cisco Catalyst >>> >>> Hmmm. So PC<--->Cisco is slow, but PC<->DLink<->Cisco is fast. >>> Very strange. As a guess: Some combination of duplex mismatch, flow >>> control, and/or buffer memory differences. I doubt you'll be able to >>> diagnose it without someone who has both clue and admin access to the >>> Cisco switch. >>> >>>> *They* say they are operating at Full-duplex. I have the admin >>>> password to the phone, and it says its operating at Half-duplex. >>> >>> I think I'd believe the hardware before some vendor phone-support weenie. >>> :) >>> >>>> But I see no way to configure it. >>> >>> I know nothing about Polycom IP phones. >>> >>> I just yesterday started playing with Nortel IP phones. Some of the >>> switch port settings can only be configured in the boot parameters >>> menu, which you can only get into via a magic key sequence done >>> immediately after power on. >>> >>>> So, sure, my chosen solution should be to ignore the obvious duplex >>>> issue and just buy more equipment? Give me a break... >>> >>> Q: What time is it? >>> A: Time to find a new vendor. >>> >>> -- Ben >>> >>> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ >>> <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ >>> >>> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ >>> <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ >>> >> >> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ >> <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ >> >> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ >> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ >> > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
