I can't speak about your particular situation, but for me I wasn't able to have open NAT until I changed settings on my DSL modem.
Old setup: DSL modem handled logging into AT&T
New setup: DSL modem didn't log in. Log in handled by my router which is connected to my DSL modem. Result --> Open NAT.
Not sure if it applies to your situation, but I remember trying a lot of what you're trying and having none of it work until I did this. I did this a long time ago so I don't remember the names of the modes and settings I had to change but I think you get the gist of it.
I also have a Linksys. My solution was to turn off uPnP, and have just one port forwarded (well triggered since I have multiple xboxes): 3074. I messed with it for hours and hours messing with all kinds of ports, and it ended up being uPNP that was screwing things up. Just disabling it by itself didn't help; but it did finally allow the port forwarding to take effect, which did solve my problem. Now I'm open NAT on both boxes.
To repeat: DISABLE UPNP, FORWARD (or trigger) PORT 3074. LEAVE DMZ OFF AND DON'T MESS WITH ROUTING
@demontium: Glad it worked. It was a huge headache for me. The lack of uPNP has had a minimal impact. The few apps that require forwarding (PlayOn and uTorrent) have been kind enough to provide me a selectable port to add to my forward (not trigger) list.
This edit will also create new pages on Giant Bomb for:
Beware, you are proposing to add brand new pages to the wiki along
with your edits. Make sure this is what you intended. This will likely
increase the time it takes for your changes to go live.
Comment and Save
Until you earn 1000 points all your submissions need to be vetted by other
Giant Bomb users. This process takes no more than a few hours and we'll
send you an email once approved.
Log in to comment