Hi all,
Of late I’ve had some buffering issues when using my roku 3. All my content is stored locally in mp4 format so direct plays. Roku is hardwired to router and PC connected via wifi.
The setup has always worked flawless but recently I had some buffering issues. I also have my atv 3rd gen connected via wifi to plexconnect. If I close plexconnect the buffering seems to stop. I’ve attached a Screenshot of my plexconnect window. Is it normal for all these DNS requests to be showing? I have no idea what they are if I’m honest so apologies if it’s a stupid question.
The atv has been off all day so why is this showing? Is this causing network congestion of some kind or taxing the PC majorly which could cause the buffering?
Thanks up front guys.
Gesendet von iPhone mit Tapatalk
Those requests are all from the same source IP and it’s an internal address, and given is only every 30 mins or so I can’t see it causing this type of issue.
Yeah they are only every 30 minutes on this occasion but the other day when I was having issues they were every few minutes. Any idea why it’s happening?
Gesendet von iPhone mit Tapatalk
This is normal ATV chatter, the ATV checks in to Apple often. To diagnose the issue when you had the problem, we would need a log from that time. Otherwise just guessing.
You don’t have port 53 open in your firewall? Or the Plexconnect box in a DMZ?
This is normal ATV chatter, the ATV checks in to Apple often. To diagnose the issue when you had the problem, we would need a log from that time. Otherwise just guessing.
You don't have port 53 open in your firewall? Or the Plexconnect box in a DMZ?
Ok thanks. Had never seen it before so wasn't aware it was normal. I'll have to check port 53 but I don't know what a DMZ is sorry.
Gesendet von iPhone mit Tapatalk
A DMZ is a config on your router, that means its not covered by the NAT firewall, so all ports are exposed to the internet, and this allows hackers to use the DNS server that Plexconnect includes. As I mentioned this is why we would need a logs form when the issue occurred to see if this is actually happening.