Netflix failure - ReadBuffer offset

I'm getting a "Netflix cannot be reached" failure with the following raw data:
ReadBuffer offset [0,1401] out of bound 1400
Is this a bug in Fing Desktop or is it something caused by the SSL inspection on my FW? More details about what these tests actually do would go a LONG way towards helping people understand the test results.


  • Marc
    Marc Moderator, Beta Tester Posts: 2,804
    250 Answers 1,000 Likes 2500 Comments 250 Awesomes
    @GaryParr , when the desktop is doing net connectivity checks using Netflix, it appears to go out to whatever DNS you have configured, then it tries to resolve and once it resolves attempts to go out and connect.  (I confirmed with Wireshark).  Example below of what it called out to once resolved...  Could your local firewall be blocking this ?

    "24852 11.943473 Marcs-Mac-mini-4.local TCP 78 58029 → https(443) [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=64 TSval=1140322295 TSecr=0 SACK_PERM=1"
    Thats Daphnee, she's a good dog...