ATV lost internet link after port forwarding

Dev Community Apps & Creations
1
ATV: 3
ATV DNS server: 192.179.1.2
PMS and PlexConnect: Installed on iMac running OSX 10.8.4, with DCHP reserved IP of 192.179.1.2
PMS: 0.9.8.4.125-ffe2a5d that was downloaded 19 Aug 2013
 
Settings.cfg file contents:
[PlexConnect]
port_pms = 32400
enable_plexgdm = True
ip_dnsmaster = 8.8.8.8
ip_webserver = 0.0.0.0
loglevel = Normal
enable_dnsserver = True
ip_pms = 192.168.1.2
port_webserver = 80
 
PlexConnect.log contents:
09:37:08 PlexConnect: started: 09:37:08
09:37:08 PlexConnect: ***
09:37:08 PlexConnect: PlexConnect
09:37:08 PlexConnect: Press ENTER to shut down.
09:37:08 PlexConnect: ***
09:37:08 Settings: add section PlexConnect
09:37:08 Settings: add option port_pms=32400
09:37:08 Settings: add option enable_plexgdm=True
09:37:08 Settings: add option ip_dnsmaster=8.8.8.8
09:37:08 Settings: add option ip_webserver=0.0.0.0
09:37:08 Settings: add option loglevel=Normal
09:37:08 Settings: add option enable_dnsserver=True
09:37:08 Settings: add option ip_pms=192.168.178.10
09:37:08 Settings: add option port_webserver=80
09:37:08 PlexConnect: IP_self: 192.168.1.70
09:37:08 PlexConnect: started: 09:37:08
09:37:08 PlexGDM: ***
09:37:08 PlexGDM: looking up Plex Media Server
09:37:08 PlexGDM: ***
09:37:09 PlexGDM: servers discovered: 1
09:37:09 PlexConnect: PMS: 192.168.1.70:32400
09:37:09 DNSServer: started: 09:37:09
09:37:09 DNSServer: ***
09:37:09 DNSServer: Starting up.
09:37:09 DNSServer: intercept trailers.apple.com: 192.168.1.70
09:37:09 DNSServer: forward other to higher level DNS: 8.8.8.8
09:37:09 DNSServer: ***
09:37:09 WebServer: started: 09:37:09
09:37:09 WebServer: ***
09:37:09 WebServer: WebServer: Serving HTTP on 0.0.0.0 port 80.
 
WORK COMPLETED TO DATE
I recently purchased ATV and installed PMS and PlexConnect. ATV works fine (other than Trailers) if IP DNS set to automatic. PMS contains some content and MyPlex seems to work fine locally. Trying to get PlexConnect to install on ATV. So far then I've configured router to reserved IP address 192.168.1.2 and changed IP DNS on ATV (I'm using wireless internet). Also forwarded port to 32400 on router and actioned manual mapping to 32400 in MyPlex. Also edited ip_pms in settings.cfg file to 192.168.1.2. If relevant then I also run Dropbox but have closed app in effort to minimize potential challenges (may use port 80).
 

PROBLEM
If set IP DNS to 192.168.1.2 (machine running PMS / PlexConnect) then ATV does not receive any internet signal ... no Trailers or other content. Also, I'm a bit confused about port 32400 vs port 80.

 

Any guidance welcomed.

2

Oops just spotted a couple of typos in my note. Any reference to 192.179.1.2 should mean 192.168.1.2.

3

Maybe you are having issues getting to the google DNS server. In the settings.cfg file change dns master to your isp’s DNS server instead of googles 8.8.8.8

4

plex connect thinks your mac's IP is .70 not .2 so either you are not staticly set or you have two connections on your mac that are connecting at once.  (IE wifi and LAN)

5

Thanks, I'll try ISP DNS this evening. Interesting re Plex Connect .70 and poss confusion. I believe that IP address of mac ended .70 before i reserved IP address on router. On review of output from router then IP address ending .70 is not used by any devices. Could an 'old' (i.e. few hours ago) IP address cause challenges? Today I have rebooted all relevant devices to clean caches.

6

If you rebooted your machine then there is no way that plex would still think it's the old IP, so either A: you still are using the old IP, or B: you are still using the old IP :)

7

Hmmm, you're clearly a multiple choice examiner. At the risk of quoting a fish then I feel like Dora from the film Finding Nemo ... 'I know this one, I know this one...' :).

I just restarted mac and repeated consol log. still shows .70 as before. ugh. I understand issue but alas rather befuddled as to how it is possible.

