WMP only connects to one port (because WME only serves data on one port). Where did you get this 2 port idea ?
If you start and then stop the connection, there's a HTTP protocol based timeout, where the port on the machine with WMP conected to the encoder will be in closing state for some time - perhaps that's what you mean?
Cheers - Neil
On Mon, 25 Jun 2007 11:02:14 +0200, "Ronny" <ronny[ at ]lack.net.il> wrote:
[Quoted Text] >Thanks, >Why then does WMP use 2 ports when connecting to WME? >Are they always consecutive? > >Thanks > >Ronny >> The "use ports" is only for the UDP streaming. With TCP streams the >source >> port (client port) is determined automatically by the operating system and >> should not be forced. With TCP the only port that is specified is the >> "connect to" port, i.e. the port that is acting as a server (WME in this >> case). >> >> So when using TCP protocols such as HTTP the source port cannot be set, >and >> would serve not purpose. WMP makes an outbound connection to port (e.g. >> WME port 8080) and passes it's (random) client port to the server. When >> the server binds the connection a "pipe" is established that allows data >to >> flow in both directions. >> >> -- >> http://www.chrisnet.net/code.htm>> [MS MVP for DirectShow / MediaFoundation] > ------------------------------------------------ Digital Media MVP : 2004-2007 http://mvp.support.microsoft.com/mvpfaqs
|