Forced Connection Closure - Win7

 

Hi all,

 

I'm running this on Win 7 64bit. I have python 2.75 and my ATV3 is on 5.2.1 my Plex server is 0.9.7.22.511-4b5280f

 

My log file is here: http://pastebin.com/Nh8JDPPX

 

 

It looks like I'm almost configured correctly, but I must be missing something as something is forcing the connection to close. (Errno 10054)

 

Any ideas?

 

Edit: I also realized that by setting my DNS manually it disables Netflix on this ATV. Once I get all of this running is there a way to get Netflix running again?

I'm also having the same issue, but I am running an ATV2 (720p).

All other variables (OS, Python, Plex server) all the same.

EDIT: I have a slightly different output in my log file:

http://pastebin.com/CBriSWuJ

Same exact issue with Windows 2012

>>  I also realized that by setting my DNS manually it disables Netflix on this ATV. Once I get all of this running is there a way to get Netflix running again?

Once you have PlexConnect running OK, your aTV feature are the same. Well, minus Apple Trailer, plus Plex.

weborder2003:

>> DNSServer : forward other to higher level DNS: 10.0.1.9

...

>> DNSServer : Source: ('10.0.1.9', 51039)

10.0.1.9 is your aTV, isn't it? Then is CAN NOT be the DNS IP to forward to - the one that originally was 8.8.8.8

Guys please stop jumping in other people’s threads saying you have the same issue when you have different configurations and different or no log files.

Start your own thread and provide the info requested in the sticky at the top of the forum, without this you may not get any support.

weborder2003:

>> DNSServer : forward other to higher level DNS: 10.0.1.9

...

>> DNSServer : Source: ('10.0.1.9', 51039)

10.0.1.9 is your aTV, isn't it? Then is CAN NOT be the DNS IP to forward to - the one that originally was 8.8.8.8

How do I fix that? I set the ATV manual DNS to the IP of my Win7 machine.  The settings.py needs the ATV iP plugged in where it was 8.8.8.8 correct?

No, the ATV IP is discovered by Plexconnect automatically. Leave the 8.8.8.8 DNS alone unless you are using a DNS service like UnBlockus.

 

I tried running the script again and got a new forward IP. The full output is here: http://pastebin.com/edit.php?i=YHiAt8q3

DNSServer : DNS request received!
DNSServer : Source: ('218.27.207.249', 40853)
DNSServer : Domain: ripe.net
DNSServer : ***forward request
 
Where is it pulling this source from? 

No, the ATV IP is discovered by Plexconnect automatically. Leave the 8.8.8.8 DNS alone unless you are using a DNS service like UnBlockus.

Oh, I thought the setup instructions said to change that to the IP of your ATV. 

No, the ATV IP is discovered by Plexconnect automatically. Leave the 8.8.8.8 DNS alone unless you are using a DNS service like UnBlockus.

Well, I thought it was fixed and I can see my library now. However when I try to play something I get "Trailers is unavailable. Try again later." so I guess I still have a bit more work to do. 

Your post got me all that much closer! Thanks!!

EDIT: Scratch what I wrote. All is well. The error was coming from one TV show in particular so it must be something in my library. Everything else I tested seems to work just fine. Yay!

Well, I thought it was fixed and I can see my library now. However when I try to play something I get "Trailers is unavailable. Try again later." so I guess I still have a bit more work to do. 

Your post got me all that much closer! Thanks!!

EDIT: Scratch what I wrote. All is well. The error was coming from one TV show in particular so it must be something in my library. Everything else I tested seems to work just fine. Yay!

See the sticky at the top of the forum about issues with some content and a workaround.

See the sticky at the top of the forum about issues with some content and a workaround.

Thanks! I will check that out.

How is this answered?? The setting is there to be changed and I needed too but get this error.

How is this answered?? The setting is there to be changed and I needed too but get this error.

It is answered for the op.

You claim to have the same issue so:

- either you do not

- you have not bothered to read the answer

If you want help please start your won thread with all of the information requested in the 'read before posting' sticky.

It is answered for the op.

You claim to have the same issue so:

- either you do not

- you have not bothered to read the answer

If you want help please start your won thread with all of the information requested in the 'read before posting' sticky.

No need to be hostile....I read and understood the answer. I am using Unotelly and it is set in my router so I need to use my router as the DNS setting. The error keeps coming back.

While I completely appreciate your fantastic work I think your comment was uncalled for. You don't mind having different thread about the exact same error? I didn't post the log since it was exactly the same.

I wasn't trying to be nasty but factual.

You do not need to use your router as the DNS server.

Set the DNS server to the Unotelly IP.

You do not need to use your router as the DNS server.

Set the DNS server to the Unotelly IP.

I could but it's already set in the router as I also have a Roku plus it's easier. Is there a reason why this method would work better?

I just updated  too but was running your first version previously.

In theory both should work but you might as well see what happens.

Also make sure that you do not just swap out the settings.py file, the format and contents of it have been changed.