Merton,
You haven't detailed what aspect leads you to the conclusion the client isn't keeping up. At a guess if you are referring to dropped video frames (for real-time conferencing and the like ) because of lack of client CPU/graphics capability, then telling the server the server to slow down isn't going to do anything for you. This is no difference for say a VoIP/internet telephony setup where if you experience congestion there is little else to do other than play silence. The only other thing to do is during setup phase where you might choose a lower frame rate/resolution which might reduce the network load and/or CPU load for encoding/decong the media.
And as Ronnie correctly says, ICMP source quench might still live in networking text books, but no one has used it in real life for a good decade or so.
Regards, Martin
MartinVisser99@xxxxxxxxx
On Mon, Jun 1, 2009 at 12:00 PM, Merton Campbell Crockett
<m.c.crockett@xxxxxxxxxxxxxx> wrote:
Using various Wireshark's various tcp.analysis expressions I've
discovered that it is not uncommon for the Live Communications Server
2005 to transmit data to a Windows XP client faster than the latter
can transfer data to the application. It's unclear whether its simply
that Office Communicator 2005 can't keep up or if it is the result of
other activity on the client system.
Does the Windows XP TCP/IP protocol stack transmit ICMP Source Quench
packets when it is in danger of exhausting its buffer space?
I didn't find any ICMP Source Quench packets in the traffic that I had
captured. If it doesn't, everything is fine. :\ If it does, I may
need to search for a network device that is overly zealous in
filtering ICMP packets. :-(
Merton Campbell Crockett
m.c.crockett@xxxxxxxxxxxxxx
___________________________________________________________________________
Sent via: Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
Archives: http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe