http://www.portforward.com

1. find out which ports are used by DoD
2. disable your router firewall or open the DoD ports for incoming connections
3. forwards the port(s) to the internal IP of the machine hosting the game
4. enable incoming connections for the ports used by DoD on the host machine's firewall (or disable it)
5. look up your external IP (router interface or http://www.whatismyip.com) and tell your friends to connect via the game console (command usually "connect <ip/hostname>(:<port>)")

To make connecting easier you could use a service like dyndns, so your friends only have to remember your hostname, not your (probably dynamically assigned) IP.

Not that you could've found out all of that by using Google... (;

I tried adding two lines to my Server.cfg and ListenServer.cfg files...

Not good, change back to defaults, or use the internal IP of the machine hosting the game. The game doesn't know about your external IP adress, just like Steam obviously doesn't.

also try sv_lan 0

Thanks for all of the info, but AFAIK I have the ports forwarded properly (see attached pic).

ADDiCT wrote:

5. look up your external IP (router interface or http://www.whatismyip.com) and tell your friends to connect via the game console (command usually "connect <ip/hostname>(:<port>)")

I haven't tried that yet, but shouldn't it work if I "invite" them to join the game from within the game itself (via the in-game Steam client overlay)?

ADDiCT wrote:

To make connecting easier you could use a service like dyndns, so your friends only have to remember your hostname, not your (probably dynamically assigned) IP.

Mine is static, unless I renew/release the connection.

ADDiCT wrote:

Not that you could've found out all of that by using Google... (;

I've Googled until my brain hurts <grin>.

ADDiCT wrote:

Not good, change back to defaults, or use the internal IP of the machine hosting the game. The game doesn't know about your external IP adress, just like Steam obviously doesn't.

Part of the Google results (as well as Steam's support site) said to add those lines.

leileilol wrote:

also try sv_lan 0

I just found that via Google... will have to give that a try as well.

I've never used Steam-based game to host sessions before, so I'm not sure how the "invite" feature works. But if your friends are getting your internal IP adress in the invite they're not going to be able to join. Maybe Steam can be configured to use the external IP, but anyway typing the correct IP or hostname in the console will work 100% so why bother with the invites.

I would check the DoD readme or Google for the correct ports. Mods sometimes use ports different to their "parent" game.

Mine is static, unless I renew/release the connection.

That's not "static", that's a dynamically assigned IP. If you had static you'd get the same IP all the time. Static IP usually costs extra, and isn't useful for most home users. On the contrary, it can be a security risk.

Those config lines are used to "bind" the game to a specific network adapter (make it listen on a specific adapter). You don't need these lines unless you have multiple NICs in your machine.

ADDiCT wrote:

That's not "static", that's a dynamically assigned IP. If you had static you'd get the same IP all the time. Static IP usually costs extra, and isn't useful for most home users.

A-OK, thanks for the info 😀 I had inadvertently called it static, because even though it is dynamic, it's only changed twice since we first got the broadband back in February.

I tried the "sv_lan 0" thing... same problem.

But, having my friends connect in the console via "connect <IP>:27015" (as well as adding the "<IP>:27015" to their "Favorites") worked like a champ 😀