Discovery Traversal through NAT / Internet Connection Sharing?

[Zathu]

My setup is unique in that I've attached my Steam PC to an Ethernet port on my HTPC utilizing Windows' Internet Connection Sharing feature. I noticed that the Steam client on my laptops do not "see" the Steam PC when it's online. I'm assuming this is because Windows' ICS uses NAT, so if it's trying to use uPNP it'll fail.

Any ideas for a workaround?

[GeeEl]

I'm not familiar with ICS.

What IP does the Steam PC get? (You can check with "ipconfig" from a command prompt.)

I'm guessing that it is using something on a 169.x.x.x range, and your regular internal network is on 192.168.x.x

I'm not sure how IHS discovery works, but my guess would be:

• Steam client A determines its own internal IP4 address (X)
  
• Steam client A registers with Steam servers as having IP X
  
• Steam client B determines its own IP4 address (Y)
  
• Steam client B registeres with Steam servers as having IP Y
  
• Steam server tells A+B about each other and they try to negotiate a connection to stream X <-> Y

If that's the case simple port forwarding in ICS (does ICS even support that) wouldn't help.

My thinking would be either MS Network bridge (for some versions of Windows Server 2003+ http://technet.microsoft.com/en-us/library/cc783558%28v=ws.10%29.aspx ) - although I have to admit TL;DR :)

You could probably also set up VPN - having a VPN endpoint on the HTPC and client on the Steam PC.