If I view my mac Network preferences then it clearly states 192.168.1.2 and shows zero other network connections (indeed nice big red 'not connected' signs on everything other than wifi).

If I view my router information (that shows all active IP addresses) then .70 IP address does not appear.

I don't see any settings in Plex that relate to this.

Would an Airport Express, used as an extender to Airport Extreme, cause complications? I have my express situated adjacent to atv. I struggle to see how impacts mac (i.e. machine with PMS/PC) ip address but clearly missing something here.

Earlier, when rebooting atv, I turned off for perhaps 30s each time (I read somewhere 10s enough). I'll try and turn off atv for longer period before reboot. no downside.

Ideas and inspiration welcomed. Thanks, I appreciate it.

8

In case relevant, gulp, earlier log recorded when ATV DNS was set to automatic (I switched it back from manual as not working). Just changed ATV DNS back to 192.168.1.2 (same as mac) and, as before, ATV unit does not function at all.

Consol log:

11:26:37 DNSServer: DNS request received!
11:26:37 DNSServer: Source: ('192.168.1.97', 53159)
11:26:37 DNSServer: Domain: time.apple.com
11:26:37 DNSServer: ***forward request
11:26:37 DNSServer: -> DNS response from higher level
11:26:37 DNSServer: DNS request received!
11:26:37 DNSServer: Source: ('192.168.1.97', 60111)
11:26:37 DNSServer: Domain: data.iana.org
11:26:37 DNSServer: ***forward request
11:26:37 DNSServer: -> DNS response from higher level
11:26:37 DNSServer: DNS request received!
11:26:37 DNSServer: Source: ('192.168.1.97', 62810)
11:26:37 DNSServer: Domain: ax.init.itunes.apple.com
11:26:37 DNSServer: ***forward request
11:26:37 DNSServer: -> DNS response from higher level
11:26:38 DNSServer: DNS request received!
11:26:38 DNSServer: Source: ('192.168.1.97', 54051)
11:26:38 DNSServer: Domain: itunes.apple.com
11:26:38 DNSServer: ***forward request
11:26:38 DNSServer: -> DNS response from higher level
11:26:38 DNSServer: DNS request received!
11:26:38 DNSServer: Source: ('192.168.1.97', 64199)
11:26:38 DNSServer: Domain: mesu.apple.com
11:26:38 DNSServer: ***forward request
11:26:38 DNSServer: -> DNS response from higher level
11:26:39 DNSServer: DNS request received!
11:26:39 DNSServer: Source: ('192.168.1.97', 57590)
11:26:39 DNSServer: Domain: p42-buy.itunes.apple.com
11:26:39 DNSServer: ***forward request
11:26:39 DNSServer: -> DNS response from higher level
11:26:39 DNSServer: DNS request received!
11:26:39 DNSServer: Source: ('192.168.1.97', 52601)
11:26:39 DNSServer: Domain: local
11:26:39 DNSServer: ***forward request
11:26:39 DNSServer: -> DNS response from higher level
11:26:44 DNSServer: DNS request received!
11:26:44 DNSServer: Source: ('192.168.1.97', 56357)
11:26:44 DNSServer: Domain: init.itunes.apple.com
11:26:44 DNSServer: ***forward request
11:26:44 DNSServer: -> DNS response from higher level
11:26:44 DNSServer: DNS request received!
11:26:44 DNSServer: Source: ('192.168.1.97', 57591)
11:26:44 DNSServer: Domain: init-p01st.push.apple.com
11:26:44 DNSServer: ***forward request
11:26:44 DNSServer: -> DNS response from higher level
11:26:44 DNSServer: DNS request received!
11:26:44 DNSServer: Source: ('192.168.1.97', 61770)
11:26:44 DNSServer: Domain: configuration.apple.com
11:26:44 DNSServer: ***forward request
11:26:44 DNSServer: -> DNS response from higher level
11:26:44 DNSServer: DNS request received!
11:26:44 DNSServer: Source: ('192.168.1.97', 51263)
11:26:44 DNSServer: Domain: 49-courier.push.apple.com
11:26:44 DNSServer: ***forward request
11:26:44 DNSServer: -> DNS response from higher level
11:26:45 DNSServer: DNS request received!
11:26:45 DNSServer: Source: ('192.168.1.97', 60875)
11:26:45 DNSServer: Domain: pd-st.itunes.apple.com
11:26:45 DNSServer: ***forward request
11:26:45 DNSServer: -> DNS response from higher level
11:26:56 DNSServer: DNS request received!
11:26:56 DNSServer: Source: ('192.168.1.97', 59479)
11:26:56 DNSServer: Domain: trailers.apple.com
11:26:56 DNSServer: ***intercept request
11:26:56 DNSServer: -> DNS response: 192.168.1.70
11:29:09 DNSServer: DNS request received!
11:29:09 DNSServer: Source: ('192.168.1.97', 57875)
11:29:09 DNSServer: Domain: bookkeeper.itunes.apple.com
11:29:09 DNSServer: ***forward request
11:29:09 DNSServer: -> DNS response from higher level
11:29:10 DNSServer: DNS request received!
11:29:10 DNSServer: Source: ('192.168.1.97', 57117)
11:29:10 DNSServer: Domain: upp.itunes.apple.com
11:29:10 DNSServer: ***forward request
11:29:10 DNSServer: -> DNS response from higher level
11:31:38 DNSServer: DNS request received!
11:31:38 DNSServer: Source: ('192.168.1.97', 61786)
11:31:38 DNSServer: Domain: a97.gi3.akamai.net
11:31:38 DNSServer: ***forward request
11:31:38 DNSServer: -> DNS response from higher level
11:39:45 PlexConnect: Shutting down.
11:39:48 DNSServer: Shutting down.
11:39:49 WebServer: Shutting down.
9

