Page 1 of 4 123 ... LastLast
Results 1 to 10 of 31

Thread: Cant' connect.

  1. #1
    Join Date
    Jul 2016
    Location
    USA
    Posts
    227

    Cant' connect.

    I'm getting the "failed to connect , make sure NEXTpvr is running" message.

    I can access NEXTpvr via the IP address, in my case 192.168.0.11:8866 (From a desktop (my ip is 192.168.0.8 in the logs) and from an android (my ip is 192.168.0.140 in the logs)

    I've disabled firewall and tried. I have tried on 3 different Androids devices, including version 4.4.4 and 6.0.1.

    The IP request from the Android version 6.0.1 is 192.168.0.140 and NRecord.log shows

    2018-04-03 11:16:59.138 [DEBUG][4] OnStart() complete...
    2018-04-03 11:17:18.389 [DEBUG][13] Received broadcast from 192.168.0.140:44682 :
    DISCOVER_REQUEST

    2018-04-03 11:17:18.389 [DEBUG][13] Waiting for broadcast
    . Not sure if that is the attempt.


    Not sure if this has anything to do with my network settings or not. I can access my shared folders via Android with ES File Explorer so not sure why if it is a network or firewall issue. I do run a VPN client but have even disabled it and tried.

    I've cleared the data and cache for the APP and restarted. I've tried over several days.



    APP version is 1.2.180402.


    EDIT: logs removed
    Last edited by p37307; 2018-04-03 at 11:27 PM. Reason: removed logs
    ~Paul

    Setup: NextPVR, Serviio, WinTV-quadHD and WinTV-HVR-955Q. Custom Roku channel developer. Feeding Tube Advocate. About me or http://chambers.pw.

    If you haven't broken it at least once, you're not doing it right.

  2. #2
    Join Date
    Jul 2016
    Location
    USA
    Posts
    227
    I enabled Windows 10 Firewall logs and this is what it shows when I attempt to connect with the app from my Android
    #Fields: date time action protocol src-ip dst-ip src-port dst-port size tcpflags tcpsyn tcpack tcpwin icmptype icmpcode info path
    2018-04-03 12:50:33 ALLOW UDP 192.168.0.140 255.255.255.255 42561 16891 0 - - - - - - - RECEIVE
    2018-04-03 12:50:33 ALLOW UDP 192.168.0.11 192.168.0.140 16891 42561 0 - - - - - - - SEND
    2018-04-03 12:50:35 ALLOW TCP 192.168.0.140 192.168.0.11 46937 8866 0 - 0 0 0 - - - RECEIVE
    2018-04-03 12:50:36 ALLOW TCP 192.168.0.140 192.168.0.11 39370 8866 0 - 0 0 0 - - - RECEIVE
    This is the firewall log when I go to 192.168.0.11:8866 from Google Chrome from my Android.

    #Fields: date time action protocol src-ip dst-ip src-port dst-port size tcpflags tcpsyn tcpack tcpwin icmptype icmpcode info path
    2018-04-03 12:54:56 ALLOW TCP 192.168.0.140 192.168.0.11 39380 8866 0 - 0 0 0 - - - RECEIVE
    2018-04-03 12:54:56 ALLOW TCP 192.168.0.140 192.168.0.11 39381 8866 0 - 0 0 0 - - - RECEIVE
    2018-04-03 12:54:56 ALLOW TCP 192.168.0.140 192.168.0.11 39382 8866 0 - 0 0 0 - - - RECEIVE
    2018-04-03 12:54:56 ALLOW TCP 192.168.0.140 192.168.0.11 39383 8866 0 - 0 0 0 - - - RECEIVE
    2018-04-03 12:54:57 ALLOW TCP 192.168.0.140 192.168.0.11 39384 8866 0 - 0 0 0 - - - RECEIVE
    2018-04-03 12:54:57 ALLOW TCP 192.168.0.140 192.168.0.11 39385 8866 0 - 0 0 0 - - - RECEIVE
    2018-04-03 12:55:00 ALLOW TCP 192.168.0.140 192.168.0.11 39386 8866 0 - 0 0 0 - - - RECEIVE
    2018-04-03 12:55:00 ALLOW TCP 192.168.0.140 192.168.0.11 39387 8866 0 - 0 0 0 - - - RECEIVE
    2018-04-03 12:55:00 ALLOW TCP 192.168.0.140 192.168.0.11 39388 8866 0 - 0 0 0 - - - RECEIVE
    2018-04-03 12:55:00 ALLOW TCP 192.168.0.140 192.168.0.11 39389 8866 0 - 0 0 0 - - - RECEIVE
    2018-04-03 12:55:00 ALLOW TCP 192.168.0.140 192.168.0.11 39390 8866 0 - 0 0 0 - - - RECEIVE
    2018-04-03 12:55:00 ALLOW TCP 192.168.0.140 192.168.0.11 39391 8866 0 - 0 0 0 - - - RECEIVE
    2018-04-03 12:55:00 ALLOW TCP 192.168.0.140 192.168.0.11 39392 8866 0 - 0 0 0 - - - RECEIVE
    2018-04-03 12:55:00 ALLOW TCP 192.168.0.140 192.168.0.11 39393 8866 0 - 0 0 0 - - - RECEIVE
    2018-04-03 12:55:00 ALLOW TCP 192.168.0.140 192.168.0.11 39394 8866 0 - 0 0 0 - - - RECEIVE
    2018-04-03 12:55:01 ALLOW TCP 192.168.0.140 192.168.0.11 39395 8866 0 - 0 0 0 - - - RECEIVE
    2018-04-03 12:55:01 ALLOW TCP 192.168.0.140 192.168.0.11 39396 8866 0 - 0 0 0 - - - RECEIVE
    2018-04-03 12:55:01 ALLOW TCP 192.168.0.140 192.168.0.11 39397 8866 0 - 0 0 0 - - - RECEIVE
    2018-04-03 12:55:01 ALLOW TCP 192.168.0.140 192.168.0.11 39398 8866 0 - 0 0 0 - - - RECEIVE
    2018-04-03 12:55:01 ALLOW TCP 192.168.0.140 192.168.0.11 39399 8866 0 - 0 0 0 - - - RECEIVE
    2018-04-03 12:55:01 ALLOW TCP 192.168.0.140 192.168.0.11 39400 8866 0 - 0 0 0 - - - RECEIVE
    2018-04-03 12:55:01 ALLOW TCP 192.168.0.140 192.168.0.11 39401 8866 0 - 0 0 0 - - - RECEIVE
    2018-04-03 12:55:01 ALLOW TCP 192.168.0.140 192.168.0.11 39402 8866 0 - 0 0 0 - - - RECEIVE
    2018-04-03 12:55:02 ALLOW TCP 192.168.0.140 192.168.0.11 39403 8866 0 - 0 0 0 - - - RECEIVE
    2018-04-03 12:55:02 ALLOW TCP 192.168.0.140 192.168.0.11 39404 8866 0 - 0 0 0 - - - RECEIVE
    2018-04-03 12:55:02 ALLOW TCP 192.168.0.140 192.168.0.11 39405 8866 0 - 0 0 0 - - - RECEIVE
    2018-04-03 12:55:02 ALLOW TCP 192.168.0.140 192.168.0.11 39406 8866 0 - 0 0 0 - - - RECEIVE
    2018-04-03 12:55:02 ALLOW TCP 192.168.0.140 192.168.0.11 39407 8866 0 - 0 0 0 - - - RECEIVE
    2018-04-03 12:55:02 ALLOW TCP 192.168.0.140 192.168.0.11 39408 8866 0 - 0 0 0 - - - RECEIVE
    2018-04-03 12:55:02 ALLOW TCP 192.168.0.140 192.168.0.11 39409 8866 0 - 0 0 0 - - - RECEIVE
    2018-04-03 12:55:05 ALLOW TCP 192.168.0.140 192.168.0.11 39410 8866 0 - 0 0 0 - - - RECEIVE
    2018-04-03 12:55:05 ALLOW TCP 192.168.0.140 192.168.0.11 39411 8866 0 - 0 0 0 - - - RECEIVE
    2018-04-03 12:55:07 ALLOW TCP 192.168.0.140 192.168.0.11 39412 8866 0 - 0 0 0 - - - RECEIVE
    2018-04-03 12:55:11 ALLOW TCP 192.168.0.140 192.168.0.11 39415 8866 0 - 0 0 0 - - - RECEIVE
    2018-04-03 12:55:11 ALLOW TCP 192.168.0.140 192.168.0.11 39416 8866 0 - 0 0 0 - - - RECEIVE
    2018-04-03 12:55:12 ALLOW TCP 192.168.0.140 192.168.0.11 39417 8866 0 - 0 0 0 - - - RECEIVE
    Last edited by p37307; 2018-04-03 at 04:59 PM. Reason: clarified which firewall log was for each task
    ~Paul

    Setup: NextPVR, Serviio, WinTV-quadHD and WinTV-HVR-955Q. Custom Roku channel developer. Feeding Tube Advocate. About me or http://chambers.pw.

    If you haven't broken it at least once, you're not doing it right.

  3. #3
    Join Date
    May 2006
    Location
    Canada
    Posts
    28,874
    Is your PIN set correctly?

    Martin

  4. #4
    Join Date
    Jul 2016
    Location
    USA
    Posts
    227
    Quote Originally Posted by mvallevand View Post
    Is your PIN set correctly?

    Martin
    It is not the default PIN, Martin. Is it supposed to set to something specific and I missed that?
    ~Paul

    Setup: NextPVR, Serviio, WinTV-quadHD and WinTV-HVR-955Q. Custom Roku channel developer. Feeding Tube Advocate. About me or http://chambers.pw.

    If you haven't broken it at least once, you're not doing it right.

  5. #5
    Join Date
    Nov 2003
    Location
    NextPVR HQ, Wellington, New Zealand
    Posts
    90,834
    Paul, can you PM me your PIN code - I'll do the math on the other numbers in your logs, and see if it looks like it should succeed.

  6. #6
    Join Date
    Jul 2016
    Location
    USA
    Posts
    227
    Quote Originally Posted by sub View Post
    Paul, can you PM me your PIN code - I'll do the math on the other numbers in your logs, and see if it looks like it should succeed.
    done. Thanks
    ~Paul

    Setup: NextPVR, Serviio, WinTV-quadHD and WinTV-HVR-955Q. Custom Roku channel developer. Feeding Tube Advocate. About me or http://chambers.pw.

    If you haven't broken it at least once, you're not doing it right.

  7. #7
    Join Date
    Nov 2003
    Location
    NextPVR HQ, Wellington, New Zealand
    Posts
    90,834
    Paul - your numbers don't seem to match what they should, so it looks like the pin is wrong. On the server selection screen, can you do a swipe right to left on any servers you see listed, then kill the app and restart it, so that it'll auto detect the servers, and let me know if it makes any difference? If not, we'll work out next steps (probably involving wireshark capture).

  8. #8
    Join Date
    Jul 2016
    Location
    USA
    Posts
    227
    Quote Originally Posted by sub View Post
    If not, we'll work out next steps (probably involving wireshark capture).
    Done.

    I tried it with my cell phone and tablet. Same response. "Can't connect, make sure NEXTpvr is running."
    ~Paul

    Setup: NextPVR, Serviio, WinTV-quadHD and WinTV-HVR-955Q. Custom Roku channel developer. Feeding Tube Advocate. About me or http://chambers.pw.

    If you haven't broken it at least once, you're not doing it right.

  9. #9
    Join Date
    Nov 2003
    Location
    NextPVR HQ, Wellington, New Zealand
    Posts
    90,834
    Can you try using wireshark to capture the 10 seconds or so of starting the application? I can then load up the captured traffic, and see what is happening.

  10. #10
    Join Date
    Jul 2016
    Location
    USA
    Posts
    227
    Quote Originally Posted by sub View Post
    Can you try using wireshark to capture the 10 seconds or so of starting the application? I can then load up the captured traffic, and see what is happening.
    The ip for the Android is 192.168.0.140

    Sorry about all the other noise in there. I tried to reduce it but couldn't disconnect the library without screwing things up right now.

    EDIT: Deleted uploaded Wireshark capture
    Last edited by p37307; 2018-04-03 at 11:29 PM. Reason: Wireshark upload removed
    ~Paul

    Setup: NextPVR, Serviio, WinTV-quadHD and WinTV-HVR-955Q. Custom Roku channel developer. Feeding Tube Advocate. About me or http://chambers.pw.

    If you haven't broken it at least once, you're not doing it right.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •