STEAM GROUP
Steam Remote Play homestream
STEAM GROUP
Steam Remote Play homestream
4,144
IN-GAME
36,839
ONLINE
Founded
November 7, 2013
All Discussions > Bug Reports > Topic Details
VincentVega Jun 27, 2014 @ 8:48am
Unable to connect - Logs showing port 0 on broadcast
Hi,

I am trying to get In-Home Steaming working but I've ran into some issues. I followed the guides and help I could find but I'm a bit stuck.

* I am on the same network/subnet.
* I disabled Windows Firewall on the host and remote computer.
* I ran netstat -ano to verify that the UDP and TCP ports were unused before launching stream on both computers.
* After launching I verified the UDP and TCP ports were mapped, and the PID was the same for all ports (that steam was able to bind)
* They are both running Windows 7
* I tried first on the GA release of Steam, opted both into beta, and tried again both clients on the same version of beta
* Rebooted many times, tried big picture, tried disabling and re-enabling streaming

When I launch and I go into the Settings for In-Home Steaming I will see my host show my client host-name and say that it is logged in as the same user but not connected. From the client I can see the host but it will say logged in as a different user. It will stay like that for a minute, and then both clear out and show nothing.

I started digging into the remote_connections.txt file in the logs directory.

On the host I see [2014-06-21 11:37:25] Received broadcast message from client <some long id> (client-name): 192.168.1.71:27036 which is what I would expect.

On the client I see:
[2014-06-21 11:37:25] Received broadcast message from client <another long id> (host): 192.168.1.50:0

Which I imagine has something to do with what is not working right.

Using netstat I validated that the host has 27036 and 27037 as LISTENING with the PID of steam correctly.

So far I've not had any luck getting any of it working :(

Thanks! I hope you can help!
< >
Showing 1-8 of 8 comments
slouken Jun 27, 2014 @ 2:51pm 
Getting a port of 0 probably means TCP port binding failed on the host. Can you see if the message "Couldn't bind TCP port" appears in the logs?
slouken Jun 27, 2014 @ 2:54pm 
Can you also make sure you're logged in and not offline on either Steam client?
VincentVega Jun 27, 2014 @ 4:22pm 
They are both logged in and not offline on both Steam clients. I did log out and back in on both to verify. It's strange that the host sees my client as logged in as the same user (but not connected) but the client sees the host as logged in as a different user (from the settings dialog).

On the host I closed Steam completely and verified (via netstat -ano) that none of the TCP or UDP ports are bound. I disabled the firewall completely. I launched Steam and I see the ports as listening with the PID tying back to Steam.

I didn't see anywhere in the logs that it could not bind. What log file should I check to be sure?

Thank you for your help! I really appreciate it!!! I'm sure I'm missing something obvious.
Kaioshi Jun 29, 2014 @ 2:08am 
I'm having this exact same problem - except I was able to connect with a Mac client over WiFi. Other LAN client sees the host as logged in as the same user, host sees that client as another user. Same client version too.

With the Mac client I didn't have to do any port forwarding or anything, it Just Worked right after install. Been messing with the other (Windows 7) client for hours and no luck.
slouken Jul 2, 2014 @ 11:48am 
Originally posted by VincentVega:
They are both logged in and not offline on both Steam clients. I did log out and back in on both to verify. It's strange that the host sees my client as logged in as the same user (but not connected) but the client sees the host as logged in as a different user (from the settings dialog).

That's very strange, I've never seen that.

Originally posted by VincentVega:
I didn't see anywhere in the logs that it could not bind. What log file should I check to be sure?

Check logs\remote_connections.txt
VincentVega Jul 3, 2014 @ 12:09pm 
Yeah nothing in the logs that it cannot bind. From netstat it seems like it's binding to the port correctly. Is there any enhanced logging capabilities?
VincentVega Jul 11, 2014 @ 6:40am 
As an update to this, it seems to be related to the router. I was using the router provided with my Uverse service, which was not working. I just upgraded to a new router (TP-Link Archer C7) and both computers immediately connected and streaming worked correctly.

I hope this is helpful to someone else!
is it possible to have virtual ip addresses/or virtual nic-s and make steam to broadcast on them all? or use multicasting?

i have same error with [not connected] but they see each other and are loged in with [same account] restarting steam solves issue... but i don't wanna restart steam on headless remote host...

it happens on same subnet sometimes...
and pretty much every time with different subnets, with and without virtual ip/nic...
Last edited by [masni] CYKA CLEANER; Jul 11, 2014 @ 8:10am
< >
Showing 1-8 of 8 comments
Per page: 1530 50

All Discussions > Bug Reports > Topic Details
Date Posted: Jun 27, 2014 @ 8:48am
Posts: 8