One scenario for TCP Reset happens with media players which don't ack TCP packets until they have been processed ready to play. If you have large no. of TCP buffers then many packets will have been received but not acked - if you are using a high compressions (e.g. slow speed mP3) or big window size (e.g. Satellite link) then the time taken to play the internal buffer is longer than the TCP timeout on unacked packets.
The problem with TCP connection reset usually happens when users increase the number of buffers and/or increase TCP WIndows size (typically on satellite connections) to optimise the throughput. This is fine for ftp or HTTP - disaster for media. To see if this is your problem you need to check how many packets are unacked when you pause a stream and if you keep stream paused for over 3 minutes (typical TCP timeout) does it reset. -- bpa ------------------------------------------------------------------------ bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806 View this thread: http://forums.slimdevices.com/showthread.php?t=62060 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
