• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

3rd Party Router Firmware

Modeps

Lifer
Here is my setup:

  • Comcast Cable Modem => WRT54G v2 (at least 2 year old Satori Firmware)
    Desktop PC is using a WMP54G PCI Wireless Card to connect to WRT54G
    Xbox360 is wired using ethernet to connect to WRT54G

If I hook my laptop up to my router with an ethernet cable and try to share media to the 360, it works fine (360 can see the laptop, laptop can see the 360, media streaming works). If I remove that cable and use wireless, it stops working (PC can still see the 360, but 360 can no longer see the PC, so I cant do any streaming).

I'm *pretty* sure that I just have to update my firmware (even Linksys' default firmware's latest release states that there is a fix for uPNP in it), but I just wanted to check with you guys to see if you have a similar setup and are running anything special on your end. I was looking at the DD-WRT firmware (http://www.dd-wrt.com) as I've heard that this also resolves some of the "Not Open NAT" messages that people can get in Halo 3.

Any assistance would be appreciated.

edit: this is from the Linksys firmware changelog:
Firmware 4.21.1
- Resolves issue with L2TP connection
- Resolves issue with Linux kernel vulnerability
- Resolves issue with UPnP
- Resolves issue with Access Restriction
- Resolves UPnP vulnerability reported by SANE
- Resolves issue with filter name
- Resolves issue where service name for PPPoE cannot be added
- Resolves issue with detecting UHP modems
- Resolves issue where DynDNS Custom and Static accounts cannot be used
- Resolves issue with WEP passphrase not recognizing spaces
I'm hoping that those two issues that were resolved, would resolve my issue, and also found their way to 3rd party firmwarez.
 
Remember, if you have a WRT54G v. 5 or later, DD-WRT is infinitely more difficult to install than it would be if you had an older one.

I myself use a SonicWall at home, but I have used DD-WRT software in the past. Really great software, and there are tons of options to tweak in there.
 
Originally posted by: adairusmc
Remember, if you have a WRT54G v. 5 or later, DD-WRT is infinitely more difficult to install than it would be if you had an older one.

I myself use a SonicWall at home, but I have used DD-WRT software in the past. Really great software, and there are tons of options to tweak in there.

I've got version 2, so I think I'm good (updated original post)
 
I use DD-WRT with my Linksys WRT45G router and don't have a problem with Xbox Live or sharing media.

Now getting my wife's T-Mobile HotSpots @ Home cell phone to stop dropping calls is a completely different matter.

PortForward.com tells you what ports need to be forwarded for different applications/services like Xbox Live and Xbox Media Center.
 
Originally posted by: Queasy
PortForward.com tells you what ports need to be forwarded for different applications/services like Xbox Live and Xbox Media Center.

That could be very useful, although I really shouldnt have to forward ports. Thank for the link, 360 News Master.
 
Originally posted by: Modeps
Originally posted by: Queasy
PortForward.com tells you what ports need to be forwarded for different applications/services like Xbox Live and Xbox Media Center.

That could be very useful, although I really shouldnt have to forward ports. Thank for the link, 360 News Master.

Doing Port Forwarding or putting your 360 in the DMZ helps resolve the Open NAT issue with Halo 3.
 
Originally posted by: Queasy
Originally posted by: Modeps
Originally posted by: Queasy
PortForward.com tells you what ports need to be forwarded for different applications/services like Xbox Live and Xbox Media Center.

That could be very useful, although I really shouldnt have to forward ports. Thank for the link, 360 News Master.

Doing Port Forwarding or putting your 360 in the DMZ helps resolve the Open NAT issue with Halo 3.

My 360 is already setup in the DMZ, yet I still get the Open NAT message. It does not seem to effect my actual gaming/matchmaking though so I just haven't worried about it. In general, Xbox Live works great... my main issue is this Media thing. I've been using an iPod for music, and I shouldnt have to. Now with the codec updates, I'm more motivated to get everything working as it should.
 
Modeps - DDWRT does not guarantee you'll get an Open NAT. I've never got an Open NAT anywhere - my old roommates house using Verizon, nor using Comcast out here. (Running a Buffalo w/ DD-WRT) The best I've gotten both places is moderate NAT, including putting it in the DMZ.

What I've found which guarantees an Open NAT 100% of the time (least in my experience) is setting up a static IP on your 360 and running the XBox Network connectivity test each time you start your XBox. (Disable auto-sign in) Yes you have to do it each time, but it's the only way I've been able to get Open NAT each time. (Adds about 30 seconds of testing time before you're able to sign-in and play XBox, but it's not a hassle for me really)
 
Originally posted by: RagingBITCH
Modeps - DDWRT does not guarantee you'll get an Open NAT. I've never got an Open NAT anywhere - my old roommates house using Verizon, nor using Comcast out here. (Running a Buffalo w/ DD-WRT) The best I've gotten both places is moderate NAT, including putting it in the DMZ.

What I've found which guarantees an Open NAT 100% of the time (least in my experience) is setting up a static IP on your 360 and running the XBox Network connectivity test each time you start your XBox. (Disable auto-sign in) Yes you have to do it each time, but it's the only way I've been able to get Open NAT each time. (Adds about 30 seconds of testing time before you're able to sign-in and play XBox, but it's not a hassle for me really)

