NextPVR Forums
  • ______
  • Home
  • New Posts
  • Wiki
  • Members
  • Help
  • Search
  • Register
  • Login
  • Home
  • Wiki
  • Members
  • Help
  • Search
NextPVR Forums Public NextPVR Android Client v
« Previous 1 … 3 4 5 6 7 Next »
Cant' connect.

 
  • 0 Vote(s) - 0 Average
Cant' connect.
p37307
Offline

Senior Member

Posts: 252
Threads: 46
Joined: Jul 2016
#1
2018-04-03, 04:26 PM (This post was last modified: 2018-04-03, 11:27 PM by p37307.)
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

Quote: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
~Paul

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

Senior Member

Posts: 252
Threads: 46
Joined: Jul 2016
#2
2018-04-03, 04:59 PM (This post was last modified: 2018-04-03, 04:59 PM by p37307.)
I enabled Windows 10 Firewall logs and this is what it shows when I attempt to connect with the app from my Android
Quote:#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.
Quote:#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
~Paul

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

Posting Freak

Ontario Canada
Posts: 53,108
Threads: 957
Joined: May 2006
#3
2018-04-03, 07:41 PM
Is your PIN set correctly?

Martin
p37307
Offline

Senior Member

Posts: 252
Threads: 46
Joined: Jul 2016
#4
2018-04-03, 07:56 PM
mvallevand Wrote: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

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

Administrator

NextPVR HQ, New Zealand
Posts: 106,789
Threads: 769
Joined: Nov 2003
#5
2018-04-03, 08:09 PM
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.
p37307
Offline

Senior Member

Posts: 252
Threads: 46
Joined: Jul 2016
#6
2018-04-03, 08:26 PM
sub Wrote: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

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

Administrator

NextPVR HQ, New Zealand
Posts: 106,789
Threads: 769
Joined: Nov 2003
#7
2018-04-03, 08:45 PM
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).
p37307
Offline

Senior Member

Posts: 252
Threads: 46
Joined: Jul 2016
#8
2018-04-03, 08:58 PM
sub Wrote: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

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

Administrator

NextPVR HQ, New Zealand
Posts: 106,789
Threads: 769
Joined: Nov 2003
#9
2018-04-03, 09:29 PM
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.
p37307
Offline

Senior Member

Posts: 252
Threads: 46
Joined: Jul 2016
#10
2018-04-03, 09:53 PM (This post was last modified: 2018-04-03, 11:29 PM by p37307.)
sub Wrote: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
~Paul

If you haven't broken it at least once, you're not doing it right. :eek:
« Next Oldest | Next Newest »

Users browsing this thread: 2 Guest(s)

Pages (4): 1 2 3 4 Next »


Possibly Related Threads…
Thread Author Replies Views Last Post
  Can't connect with Android App Nvidia Shield (Solved) Fith 9 3,202 2022-12-02, 03:28 PM
Last Post: mvallevand
  Cannot connect to NextPVR from Samsung S21 Ultra DSperber 68 12,560 2021-12-30, 02:18 AM
Last Post: mvallevand
  Connect to PVR tesla1886 10 4,677 2021-05-31, 12:00 AM
Last Post: tesla1886
  Cannot connect remotely vitony 2 1,701 2020-08-02, 09:54 PM
Last Post: vitony
  Android Client wont connect joolsc 2 2,641 2020-03-16, 01:41 PM
Last Post: joolsc
  Android Client wont connect Mark-McG 12 4,973 2019-12-17, 09:20 PM
Last Post: mvallevand
  Just Purchased NextPVR android - Cant connect hdpvr-doug8796 13 5,232 2019-09-26, 07:56 PM
Last Post: hdpvr-doug8796
  Unable to Connect crackulator 6 4,212 2019-06-11, 05:51 PM
Last Post: sub
  Client sees server but won't connect Paws3307 3 2,621 2019-05-15, 08:17 PM
Last Post: sub
  Cant connect paulsavo 2 2,280 2018-12-26, 12:00 AM
Last Post: sub

  • View a Printable Version
  • Subscribe to this thread
Forum Jump:

© Designed by D&D, modified by NextPVR - Powered by MyBB

Linear Mode
Threaded Mode