This happened once on my 930E as well. Hasn't happened again... yet. If it does, I'll probably put in an USB Ethernet adapter.

Is it possible that it's creating a broadcast storm? That would explain why the rest of the network becomes unresponsive...

I have this same TV and there are random times where my ethernet network would cut out... I wonder if this is why...

More clueless about why than you are though, sorry!

I've heard of wifi bugs like this on Android tv boxes but cannot recall the solution.

Assuming you've ruled out IP conflicts, and you can duplicate it using another router or network, I'd go ahead and pursue the tv replacement route.

One thing you can try is disabling ipv6 if your tv allows. It can be buggy.

Just curious, I don't have this TV but is it possible that when your plugged into Ethernet it's still connected to wireless? Wonder if the interfaces are bridged, thus creating a broadcast storm from a loop. I would try forgetting the wireless network on the TV before plugging in.

is it handing out ip addresses to everything?

The Ethernet issues on these TVs (850/900/930) is very frustrating. Sony remains silent and offers no fix.

I’m another person who has had the same issue with a Sony TV. It was my 850D doing the same thing. I quit using it on Ethernet because it was problematic. I have since moved it to a different room where it’s on WiFi only. I am not sure exactly what fixed it since I have done several forced factory resets and disabled some of the bloatware, especially that Samba spyware crap. I suspect that it the problem was caused by the channels app and adding streaming channels to it. The problem went away when I switched to only using the channels app for broadcast channels off the antenna. I don’t know if that was the problem or only a coincidence.

Well, at this point a Shield is cheaper than a new TV. Or a Roku if you're not set on Android TV.

Check if there are network settings for wake-on-LAN and see if turning it off helps. Sounds dire though.

still sounds like an IP conflict. try exlcuding an IP from dhcp and statically assign.

Do a packet capture with Wireshark from a computer connected with crossover cable.

Set up a routing table.

From an elevated command prompt in Windows, you can use the command ROUTE.

You can see your current route table and interfaces using route print.

My VPN only connects via my mobile phones carrier and not by my WiFi. As such, I set up my routing table by:

route delete 0.0.0.0 - Gets rid of the default routes once I've connected my to my phones hotspot, as it'll usually set up two and they'll both handle it with different metrics. Metrics determine the priority of a route, the lower the number, the higher the priority.

route add 0.0.0.0 mask 0.0.0.0 192.168.44.1 if 5 - Sets up a new default route for all otherwise unhandled traffic, pointing at 192.168.44.1 (The gateway of my phones hotspot), using interface 5, which is the Bluetooth PAN device of my machine found by looking in route print.

I can then connect to VPN, delete the 0.0.0.0 route again, and re-add the route to my WiFi. Finally, I can use:

route add 192.168.0.0 mask 255.255.255.0 192.168.13.11 IF 58 - This points all traffic to a 192.168.0.X subnet to the gateway of the VPN server, using the VPN interface.

Once this is completed, all 192.168.0.X traffic is sent to the VPN server. Any other, non specifically routed traffic, is then handled by the 0.0.0.0 mask,

Although mine is primarily for my VPN, similar story applies where the traffic isn’t being controlled when you plug the Ethernet into the TV. By controlling/directing the traffic you should find it will solve your issue.

Set a reserved IP address to the TV and see if that helps.

Also maybe try turning off IPv6 on the router if it's on.

See if that helps

I have an 65X900E. Don't even bother- just get yourself a Shield. There are so many issues with the built in OS that I gave up on it very quickly.