Awaiting Duplex

[doodlleus]

It just seems to hang around on the awaiting duplex stage when trying to establish a connection. eventually it times out. this is when trying to connect from win 11 to steam deck

[slowscript]

This happens when the other side (steam deck) doesn't see your PC or can't connect to it. If your steam deck doesn't see the Windows version, you can try manually reannouncing (Main->Reannounce). If that doesn't help that means the mDNS packets are not reaching the Steam Deck - you will likely need to allow UDP traffic on port 5353 in its firewall. If your Steam Deck sees the other computer and can't connect, you will need to allow incoming connections (UDP and TCP) on port 42000 on the Windows side. Although I think Windows Firewall doesn't deal with ports and all you need is add an exception for the Warpinator.exe.

[bramnet]

I'm having the same problem. My PC can see the steamdeck, but the steamdeck doesn't see my PC. I've setup the 5353 UDP rule on both my PC and the steamdeck, but the steamdeck is still not seeing my PC.

[Decimation]

Same problem here on Windows 10. Just use adb, KDE Connect, or something similar instead in lieu.

[Deozaan]

I just had this issue (Windows 10 -> Steam Deck) and the cause (and solution) was actually described in #15.

Warpinator (on Windows) was using the wrong network adapter, and had the wrong IP address. Manually configuring which adapter to use in Warpinator's settings and then restarting Warpinator solved the problem for me.