I agree with Four4875 but If I may interject, dont use an internet DNS server as the primary use the IP of your router. Since it is getting its WAN info from the ISP the DNS server will update automatically, these things tend to change. In regards to worring that your ISP is DHCP and if your IP changes you have to reconfig the router every time your ISP changes your IP, well dont it is a wated thought. Four has it nailed on the static IP internally as this is where you would run into that worry. I tend to disagree with the interpertation of the DMZ though. Putting a piece of equipment into a DMZ will not forward all ports to this device. Infact it will forward no ports to the device. What it does allow it to do is initaite comms on any of the ports aviailbe from 1-49151 (
http://www.iana.org/assignments/port-numbers) A DMZ means wide open no firewall A home type router doesnt go this endepth, but it has a very Basic Firewall Function. Probally will only allow for common ports ie 80HTTP 443SSL 25SMTP 21FTP 23Telnet 22SSH and a couple of others, otherwise all outbound connections are squashed. With a real firewall you can controll all ports and protocols. This being said Port Forwading is when you take an inbound port and protocol and direct it an internal IP. For example SMTP communicates on 25 between email servers. If your mail server sent me a message then it would seek my server on port 25. Once the request makes it to my public IP, the one given to you by the cable modem, it will then say hey I have a request on 25 were does it go..hmmmmmmmm.let me see....oh yeah I need to forward it to Internal IP defined in rule. In your case you probally need some random port or range of ports forwarded to your server to host the game. You will need to find out 3 things. 1 what port(s) is required to talk on 2. what protocol ie TCP,UDP and 3. their direction is in out in in/out send recieve send/recieve. I know this sounds like a map but it is key. Heres a crash on comms. the server makes a call to another on a predifined port(s) the server responds on the port(s) When the server made the call it was an out when it hit the other machine it was an in. Out and in are used in TCP connections TCP is nothing but a protocol like UDP which uses sends and receives respectively to in/out. Dont be afaid to setup this up its really not that hard and this explaniation is simplified leaving gaping holes in the principles in which this really works, but it should give you an idea. Do what Four suggests, set a static IP on the machine you want to host games from. You can do this quite simply by running ipconfig on the pc while it is getting a DHCP address and wrtie down these things the first 3 octets of the IP address ie 192.168.1 then write down the Gateway and DNS server you will find them to be the same # then write down the subnett mask. You will want to make sure that your DHCP server ( your router) will not hand out the IP you choose so look at the "pool" and set an IP out of scope, not in the list. Goto the firewall page/routing page dont recall how netgears are setup up and set up your port forwards and your rules for in/out to allow that IP to talk. If you arent worried about the whole world knocking on your front door you can put the pc's ip in the dmz. Again really this isnt too hard. If you need help and can post the port info and screenshots of your routers web interface I can walk you through quickly.
Personally I would recomend getting rid of that Netgear and NEVER buy a d-link. In my past experience I have found Linksys to be the best I have had them all. If you really want to do some damage and stay stable invest in a cisco 1700 with a 10base wic. Alothough it is alot harder to configure than a "home solution" its performance and stability will take you back.. You can look for "Cisco Lab" in google people sell these things dirt cheap as they are passed around for CCNA tests like used cars.
