Works with Windows PC, but not Linux Mint PC in same network

[Dafon]

I've been trying to set up Steam Link last weekend and it immediately worked with my girlfriend's Windows 10 PC, but I can't get it to find my PC running Linux Mint 19. It's on the same network, everything connected with a network cable, and I don't have a firewall running on my PC. I can even ping the Steam Link and get a reply, yet it refuses to notice my Steam.

[madhattr]

I'm also running LinuxMint 19 on my host PC and connecting to it with steam link hardware and steam link from a pi. Hopefully some of the following may help.

As you said everything was on the same network, so we'll skip to making sure the ports are available and listening.

Check out this article to see the ports needed for steam link to connect - https://support.steampowered.com/kb_article.php?ref=4950-EBNM-7843

Did you configure a firewall on your LinuxMint PC? I'm not sure what the default iptables are, but I did not have to modify that on my setup. If you made any custom firewall settings on your LinuxMint PC go back and review those first to verify nothing will block the traffic.

Start Steam on your LinuxMint PC.

Next check to make sure the correct ports are listening. On your LinuxMint PC try running the following.

nestat -avn | egrep "27031|27036|27036|27037"

Make sure you see output has the appropriate ports and protocol listening. based on the article above.

Assuming everything looks good so far, try running nmap or some other tool to make sure you can reach the TCP ports from your Windows PC or your steam link. I don't mention UDP because that can be hit or miss, focus on the TCP ports first. Assuming you can reach those then UDP will probably be ok.

From the windows PC, run nmap/zenmap and specificy the TCP ports 27036 and 27037. Make sure that nmap or your tool reports that those ports are open and listening.

Let us know if you find anything strange or figure out the solution.

[Dafon]

Well, I have absolutely no way of explaining this so I'll just tell what happened.

I ran that netstat command, it showed both tcp and udp listening on port 27036. So I figured I'd search for computers with the Steam Link just to check and it found none.

Next I turn on the windows 10 PC, went into the Steam settings to make sure Remote Play was enabled just in case and there was my linux pc listed under the devices. Confused by this I decide to just download nmap and see if I notice anything, took me a bit to figure out how to use it but I got it to show that it is also listening on port 27036.

While figuring out how to use nmap Steam Link had gone into standby, so I pick up the controller and turn it back on, it says connecting to network and what do you know, it suddenly shows my linux PC...

I have no idea what made it work now so anyone in the future looking this up, I'm sorry

[madhattr]

Magic :)

Seriously, glad it is working and I hope it continues to work. Have Fun!

[madhattr]

I thought about this later, but there is a menu option from steam link to scan for PCs on the network. Not sure if you gave your PC enough time to boot and start steam before you scanned the first time, that may have been the issue. If it happens again try re-scanning from steam link and make sure you have given your PC long enough to boot and steam to launch.

Second thing, FYI for anyone that reads this later, don't install nmap on your work computer unless you have a reason. The tool used improperly could unintentionally cause issues on a network. Also it could be a violation of your corporate policies or even your ISP if you scan something outside of your network.

I'm not going to debate the legality of using the tool, there is already a good article they wrote up: https://nmap.org/book/legal-issues.html