On review of my router then 192.168.1.97 (noted above quite a few times) appears to the IP address of the ATV.

10

tbh I have no idea how an airport running as a wireless repeater could give incorrect IP information, here's a question for you, which one of these urls work for you?  http://192.168.1.2:32400/web/index.html  or http://192.168.1.70:32400/web/index.html   If the .2 does actually work then in the plexconnect settings.cfg file you can change enable_plexgdm=true to false. restart plexconnect and see if it will connect to plex server still.  

11

hi. the first weblink - that ends 1.2 works successfully and access plex server. the second weblink does not work.

changed pms settings file and restarted PMS. first weblink still works and connects to plex server successfully.

12

ok well that's good, and yet when you change your atv to use .2 for dns you say trailers app doesnt work is that correct?  

13

hi, yes that is correct. when i use .2 dns on atv then neither trailers app nor any other internet service (e.g. netflix) function. i had an idea and changed atv dns setting and my mac ip to .70 but that did not work either. when set to automatic then atv dns self-configures to 192.168.1.254 - the ip address of router.

14

tbh I have no idea, you can see in your logs the atv is requesting information you are not running any beta software on your atv are you?

15

First post...

>>So far then I've configured router to reserved IP address 192.168.1.2...
What does that mean?

Also, your Settings.cfg file and the given Log are contradictory - according to the Log, PlexConnect creates NEW settings from its defaults, not reading anything from your cfg file.

I would like to get a fresh report of your issue

- information on you environment (IPs and such, like in "How to report an issue")

- current Settings.cfg

- fresh log

...and a quick guidance on what is not working. Is it still "aTV has no access to internet"?

16

Monsieur Latte, no - atv has no beta or other software.

Baa, no problem. 'So far then I've configured router to reserved IP address 192.168.1.2' was intended to mean that (as I believe suggested in Plex forums) I entered DHCP Reservations of router and mapped the MAC address of my mac computer (that is running PMS/PlexConnect) to a fixed IP address (192.168.1.2). On my router then I (again I believe suggested in Plex forum) entered port forwarding settings of my router and mapped port 32400 (TCP and UDP) to IP address 192.168.1.2. I hope that this is clearer.

Here's a full recap, as per how to report an issue, with current file content.

ATV model 3. ATV firmware 5.3 (1605). ATV was purchased a few days ago and firmware updated so presumed current.

DNS on ATV: 192.168.1.2 (set manually on wireless)

Device running PMS/PlexConnect is a recent iMac running OSX 10.8.4 (current)

Local IP of device running PMS is 192.168.1.2 (having been so set via DHCP Reservations). I confirm this IP address in show in Preferences/Network settings on mac.

PMS version 0.9.8.4.125-ffe2a5d that was downloaded and installed a few days ago

Local IP of device running PlexConnect is 192.168.1.2 (being the same device/mac that is running PMS)

