Nat strict and losing connection during 1 game mode only

Hi,

This is very common with Belkin N's follow this guide to the letter and it should resolve it:-

www.unofficialguidetolive.co.uk/.../62-my-nat-is-strict-or-moderate

I did everything it said to do. I've tried setting up a static IP address numerous times on the Xbox, every single time after I do it I can't even connect to live anymore.  I've gotten directions on how to do it from numerous sources and I get the same results every single time. When I test my live connection I get "Test Failed, There's a problem with your connection. Select more info for a description of the problem and how you can fix it. Again, I do everything in the more info, still no luck. This is getting unbelievably frustrating because I don't understand why I'm still having problems when I'm doing everything that everybody is telling me to do. Wasn't so bad until I can't even play the Onslaught mode that I just bought.

Belkin routers aren't very good IMO for this reason alone. Are you running the latest version of firmware on the router? Check their website don't rely on the router sayings its up to date

I'm surprised its still a problem though, if you follow those instructions to the letter and have UPnP turned off and any portforwarding turned off it should work,

Oh my god, wait... I just realized I messed up on the DNS part of it and all of the other times I've done it they've never said anything about changing the DNS away from automatic, soi that had to have been my problem... I'm connected to live now through the static address with an open nat right now, BUT every single time I do something new, my nat IS open right after and sometimes even lasts while I play through a couple games.  So I'll have to get back to you tonight and let you know if it's still open.  If it is, THANK YOU SO MUCH... This has been so frustrating and it turned out to be 1 extra stupid step.

Ok

Ok, so far so good, been playing onslaught without a single problem... Like I said, I've done things before where the nat setting would go to open for a bit, but then sooner or later it would be strict again, I should know by tonight though, wouldn't last any longer than that before.  Thanks a ton. Now I've always been told to have the upnp on, why is it ok to have it off now?

Could anything I've done there effect a blu ray player being able to play netflix connected to the same router? I've never had a problem with it before, now I can connect to netflix, see all the movies and stuff in my queue, but none of them will load and play.

Hi,

Good stuff, when configured in the DMZ properly it should never change, UPnP, DMZ, Porforwarding all do the same job for the Xbox so if you have them some of them configured at the same time they interfere with each other

I don't know much about your blu ray player or Netflix I'm afraid. Does it need certain ports open to be able to contact the service (I assume this is nothing to do with Xbox?) if the player does need certains ports open yes UPnP may have opened them for the player if the player is using UPnP as well. If that is the case its a matter of finding out what ports are needed to be open for your player and setting up portforwarding for it.

Just done a quick search about this and Try this:- http://portforward.com/english/routers/port_forwarding/Belkin/F7D2301v1/Netflix.htm

If that causes problems with anything else don't both forwarding port 80 and just forward 443

What I was asking is if doing what I did to fix the Xbox could have affected the Blu Ray not working because it never had any problem before I changed the setting on the router when I was fixing the Xbox but it must have just been some problem that specific day...  I just went to check and see if it still wasn't working before I messed with the port forwarding stuff and it's working fine now.  Thanks A LOT for the help, I can't believe how simple it ended up being with just 1 link. I've looked up so many different things, asked a lot of people, got so many different answers, I can't believe it's finally fixed. Really, thanks again!

No problem