"Couldn't connect to the remote computer"

[Oltsu]

So a week or so back in home streaming worked just fine for me. No issues at all.

However when I wanted to try it again today I couldn't get any game to work. Every time I try streaming a game I get the normal pop up on the client pc that it's starting streaming, the game then starts on the host pc, nothing happens on the client PC, and after 15 seconds or so I get a pop up on the client pc saying: "Couldn't connect to the remote computer". After this I have to go to the host computer and quit the game manually.

Same happens in big picture mode, from desktop to laptop / laptop to desktop, with latest beta version of the steam client, with the latest non beta version, with and without firewalls running, etc. Seems to happen with all configurations. Both computers are in the same lan of course with wired connections.

Desktop is running win7 x64
(4770K, Titan, latest whql NV drivers)

laptop is running win8 x64

Anyone else run into the same issues? I did find a couple of threads about people getting the same error as I get but there really weren't any solutions to be found.

[Twelve-Oh-One Alarm]

I got the exact same issue.

[Zaneak]

I am also having this issue.

[Skater]

I'm getting the same issue on a 2010 MacBook Pro running OS X Mavericks

[Wikitibah!!!]

This sounds exactly like what I was experiencing. Check out this thread:

http://steamcommunity.com/groups/homestream/discussions/0/540731690639490048/

Post #50 on down was the most helpful to me.

[Zohar]

I'm having the exact same problem. It was working before, but suddenly every time I try streaming from my desktop to my laptop it says, "Couldn't connect to the remote computer." I've tried pretty much every solution I could find in this group but still no luck.

I can, oddly enough, stream games FROM my laptop to my desktop without any problems. :/

[slouken]

Zohar, it sounds like a firewall issue on your desktop. As an experiment, can you try temporarily disabling Windows firewall?

[Zohar]

I've tried disabling the firewalls on both PCs with no luck.

[Zohar]

Originally posted by slouken:

Zohar, it sounds like a firewall issue on your desktop. As an experiment, can you try temporarily disabling Windows firewall?

As it turns out, the modem/router combo that AT&T provides with U-Verse has it's own firewall. A firewall which you cannot disable (From what I understand, they do this due to the other services (phone and TV) they offer using the same box).

The solution I found was to dig my old router out, connect it to the U-Verse modem/router and then connect my two PCs to my old router.

Works like a dream!

[Kenzie.]

Originally posted by slouken:

Zohar, it sounds like a firewall issue on your desktop. As an experiment, can you try temporarily disabling Windows firewall?

turns out it was, what are the flags i should enable in the windows firewall to stop this happening again?

[thule]

Turns out, Steam uses another process - called streaming_client.exe - as a streaming server (I know, it is named 'client'). Just allow this exe in your firewall along with main steam exe.

[DJ]

To those of you having this issue, simply click on the property of the wifi you are on. Make this pc discoverable -----------> On

[xBoB3k]

Just thought I'd post -- this just happened to me out of nowhere, and it was the firewall. Win 10 and all their obnoxious auto updates these days. Had to go in and turn the firewall off, specifically on the private network category which is what I'm set to for my home lan.

[DesertShadow]

Same issue. Restarting steam on both computers fixed it then it happened again

[ShadowDiver]

i had the same issue. but i went in my windows defender firewall and turn on some things that seemed necessary to stream it and play it on a other pc via internet and it workt

[Avogadro]

I think the latest Windows update (1903) monkeyed around with the firewall settings -- both this and Shield streaming are blocked unless I turn off the firewall on the host PC. I have made sure Steam and streaming_client.exe are excepted in firewall, and added inbound port exceptions for the UDP and TCP ports listed as required with no luck. Has anyone managed to get it working without turning off the firewall entirely?