Strange Ethernet Negotiation Issue on Nvidia Shield Pro

[rbjtech 5282]

So I have been happily using the Nvidia Shield wired Ethernet running at 1Gb for the past 5+ years, same fixed wiring etc.     However yesterday, half way though watching a movie - I get a permanent disconnection.    I check everything obvious, cabling, switch etc.   The Ubiquiti switch has blocked the port I'm using, suggesting STP - err... ok.   So I reset the port (and eventually the switch), STP resets but no joy connecting.  I try a different port - no joy.  I try a laptop on the port/shield connection - zero issues.   I conclude the Shield Ethernet port appears to be dead.  Wireless works fine.    As a last resort I then set the port to manual negotiation (1000 FX) and bingo - port/Shield springs into life with seemingly zero issues.

All very odd - how can something working for the last X years suddenly change like that - it's not a f/w issue on the shield as that has been blocked for years as I'm on (and want to stay on) SE8.

Anyway - posting this as a possible resolution for a disconnected Nvidia Shield Pro.

[vincen 71]

Hi

I would stay an Unifi update as they are quite good at pushing updates that mess things sometimes  Is your Shield being connected both at Wifi and Ethernet in same time ? I got that issue with some devices on Unifi network in past.

Vincèn

[Neminem 1515]

It sound like auto negotiation is failing.

I have seen that on some old equipment in the past, specialty if connected to a POE switch.

Not sure if that's the case here.

 

[rbjtech 5282]

On 28/11/2025 at 16:18, vincen said:

Hi

I would stay an Unifi update as they are quite good at pushing updates that mess things sometimes  Is your Shield being connected both at Wifi and Ethernet in same time ? I got that issue with some devices on Unifi network in past.

Vincèn

Possibly - but very odd why it suddenly failed.  It's been on Ethernet/Auto-Neg/DHCP reserved for years.   If I plug anotehr device into the same wall port, then it all works perfectly again - so I *think* it's the Shield itself no longer Auto-Neg, but why I have no idea.   

On 28/11/2025 at 17:50, Neminem said:

It sound like auto negotiation is failing.

I have seen that on some old equipment in the past, specialty if connected to a POE switch.

Not sure if that's the case here.

 

I guess it's possible some components may have degraded as part of the Auto-Neg process due to age 

Very odd however as the Auto-Neg happens at the OSI Data Link layer - and this was plugged in and working when it decided to 'quit' ..   I hope it holds out under manual forcing 1000FX lol ..

Edited December 1, 2025 by rbjtech

[vincen 71]

19 minutes ago, rbjtech said:

I guess it's possible some components may have degraded as part of the Auto-Neg process due to age 

I know it's a quite boring process but I would try a full factory reset of the device and see what happens ! If you plug it on a completely different switch (different manufacturer if possible, how does it go ?

[rbjtech 5282]

15 minutes ago, vincen said:

I know it's a quite boring process but I would try a full factory reset of the device and see what happens ! If you plug it on a completely different switch (different manufacturer if possible, how does it go ?

It's working as a manual speed, but it if quits completely then I'll try a factory reset 

[justinrh 259]

I would think it to be a hardware issue.  Try a new cable?  Clean the Ethernet ports?