Steam Link (Hardware) - Works via WiFi but NOT wired

[Yoster]

Experiencing a strange issue with my Link (Hardware version). When connected via wifi, it sees my PC (which is hardwired) just fine and can connect with it. Performance isn't the best though due to the wireless network on the steamlink end.

So, instead, I connect the steamlink via ethernet to the router. The Steam Link "sees" the PC just fine, can do a streaming test to it and everything. When I go to "connect" - my PC goes right into big screen mode no problem and says its "streaming to steamlink". The TV (with the steamlink) goes black and says it's connecting. Sits there for about 15 seconds, then kicks BACK to the steamlink screen where it shows available PC's to connect to.

Any ideas? I've tried all mix of settings. And very randomly.. unplugging the ethernet from the steamlink, bamo, it works fine. I don't get why the wired connection would be having problems, especially when it passes the streaming network test to the host PC just fine.

[_I_]

is windows network set to private? not public

try a factory reset on the link and pair it with the host again
it may not be updating the ip correctly when connecting to lan from wifi

[Yoster]

Yes host computer is on private - also has no problem streaming to any other computer or steam link app in the house.

It's just for some reason this steam link hardware version refuses to work when on Ethernet, again despite it passing the connectivity test with flying colors. Tried a system reset but no dice.

[Yoster]

Update: discovered that disabling network prioritization on host settings fixed it. Odd because having that option enabled usually helps me, but oh well. Fixed and happy.

My guess is that since, with steamlink on wifi, it was going *direct* to the wireless AP that the host PC was wired into, there was no issue. When the steamlink was hardwired however, I had it jumping through a few switches and wired access points before it got to that same AP. All the connections along the way support network optimization technologies, but there must have been some conflict somewhere along the path, which I guess only manifested itself once actually loading into the host PC, but not when performing connection tests.