<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.19328"><LINK rel=stylesheet
href="BLOCKQUOTE{margin-Top: 0px; margin-Bottom: 0px; margin-Left: 2em}"></HEAD>
<BODY style="MARGIN: 10px; FONT-FAMILY: verdana; FONT-SIZE: 10pt">
<DIV><FONT size=2 face=Verdana>
<DIV></DIV>
<DIV>Hi </DIV>
<DIV></DIV>
<DIV>I use testMPEG1or2AudioVideoStreamer to streams mpg file to the multicast group 239.255.42.42, port 6666/6667 (for the audio stream) and 8888/8889 (for the video stream). When the client(the ip is 129.1.5.222) connect to the server with vlc(using the url rtsp://129.1.5.156/testStream) I run ping command(ping 129.1.5.222 -t) and </DIV>
<DIV>there are many "time out" message:</DIV>
<DIV>C:\Documents and Settings\Administrator>ping 129.1.5.222 -t</DIV>
<DIV>Pinging 129.1.5.222 with 32 bytes of data:</DIV>
<DIV>Request timed out.</DIV>
<DIV>Request timed out.</DIV>
<DIV>Reply from 129.1.5.222: bytes=32 time<1ms TTL=128</DIV>
<DIV>Reply from 129.1.5.222: bytes=32 time<1ms TTL=128</DIV>
<DIV>Reply from 129.1.5.222: bytes=32 time<1ms TTL=128</DIV>
<DIV>Reply from 129.1.5.222: bytes=32 time<1ms TTL=128</DIV>
<DIV>Request timed out.</DIV>
<DIV>Request timed out.</DIV>
<DIV>Request timed out.</DIV>
<DIV>Request timed out.</DIV>
<DIV>Request timed out.</DIV>
<DIV>Request timed out.</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV></DIV>
<DIV>I close the vlc and then run ping command(ping 129.1.5.222 -t), It becomes ok:</DIV>
<DIV>C:\Documents and Settings\Administrator>ping 129.1.5.222 -t</DIV>
<DIV>Pinging 129.1.5.222 with 32 bytes of data:</DIV>
<DIV>Reply from 129.1.5.222: bytes=32 time<1ms TTL=128</DIV>
<DIV>Reply from 129.1.5.222: bytes=32 time<1ms TTL=128</DIV>
<DIV>Reply from 129.1.5.222: bytes=32 time<1ms TTL=128</DIV>
<DIV>Reply from 129.1.5.222: bytes=32 time<1ms TTL=128</DIV>
<DIV>Reply from 129.1.5.222: bytes=32 time<1ms TTL=128</DIV>
<DIV>Reply from 129.1.5.222: bytes=32 time<1ms TTL=128</DIV>
<DIV>Reply from 129.1.5.222: bytes=32 time<1ms TTL=128</DIV>
<DIV>Reply from 129.1.5.222: bytes=32 time<1ms TTL=128</DIV>
<DIV></DIV>
<DIV>I try many times like this.The result is the network becoms very bad when client connecting to the testMPEG1or2AudioVideoStreamer server using url rtsp://129.1.5.156/testStream.</DIV>
<DIV>If client connect to the multicast group 239.255.42.42 directly using url rtp://239.255.42.42:6666 the client can receive audio stream and the network also is OK.</DIV>
<DIV>Why the network becomes so bad when client connecting to the testMPEG1or2AudioVideoStreamer server ?(caused a broadcast strom?) </DIV>
<DIV>Please help me.</DIV></FONT></DIV>
<DIV><FONT size=2 face=Verdana></FONT> </DIV>
<DIV align=left><FONT color=#c0c0c0 size=2 face=Verdana>2012-10-08
</FONT></DIV><FONT size=2 face=Verdana>
<HR style="WIDTH: 122px; HEIGHT: 2px" align=left SIZE=2>
<DIV><FONT color=#c0c0c0 size=2 face=Verdana><SPAN>kingaceck</SPAN>
</FONT></DIV></FONT></BODY></HTML>