How-To: Setup a Static IP on an XBOX 360 & Open NAT

[Octavious]

Since I'd posted about this awhile ago and have since solved the problem, I wanted to post my solution in case anyone has encountered similar problems with their 360 and online multiplayer over LIVE. This will open your NAT and solve the 'cannot connect to host' problem that occurs occasionally. It's fixed the rampant disconnects that plagued me in Call of Duty 4 / HALO 3 as well, so I hope it's of some assistance.


(This will focus more on a Linksys Router, but a similar procedure should work on most other routers as well)
First, open your browser and we'll forward the ports that will open your NAT on the 360 Network Connection Test. Go into your router, url=http://192.168.1.1 for Linksys Routers, and click the Applications & Gaming tab. Now forward the following ports and make sure you name them so you know their purpose. The image below should be the forwarded ports.


http://img243.imageshack.us/img243/5...edportstt7.jpg


Next, restart your router by unplugging it and it's time to turn on the 360. Go to your 360 Wireless Settings by going to System Settings > Network Settings > Configure Network. Now we're going to manually setup an IP for the 360 and you'll need the Primary & Secondary DNS Server info from your ISP. Basically, just call and ask for the information and they are required to give it to you. I'll place what you should see in the Network Configuration below with the important changes you'll need to make in bold.

Wireless Mode 802.11a/b/g
Network Name (SSID) Your Network's Name
Network Type Infrastructure (Channel 6)

IP Settings
IP Address: 192.168.1.140
Subnet Mask: 255.255.255.0
Gateway: 192.168.1.1

DNS Settings (example DNS server settings)
Primary DNS Server: 88.88.8.88
Secondary DNS Server: 88.88.8.89

After adjusting your Network Settings, save & exit and it will prompt you to run a connection test. After the test has been done, your NAT should appear as 'Open' in most cases and 'Moderate' in some. Either way, you should have no problems connecting on XBOX Live anymore and this should solve any rampant disconnect issues on XBOX Live.

[Kaisha]

Is there a reason why you did the TCP/UDP seperately for port 3074?

I would have just condensed it into two (given how all our damn LinkSys routers support just 10 seperate entries) by opening port range 80-88 TCP to the 360 and hit both for port 3074.

Isn't another (easier) option to just open the DMZ to the console's IP?
(or is there a drawback to that I've yet to see? Used it all the time for my PS2 back when I was living with my parents)

[Octavious]

Is there a reason why you did the TCP/UDP seperately for port 3074?

I would have just condensed it into two (given how all our damn LinkSys routers support just 10 seperate entries) by opening port range 80-88 TCP to the 360 and hit both for port 3074.

Isn't another (easier) option to just open the DMZ to the console's IP?
(or is there a drawback to that I've yet to see? Used it all the time for my PS2 back when I was living with my parents)

I could condense the ports but I actually experimented with opening one/the other to see how it would change the connection status. There's a few people I play COD4 with who I couldn't connect to when they were hosting so I wanted to add in ports and see the difference. You could condense them yea. Also, I tried the DMZ option however that didn't provide an 'Open' NAT setting and I was still plagued with 'Cannot Connect to Host' errors on a few games. Setting up a DMZ requires equal effort anyway, but it didn't solve my connection issues.

edit: Basically the only drawback with a DMZ would be the potential access from outside sources since it's operating essentially outside the firewall (from what I understand). However there's little chance a 360 would be hacked etc from running it like that so it's kind of a toss up. You could set it up and just forward the ports or try a DMZ. I honestly tried the DMZ and it didn't change my host issues or my connection speed, so I would say go with whats best for you.

[Mici]

Thanks, just did this and it works great for me!
Also instead of calling ISP you can Start>Run>cmd>ipconfig /all - It will say DNS servers as the last one, first is primary 2nd is well secondary
But thanks again, working great

[Octavious]

Thanks, just did this and it works great for me!
Also instead of calling ISP you can Start>Run>cmd>ipconfig /all - It will say DNS servers as the last one, first is primary 2nd is well secondary
But thanks again, working great

I completely blanked on doing an IPconfig lol, but it did result in some funny conversations with my ISP. "Could I get my DNS info?" | "Well, you should let your 360 automatically-" | "No, I did that and it's fucking with the XBOX Live Connection, give me my info please." | "Here ya go-" lol. Glad to hear it worked out :D

[Kaisha]

Could also just check the DNS IPs the router gets on its Status tab.