The only thing I can think of is to assign each wired device it's own IP address that is outside of the DHCP pool. (My DHCP pool is .100 to .200 and all my wired devices have fixed ip below .100
For my wireless devices that stay in the house, I have reserved IP addresses though my router so they always get assigned the same IP address and it is tied to the devices MAC address.
I also have my DNS settings in the router set to use Google 8.8.8.8 and 208.67.222.222 instead of the DNS of my ISP.
I found most of this out when I added my NEST Thermostat and it would drop off the network for no reason at odd times and I could never figure out the exact cause, but these changes have kept it on line.
I guess you missed this on the last page..
I am also on audio3.radioreference.com.... I wonder if squadman and Chronic's feeds are also based on that server..
Yeah my streamer runs on an XP box (wiped and fresh installed specifically for this purpose), so updates/antivirus are also disabled, and I know there is no crapware/spyware/etc interfering because this machine is not used for anything else.
I have a 50/10Mbps fiber connection and an advanced network at my house.. It's a domain with its own DNS/Active Directory server, hardware firewall (pfSense on a Firebox), static IPs on everything except wifi devices - and they are pseudostatic (the DHCP server assigns pre-determined static IPs to each device based on their MACs) just to avoid issues when using them on other wifi networks. The only things that use the actual DHCP pool are like visiting family and friends and customer computers.
Our ISP runs fiber to the house (like FiOS), and there is no "modem" in a classic sense. It is straight Ethernet from the ONT on the side of the house right into the firewall.
I really hope someone who deals with the backend is checking in on this topic..