Wow, that seems like overkill. I should read up on what having an Open NAT actually means for playing Halo 3... if it really impacts things or not.
 
Originally posted by: Modeps
Originally posted by: RagingBITCH
Modeps - DDWRT does not guarantee you'll get an Open NAT. I've never got an Open NAT anywhere - my old roommates house using Verizon, nor using Comcast out here. (Running a Buffalo w/ DD-WRT) The best I've gotten both places is moderate NAT, including putting it in the DMZ.

What I've found which guarantees an Open NAT 100% of the time (least in my experience) is setting up a static IP on your 360 and running the XBox Network connectivity test each time you start your XBox. (Disable auto-sign in) Yes you have to do it each time, but it's the only way I've been able to get Open NAT each time. (Adds about 30 seconds of testing time before you're able to sign-in and play XBox, but it's not a hassle for me really)

Wow, that seems like overkill. I should read up on what having an Open NAT actually means for playing Halo 3... if it really impacts things or not.

It mostly affects the speed of matchmaking.
 
I have a version 5 wrt54g and a buffalo router as the client bridge connected to the 360. I don't have to do any fancy tricks. I just have my xbox w/ DHCP from my linksys and DMZ that ip on the linksys and it works fine. It tests as Open NAT as well.

Also when I first set it up w/o DMZ I would get moderate NAT and could not host any Halo 3 lobbies and had a hard time connecting to games with my friends.
 
Originally posted by: Queasy
Originally posted by: Modeps
Originally posted by: RagingBITCH
Modeps - DDWRT does not guarantee you'll get an Open NAT. I've never got an Open NAT anywhere - my old roommates house using Verizon, nor using Comcast out here. (Running a Buffalo w/ DD-WRT) The best I've gotten both places is moderate NAT, including putting it in the DMZ.

What I've found which guarantees an Open NAT 100% of the time (least in my experience) is setting up a static IP on your 360 and running the XBox Network connectivity test each time you start your XBox. (Disable auto-sign in) Yes you have to do it each time, but it's the only way I've been able to get Open NAT each time. (Adds about 30 seconds of testing time before you're able to sign-in and play XBox, but it's not a hassle for me really)

Wow, that seems like overkill. I should read up on what having an Open NAT actually means for playing Halo 3... if it really impacts things or not.

It mostly affects the speed of matchmaking.

Also affects who can connect to your games and vice versa in some cases. I've had trouble connecting to my cousin and my old roomie when it was moderate NAT. Overkill? Sure, but it isn't as bad as you think to do it everytime you turn it on.
 
Originally posted by: RagingBITCH
Modeps - DDWRT does not guarantee you'll get an Open NAT. I've never got an Open NAT anywhere - my old roommates house using Verizon, nor using Comcast out here. (Running a Buffalo w/ DD-WRT) The best I've gotten both places is moderate NAT, including putting it in the DMZ.

What I've found which guarantees an Open NAT 100% of the time (least in my experience) is setting up a static IP on your 360 and running the XBox Network connectivity test each time you start your XBox. (Disable auto-sign in) Yes you have to do it each time, but it's the only way I've been able to get Open NAT each time. (Adds about 30 seconds of testing time before you're able to sign-in and play XBox, but it's not a hassle for me really)

I used to have to do the Connection Test every time i wanted to get on XBL... PITA.
 
Anyway, my main reason for installing this update is not for Halo3, but for streaming media from my wireless PC to my wired Xbox. Hopefully that will work.
 
getting an open NAT is not nearly as difficult as the people are describing here.
1: assign 360 with a static IP
2: google which ports need to be opened on the router (don't remember the 3 or 4 off hand)
3: play games

Has worked successfully 2x for me with this setup.
 
Last night, I attacked. Full force.
In order to properly uninstall the Satori firmware, I had to telnet into the router and perform a 'nvram erase' then immediately flash the router with the Linksys official firmware. After the router reset, I did the 30 second refresh (unplug router, hold down reset button and plug router back in, keep holding reset for 30 seconds). After I knew I hadn't bricked my router (yay!), I prepped the DD-WRT firmware and installed that as well. It also required a 30 second refresh, but after that, just about everything was smooooth sailing (just about).

The firmware has allowed me to stream media from my wireless PC to my wired Computer using WMP11. Audio works perfectly as now when I open my guide and select music, I've got quite the library to choose from. A problem I've found though, is that it seems every once in a while while looking at certain video, WMP11's sharing service will crash. Luckily it does it before. It may just be specific formats, or it may be some other issue, but if it keeps it up, I'll have to convert all my videos to a specific format... or maybe just got the transcoding route.

Now, about the NAT issue. Even though I said we could stop talking about it. I popped my 360 into the DMZ and no matter what I did, the test came up with Moderate NAT. How is that freaking possible? No idea... but you know how I fixed it? I changed from manual configuration, to automatic (DHCP). This took my 360 OUT of the DMZ, just placing it on my network normally and boom-shalaka-laka, we have Open NAT. No port forwarding was done. Really weird.

Anyways, I'm just about super happy, now to figure out why WMP11 sharing keeps crashing.
 
Back
Top