21 Jan 11, 11:04AM
Most routers distributed by ISPs do not know how to handle this scenario.
Your local PC tries to contact your remote IP (WAN/iNet) and the router is supposed to DNAT it, but it's local, and yet remote .. the router is plain confused.
Simple fix: just add your LAN-IP of the box running the server and you'll see it show up in the serverbrowser :-)
You can also always simply do "/connect 192.168.123.123" (with correct LAN IP).
Your local PC tries to contact your remote IP (WAN/iNet) and the router is supposed to DNAT it, but it's local, and yet remote .. the router is plain confused.
Simple fix: just add your LAN-IP of the box running the server and you'll see it show up in the serverbrowser :-)
You can also always simply do "/connect 192.168.123.123" (with correct LAN IP).