PlexConnect version: I followed advice stated per https://github.com/iBaa/PlexConnect/wiki/OSX-and-ATV-with-5.2-firmware-and-ethernet-internet-connection-installation-guide and downloaded PlexConnect a few days ago. I do not see a version number. Files in PlexConnect folder appear to have dates of either 21 June 2013 or today/yesterday.

Settings file contents

[PlexConnect]
port_pms = 32400
enable_plexgdm = False
ip_dnsmaster = 75.153.176.9
ip_webserver = 0.0.0.0
loglevel = Normal
enable_dnsserver = True
ip_pms = 192.168.1.2
port_webserver = 80
 
Detailed description of issue (pre-PlexConnect): I recently purchased ATV 3. ATV has not been jailbroken or had any other modifications. Prior to PlexConnect then setup of ATV was successful and standard apps (Netflix, ...) worked successfully. Setup of Plex was successful and initial video files accessible in Plex library. PMS application preferences show that I am signed in and that MyPlex server is mapped to port 32400. I note that Plex library can be accessed through PMS application (seems to connect to http://127.0.0.1:32400/web/index.html) but that library is also accessed through http://192.168.1.2:3.../web/index.html (thanks to Monsieur Latte's advice). Currently, if I set my ATV DNS settings to Automatic then ATV apps (other than Trailers/PlexConnect) work successfully. 
 
Detailed description of issue (post-PlexConnect): With ATV and Plex working independently then I thought install PlexConnect to enable ATV Trailers app to access my Plex library. As I believe as outlined in Plex docs then I actioned three steps: a) set IP of device running PMS/PlexConnect to a fixed IP address in the DHCP Reservations settings of my router; b) setup port mapping of PMS device IP address to port 32400 (and clicked related box in MyPlex settings); and c) Changed DNS settings in my ATV to be the IP address of the device that is running PMS/PlexConnect. This setup seems unsuccessful. ATV appears to receive no internet connection and no ATV applications (Netflix, Trailers, ...) are operating successfully.
 
Based on advice above then I changed settings.cfg file ... ip_dnsmaster from 8.8.8.8 to the IP address of my ISP, and enable_plexgdm from True to False, and ip_pms to the IP address of the device running PMS/PlexConnect.
 
Monsieur Latte has been wonderfully tireless in his assistance but, at this time, the setup does not work.
 
Conscious post now quite long so will copy PlexConnect.log file in separate post.
17

Hmm, time for a dumb question ... how do I know if PlexConnect is running on my mac device? (I can see PMS is running).

PlexConnect.log file seems to have been last modified yesterday morning, despite various efforts yesterday ... indeed I am uncertain if original log file (and hence Monsieur Latte's keen spot of .70 IP address) was before I changed PMS device IP address to 192.168.1.2.

After I quit PMS; change settings to High; open PMS and then look at PlexConnect.log file then nothing has changed. I saved the downloaded PlexConnect folder/files in the Applications folder of my mac. Was I supposed to placed this content in another location or otherwise actioned it?

18

Hmm, time for a dumb question ... how do I know if PlexConnect is running on my mac device? (I can see PMS is running).

PlexConnect.log file seems to have been last modified yesterday morning, despite various efforts yesterday ... indeed I am uncertain if original log file (and hence Monsieur Latte's keen spot of .70 IP address) was before I changed PMS device IP address to 192.168.1.2.

After I quit PMS; change settings to High; open PMS and then look at PlexConnect.log file then nothing has changed. I saved the downloaded PlexConnect folder/files in the Applications folder of my mac. Was I supposed to placed this content in another location or otherwise actioned it?

Well if you are running it via terminal you should see everything scrolling by in terminal, are you not leaving terminal open when using plex connect?

19

In case useful, when I downloaded PlexConnect then I followed procedures outlined per https://github.com/iBaa/PlexConnect/wiki/OSX-and-ATV-with-5.2-firmware-and-ethernet-internet-connection-installation-guide

After the terminal commands then, as expected per instructions, then it appeared that PlexConnect started running.

Yesterday I rebooted the mac that is running PMS/PlexConnect a couple of times, to potentially help efforts, but I did not repeat terminal stuff each time.

Monsieur Latte - To answer Q then no, I do not currently have terminal open continually. I actioned the Terminal app and actioned PlexConnect commands at time of installation of PlexConnect. Do I need to re-action launch of PlexConnect in terminal each time I restart the device that is running PlexConnect, and keep Terminal open at all times?

20

The Terminal Window is Plexconnect. 

Without it running you would get exactly what you are seeing, no internet access, no plex on trailers etc.