[solved] computers can't see each other

[tikkoneus]

Just leaving this for posterity because I didn't see this solution listed anywhere else obvious. I had two computers running steam (both Win10) and they just weren't detecting each other for in-home streaming. A network capture showed no discovery packets on 27036. The trouble was that there were multiple active interfaces and steam was advertising on the wrong one! When I disabled the VMWare virtual ethernet adapter it connected instantly.

This seems like a pretty common situation. There are plenty of ways to have multiple interfaces (VPNs, virtual machines, etc.). If the steam developers are reading this my suggestion is to have a drop-down box in the in-home streaming configuration tab to let the user select which interface to look on.

[ReBoot]

So Steam is only trying one instead of all of them?

[The Hot Trout]

I'd like to bump this topic as this also solved the issue for me

Specifically I also have an extra network interface from installing virtual box on the laptop I am using as the streaming client

Repeatedly the machines would stop seeing each other, I narrowed this down to when the machine was sleeping or otherwise lost it's wi-fi connection

After disabling the VBox interface I have been able to put the client laptop to sleep and disconnect / reconnect the wi-fi and am seeing much more reliable recognition of the streaming pc

[brimu]

One more bump. With VMware Workstation 10 I had to completely uninstall to get Steam In-Home Streaming working. With VMware workstation installed a network packet capture showed the UDP packets going out to port 27036, but, they were being sent to the subnet identity address, in my case 192.168.0.0, instead of to the subnet broadcast address, 192.168.0.255. This was very strange.

I was able to also fix the issue by disabling the VMware DHCP, NAT services, disabling all VMNet network adapters and disabling the VMware Bridge Protocol within the properties of my main network adapter.

Strangely using a wifi connection didn't show the same issues, even with VMware installed.

[Kairos142]

I have been looking for a solution to this problem for months. MONTHS! Thank you OP!

[Misquoth]

Had this same issue. I hope they do something about it. Prolly won't.

[hon2a]

Thanks, @tikkoneus. I wanted to try In-Home Streaming and I was only able to get it to work by disabling the VirtualBox network adapters.

[x416C6578]

Bump, had same issue... resolved now ;)
Thanks

[HelloLeem]

Bump! Just want to say, this solved my problem! Weirdly, I have a Steam Link that had no problem connecting to my host pc, but my client laptop could not see the host.

I removed VirtualBox from both pc's and it solved the problem. I suppose I can't use VirtualBox now though....

[nick2quick]

the troubleshooting never would've lead me to this! i ensured the port was open, and from there was left mystified.

this was exactly the problem, on both ends. i use hyper-v and had a virtual networks configured. i disabled the virtual adapters and everything started to work. also had no issues on steam link, specific to pc to pc.

[robertmoon2001]

Fantastic. Thanks so much to the OP for this. Hadn't streamed in ages but happened to have installed a VM for a course a few months back. Spent the last hour trying to connect. Disabling its adapter did the trick.

[LeadPoop]

Here we are 2019, and this bug is still an issue. Disabled my virtualBox adapter and instantly, all is well.

[ohhwell0525]

Yup, just had this same exact problem as well and sure enough, disabling the virtualbox adapter did the trick.

[T-Pain]

Just to add to this - I had a similar issue with Hyper-V Virtual Ethernet Adapters (as opposed to VirtualBox specific ones) on both my host and client machines. Disabling these devices on both fixed the issue.

[Admiral]

Holy crap, this was exactly my problem too. I had VirtualBox installed, but hadn't used it in months. Solution: Going to the Windows "Network Connections" control panel, right clicking the "VirtualBox Host-Only Network" and selecting "Disable". Then I restarted Steam, and all the other machines on the network saw the computer in question.

[76561198958600324]

add me please