New feature "Local Network Game Transfer" not distributing data from PC

[Patrick Star]

Very recently the feature "Local Network Game Transfer" has been released with the latest Steam Beta update - reference: https://steamcommunity.com/app/1675200/eventcomments/3773490215223811783/?tscn=1676673909.

Unfortunately it doesn't seem to work on my setup here:
1. Steam Deck is on latest beta, as is my PC client.
2. Both logged in with same account.
3. Feature enabled to allow it for all steam friends and restarted.
4. Remote Play notification comes up when SD started, so connectivity between the clients is fine.
5. SD is connected via WLAN, PC via LAN.

Then I did following:
1. I downloaded a new game on PC via Steam Beta client, it completed just fine.
2. A few minutes later, I started download of same game on Steam Deck. Deck is however loading it from Steam CDN, not from my PC. That's odd and I'd have not expected this behavior.
3. I have verified it by checking 1) internet usage, 2) that my PC is not sending any traffic to my SD.

Important note: Steam Deck and PC are on different subnets on my setup (because LAN and WLAN), but they do have network connectivity between each other as the working Steam Remote Play feature proofs. (I can see the notification Steam Deck coming online and is available for streaming once turned on)

[martino]

Right now this only works if they are on the same subnet, the Steam RemotePlay feature uses messaging through our backend to discover the other device.

[Patrick Star]

Ah, I see. That's good to know - thank you very much for the very, very quick confirmation!

The release notes were just mentioning "local area network" and not specifically the requirement of having it in the same subnet. Might be worth adding.

I'd have assumed RemotePlay using multicast/broadcast to discover the other devices, but apparently I was wrong.

Any workarounds in getting both clients to know each other by e.g. specifying the IPs/DNS on both clients manually (in some hidden, magical config files)?

[martino]

We do use broadcast pings to discover devices, but also use discovery across subnets using our backend. It's definably worth looking into support transfers across connected subnets.

[jvyden]

I have a similar configuration as Patrick, Deck on WLAN subnet and a Linux desktop on LAN subnet.

I also have a Windows desktop on the same LAN subnet on a different Steam account but I couldn't get that to work, either. Other than being on a different OS and account, configuration is the same. Same subnet, both are on beta, both are configured to allow downloads are configured to receive from any user.

I'm experienced with tools like Wireshark to assist in debugging if it comes down to needing packet captures, haha

[martino]

We log peer connection details in "C:\Program Files (x86)\Steam\logs\content_log.txt", look for keyword "peer" on both client and server device. Feel free to forward me ([e-mail]) the log with a description of your network setup.

[jvyden]

I've sent the logs. Let me know if you never got my email.

[Patrick Star]

Did another clean reproduction, and cleaned logs before doing so. Also sent further details and logs your way, @martino. Thank you very much for your help!

[idropshot]

Have yet to actually use my Steam Deck (waiting for the right time?), but just want to commend and echo the others' voice on how great it is that support and help is here for when issues arrive and that bugs seem to be getting fixed and pushed out every day.

Thank you.

[jvyden]

My bug with game transfer not working across computers on different steam accounts was resolved; for those reading who also had this issue, try now. There was a backend issue according to Martin.

[Herr Orange]

Originally posted by martino:

We do use broadcast pings to discover devices, but also use discovery across subnets using our backend. It's definably worth looking into support transfers across connected subnets.

Can you help me out with required ports for the feature to work? I've been trying to use it between my machine (Linux-based) and my Wife's (Windows 11-based) and it only works from Win 11 -> Linux, but not the other way around. I'm guessing I need to open few additional ports. I can see it's appearing as trying to serve the files, but no actual transmission happening.

[martino]

it's using port 27040. check you logs\content_log.txt on both machines for keyword "peer", maybe you see related errors.

[Herr Orange]

Originally posted by martino:

it's using port 27040. check you logs\content_log.txt on both machines for keyword "peer", maybe you see related errors.

Perfect, that worked! Would be great if you can add it to the feature page.

[Arik ⌃🔥]

I cannot get it to work in my setup.

my isp requires my devices to have static IP of form: xxx.xxx.YYY.xxx, where YYY is unique for devices. So I am guessing the reason for the feature not working is the subnet mismatch?

The devices seem to detect each other just fine for remote play but not for transfers. Both of them are on windows. "logs\content_log.txt" doesn't seem to contain anything with the "peer" keyword.

[ک∂𝓡∂ƈعŋ •̪̀͡●]

Hi, When pressing download button on my Steam Deck, the desktop screen does flip to the 'Hosting Network Transfer' ribbon showing the game, however, the transfer speeds are all zero and the Steam Deck remains downloading straight from the Steam servers.

I also added separate Firewall service rules in the router to allow Port 27040 inbound/outbound.

Desktop PC is on the same LAN/WAN as the Steam Deck.

Checked the logs and this is what i see...any ideas why I cannot transfer locally?


[2023-04-28 00:52:22] Finished peer content server job for AppID 1227530 : 0 chunks requested, 0 chunks sent ( 0 bytes )
[2023-04-28 00:53:07] Initialized peer content server for AppID 1227530
[2023-04-28 00:53:07] Initialized peer content server for AppID 228980
[2023-04-28 00:53:07] AppID 1227530 state changed : Fully Installed,Peer Server,
[2023-04-28 00:53:07] AppID 228980 state changed : Fully Installed,Peer Server,

[alamoscouts]

The feature is a mess across the board; even from PC to PC the transfer will fail 9/10; better off using nitroshare to move it to target PC and then have steam detect the files.