Games in Progress: 3 | Players logged in: 3 | Players Registered: 37413 | Games Played Total: 68656
Print Page - D-Link Router Port forward

Planet M.U.L.E.

M.U.L.E. Community => General Discussion => Topic started by: Who is Your M.U.L.E. on March 19, 2010, 23:27



Title: D-Link Router Port forward
Post by: Who is Your M.U.L.E. on March 19, 2010, 23:27
Hello,

I just got a new D-Link router and can't get it to port forward :(

I've tried all sorts of combinations of IP addresses but I am still missing
something.   ???

It's a D-Link DIR-825.  I'm not too technical with things, but I'm
running XP SP2, my internal (network) IP is 1XXXXXXXXXXXX (static),
my external IP is XXXXXXXXXXXXXX.

When I try to open and host a game the IP at the bottom is XXXXXXXXXXX.

Right now, the best I can get is this message:
ADDRESS: 127.0.0.1
CONNECTION FAILED
FAILED TO START SERVER ON PORT 6260
PLEASE MAKE SURE YOU HAVE STARTED ONLY ONE INSTANCE OF THE GAME.


Help Anyone??

Cheers, and I look forward to hosting (again)!



Title: Re: D-Link Router Port forward
Post by: Rhodan on March 20, 2010, 01:15
I have a different D-link router then you but the menu system may be the same.
Under Advanced settings you will see Gaming. There you will see add a Game Rule.
For Ip address enter your static ip 0.16
TCP and UDP ports to open enter 6260
Inbound filter allow all
save it
Then save settings to the router
Hope this helps


Title: Re: D-Link Router Port forward
Post by: Who is Your M.U.L.E. on March 20, 2010, 02:35
GREAT!

That was very close to what I needed to do!!!

THANKS!  :)


Title: Re: D-Link Router Port forward
Post by: Plod on March 28, 2010, 14:58
If your D-Link router is anything like mine, (DSL-G604T) it may have a tendency to drop user introduced settings.


Title: Re: D-Link Router Port forward
Post by: Pescado on April 06, 2010, 06:15
If you cannot even connect to your own game on localhost, then your router isn't even in the picture yet. Routers only control connections to the outside world. If you cannot connect to your own computer at localhost, then your problem is coming from inside your computer somewhere.