You shouldnt have to do any port forwarding for connecting to FL Servers. Port forwarding on Routers is really for Servers, not for clients.

I beg to differ, mine was inaccessible until I forwarded all ports to the server pc. Granted it's also a firewall and NAT translator, but all I did was forward UDP ports 2302-2304 to the respective ports on the server pc.

A trigger port? So it isn't simply an option to enable port forwarding. How odd. try both opening those ports AND forwarding them, if your router allows that. Is it also a firewall etc?

Copula eam se non posit acceptera jocularum

---

I beg to differ, mine was inaccessible until I forwarded all ports to the server pc.

---

His post implies he is a Client, not a Server. Which is what my post stated. Clients do not need port forwarding.

I may have been unclear about that, but I do talk about me being a server. Connecting to other servers works fine, but no people can connect to my server.

Which router do you use?

I'm using a Sweex Broadband Router.

Looking at the Manual for that router, the features they offer appear that you may have to try a few things.

First, I would try their Virtual Server setup. Set your Servers internal IP in the Private IP box, probably something like 192.168.2.101. Use 2302 for the Private and Public Port. Add two more, same Private IP and use 2303 for the ports and then 2304 also. Use UDP for all.

You can try the Special Applications one, but not sure how that would work pointing to your Server.

Under Hacker Prevention, you may want to check and ensure you can be pinged from the outside. If not, your Ping may not show up on the Server List.

Last resort would be using the DMZ feature and pointing it to your Server. This is the least secure method though, since all ports are open to your machine. You may be able to mix DMZ with your Access Control option and block all ports but 2300-2400.

Good luck