@Riley_S Thank you for the response and suggestions.  
 

I previously changed the AppleTV DNS settings from auto to custom and entered 8.8.8.8 (Google), but still does the same thing. 😔

I don't know what you mean by, "Also set an IP reservation in the Deco App when using a static address." or the steps necessary to accomplish this.

Thanks

  @DavidMebaneNC,

You might also consider changing the DNS settings for the entire network, not just using a custom DNS for the Apple TV. 

Your IP Address is normally something like 192.168.xx.xxx.

A Static Address set on a device will only allow the device to connect to the network with a specific address. (typically, your devices will automatically get an address assigned by your router)

An IP Reservation set on your network will prevent your network from handing out the address to another device, causing an IP conflict. Without a static address on the device, the device will only be assigned the IP set in the IP Reservation settings due to the reservation associating the devices MAC Address Identifier with an IP.

Those threads indicate that they moved their Apple TV's Network IP Settings from Automatic (DHCP) to Static to fix the problem.  The corresponding IP Reservation is then made in the Deco App to set aside that address for the Apple TV - preventing future conflicts.

FAQ: How to Configure Address Reservation on Deco Networks

  @Riley_S what's odd is I downloaded the Deco App and it's asking to setup WiFi deco devices which I don't have nor use. 😔

  @DavidMebaneNC,

Apologies for the lateness, things have been more than hectic around here.

My MistakeThe Deco app is for our Deco Mesh Networks, and the Tether App would be for our Archer Routers. You can create a reservation in your WebUi with an Archer and may be the easiest way forward: How to Configure Address Reservation on an Archer Router

  @Riley_S thank you!

I believe I did this as the post suggested.  However, I'm still having the same issue.  Was I supposed to create a new number to be assigned, or select the AppleTV from my list of wired clients, which is what I did.  
 

The post doesn't specifically say the purpose of this action, and what it does beside the obvious.  Pardon my ignorance, just trying to get a hold of this dilemma.
 

It's so frustrating to see this only happen with my Amazon streaming app and only with this router. I have WiFi completely disabled.  
 

I use Google mesh system and I'm wondering if I should "reserve" an address for it since its main puck acts as a router to feed the other WiFi mesh points. Perhaps this router (which is connected to the Archer via the TP-Link 2.5gbps switch may be causing an issue because it's a router connected to the Archer router)?
 

Again, this same configuration works with the router provided by Lumos. However, their router has one 2.5 WAN and four gigabit ports out. I'm receiving 2gbps from Lumos which is why had to purchase the TP-Link setup (router & switch).
 

I'm sooooo mentally exhausted 😩 

Thank you for your valued and humbly appreciated customer support. 👍🏻👍🏻

  @DavidMebaneNC,

Pretty sure you actually have a good grasp of where the problem will lie. 

It is not possible to run two routers on a network, without going through some advanced configuration. Normally the behavior affects the device's connection as a whole, but individual services may be affected if they make multiple requests through your network.

Solutions are to use your Google Mesh in AP Mode, or Bridge the Connection of the Router.

I am not sure what options Google offers, however, you should see if they offer an AP Mode. Based on this thread, the Googles may need to be at the head of your network(depending if it is google mesh or nest wifi); but I will check with our team for other verified setups.

It is likely that the Lumos router was functioning in a bridge mode by default or allowed for an IP passthrough, that is why the sudden swap is making such an affect.

--

Creating the IP Reservation basically makes a permanent unchanging router for your data to pass through. In the analogy of an IP address being a physical street address. IP reservations can be seen as a tenant moving from a rental agreement to a mortgage - meaning it is likely that they will be there for awhile and their street address wont change until they move out.

Unless configured incorrectly, creating a reservation is a very lightweight setting and can only help with some routing issues. Feel free to create that node reservation for stability, but I do not think that this will cause a problem due to the Archer being able to assign IP addresses to the nodes since they are the first step.

Static Addresses are similar, but are set at a device level, instead of a network level. Almost as if there is a squatter in a property saying "No, I live at this address" even though your router lists another device at that address - potentially causing a conflict in a different way.