Skip to main content
August 13, 2010
Question

Bad network data; terminating connection

  • August 13, 2010
  • 3 replies
  • 2307 views

Many times, each day, a notice this error in the event log :

Bad network data; terminating connection : (Adaptor: _defaultRoot_, VHost: _defaultVHost_, IP: XXX, App: AppName/Instance, Protocol: rtmp, Client: 5856213718289632378) : v E3 k A3 + 16 S B9 ED > 84 8C A7 98 C3 & G B1 u 8 4 90 T N { 18 d 84 0C 00 92 A1 EF E1 F6 % P F9 80 0 02 E5 D8 \ 08 o j 12 F9 E6 F S 05 D3 l q Q ) C3 82 02 8A BA t A F

each time after this error, the netconnection between the publisher and the server close.  I have some log in my app who check the connectivity between the publisher and the server :

function threadIsPublisherOnline()

{

     clearInterval(ptrThreadIsPublisherOnline);

if(!_root.nc.isConnected)

{

if(mustDisconnect)

{

     trace("The server as close the connection, redirect the publisher");

     getURL("closer.aspx?language=" + _root.Language);

}

mustDisconnect = true;

var ro:Object = new Object();

ro.onStatus = function(info)

{

       trace("nc.isConnected is false and I can't receive the return of my server call, so I redirect the publisher");

getURL("closer.aspx?language=" + _root.Language);

}

ro.onResult = function(info)

{

mustDisconnect = false;

}

_root.nc.call("ack", ro);

}

I search over the internet and the only real info I found about it is on this site : your system has been port scanned or attacked

http://books.google.ca/books?id=ivHm6W7nRBIC&pg=PA786&lpg=PA786&dq=Bad+network+data;+terminating+connection&source=bl&ots=2GpagF5L6c&sig=mWwsDz6nk3qbroMlkggQM8TsMUE&hl=fr&ei=7VJkTLfVI4T78Aa4-e2jCQ&sa=X&oi=book_result&ct=result&resnum=8&ved=0CEEQ6AEwBzgK#v=onepage&q=Bad%20network%20data%3B%20terminating%20connection&f=false

I just want to confirm if it's the real issue of this problem or if other thing can provide this result and how can I prevent the deconnection of the publisher if this append again?

Thanks

    This topic has been closed for replies.

    3 replies

    August 23, 2010

    Yes, I updated one of our servers to version 3.5.4, but the
    number of error remains unchanged.

    Have you any idea what is the basis of this error?
    It may be that this is somes packet lost on the internet connection?
    Or third party software that try to grab the stream?

    What could cause this error?

    Thank your for your help, this is a very annoying issue.

    Adobe Employee
    August 24, 2010

    This comes when FMS state machine which expects the chunkified rtmp data fails to parse the data. So this might happen if some of the data is lost or is corrupted in between..

    -Which encoder are you using to publish the data. Is it FMLE. ?

    August 19, 2010

    We had already put in place safety procedures, but we still considered the material you have sent.

    We have done tests on 3 servers

    - The first was the original configuration
    - The second was the change reflected in the documentation you have sent
    - the third was outside of our infrastructure with a different internet connection.

    After a day of testing, the results are similar on the 3 machine.

    Do you have any other assumptions about the possible cause of this error?

    I don't think this is a attack because the ip who is disconnecting the stream and generate this error only crash one instance of the application and we do not have any recurrence from these ip after this.

    Thanks for your help.

    Participating Frequently
    August 20, 2010

    Sorry if i did not get you clearly but i just wanted to confirm with you that you see the issue even after upgrading to 3.5.4?

    Participating Frequently
    August 16, 2010

    It might be the case that someone is trying to attack your system which is causing this issue. Before we go further i would like you to recommend you few things:

    1. If you are on 3.5 version, please update it to 3.5.4 which has got quite a few security fixes.

    2. Please configure your server more securely if you have not done so - you can refer to Hardening Guide by Asa which talks about these aspects : http://www.adobe.com/devnet/flashmediaserver/articles/hardening_guide.html

    3. You can also read this whitepaper and take measures based on it: http://www.adobe.com/devnet/flashmediaserver/articles/protecting_video_fms.pdf

    After you have done above steps and updated and configured your server properly if you are still getting the Bad Network data errors, do let us know and we will dig deep into it.