Halo 2 Forum
This topic has moved here: Subject: only big brains need apply ...
  • Subject: only big brains need apply ...
Subject: only big brains need apply ...
  • gamertag:
  • user homepage:
  • last post: 01.01.0001 12:00 AM PDT

Open NAT and two xbox's. Playing Halo 2. Australia, ISP is Internode.

For background, if you don't know what I'm talking about when I refer to open NAT, you may want to refer to the following:

http://www.xbox.com/en-US/support/connecttolive/xbox/connecti onmethods/diagnosingconnections.htm

I have an understanding it has to do with UPNP, and perhaps the degree SPI in the NAT implementation.

I Know that port forwarding and putting the client in the DMZ will solve the issue if i only have one xbox....

I have two xbox 360s.

I am using a web excel (no name) AL-2108TC modem/router - supports UPNP, turned on.

Both xbox's report open NAT - when both are connected or each separately.

When only using one xbox we seem to have no worries - what you would expect with Open NAT.

But when we are using both xbox's at the same time we have problems connecting to some users : ( with one of the xbox's - which one can vary. (sometimes cannot hear peoples voice and vis versa in pre game lobby, some people cannot connect to game)

Is there a way around this problem?

Can you change what port the 360 uses for xbox live that i can port forward to two different ports? (due to the nature of p2p gaming - I'm not sure that this would work anyway).

  • 07.30.2007 4:29 AM PDT
  • gamertag:
  • user homepage:
  • last post: 01.01.0001 12:00 AM PDT

um cant really remember much but go to www.portforward.com and try port forwarding your virtual ports then entering the ip address of your router in your 360s settings and get the othe info by running command prompt and type in ipconfig/all if you want to get in command prompt go to run in the start menu and type cmd

  • 07.30.2007 5:15 AM PDT
  • gamertag:
  • user homepage:
  • last post: 01.01.0001 12:00 AM PDT

Ok, I'll start off by saying in my situation, the boxes were not NAT.

However, I used to have this problem as well, the first 360 would work just fine, but the second one couldn't always connect or some users would appear muted to the second 360. What the problem is, the why I see it, is when you go into some games, the second 360 is getting assigned an IP address by the DHCP on your modem that is the same as the IP address of another box in game. If this happens with the first 360, it usually isn't affected because Port Forwarding/DMZ/UPnP allow reworking around the IP conflict to occur. The solution, for us, as to go into the DHCP settings on the router, and change the "Lease Allow Range." It will probably be something like "192.168.1.100 - 192.168.1.255" or something similar. Most routers will automatically assign the first connection to the router "192.168.1.100" and the second connection "192.168.1.101" and so on and so forth. So I changed the range that it is allowed to assign to some obscure numbers like "192.168.1.237 - 192.168.1.240" and I did not seem to have this problem anymore. Not sure if it will work for you or not, but it did for me anyway.

Good luck, hope this helps.

- Xaej

  • 07.30.2007 5:23 AM PDT
  • gamertag:
  • user homepage:
  • last post: 01.01.0001 12:00 AM PDT

Posted by: II Fozzy II
um cant really remember much but go to www.portforward.com and try port forwarding your virtual ports then entering the ip address of your router in your 360s settings and get the othe info by running command prompt and type in ipconfig/all if you want to get in command prompt go to run in the start menu and type cmd


That works great for one xbox, but when you've got two, the second one would get no traffic ... unless i can change the port one of the xbox's uses for xbl.

Thanks.

  • 07.30.2007 5:26 AM PDT
  • gamertag:
  • user homepage:
  • last post: 01.01.0001 12:00 AM PDT

sometimes i connect both 360s to the same network either i use a hub or i bridge the connection through my computer which is connected by usb
hubs dont have a firewall and a really cheap

  • 07.30.2007 5:36 AM PDT

Formerly: Mr Shroom
No...it's because I'm kept in the dark and fed bull-blam!-!
"One man alone can be pretty dumb sometimes, but for real bona fide stupidity, there ain't nothin' can beat teamwork." -Edward Abbey
00110111

I know exactly what you're going through. My roomie and I collectively have 2 original xboxes and 2 360's and we were running into this same problem for a long time. No, we weren't trying to play live with 4 consoles, but whenever we tried 2 at one time, we would have similar problems. The DMZ approach seemed to solve this for us. We haven't had any problems since then. Good Luck.

  • 07.30.2007 7:10 AM PDT
  •  | 
  • Exalted Mythic Member
  • gamertag: gezab
  • user homepage:

Carrots.

Einstein had an abnormally small brain, so stfu.

  • 07.30.2007 7:34 AM PDT

I'm not familiar with your modem/router combo but why not just assign both xbox's an IP instead of using DHCP and drop them both in the DMZ if you think that's what the problem is. That is, if you can have two IP's in the DMZ, like I said I don't know anything about web excel.

As far as I know there is not a way to change the port used for xbox live.

Hope this helps.

  • 07.30.2007 9:07 AM PDT

All routers use NAT, otherwise you would need an IP address from your ISP for each xbox/computer/device on your home network. The "Open NAT" refers to the routers ability to properly translate ports/protocols from your private IP to your ISP's public IP assigned to you. Some routers implementation of NAT was buggy/flawed so this is why it is tested by your xbox. Also, the "private" IP assigned to your xbox by your router cannot be seen by another xbox. Only the IP address assigned by your ISP to the router/modem is seen by the other persons router.

Posted by: Xaej
Ok, I'll start off by saying in my situation, the boxes were not NAT.

However, I used to have this problem as well, the first 360 would work just fine, but the second one couldn't always connect or some users would appear muted to the second 360. What the problem is, the why I see it, is when you go into some games, the second 360 is getting assigned an IP address by the DHCP on your modem that is the same as the IP address of another box in game. If this happens with the first 360, it usually isn't affected because Port Forwarding/DMZ/UPnP allow reworking around the IP conflict to occur. The solution, for us, as to go into the DHCP settings on the router, and change the "Lease Allow Range." It will probably be something like "192.168.1.100 - 192.168.1.255" or something similar. Most routers will automatically assign the first connection to the router "192.168.1.100" and the second connection "192.168.1.101" and so on and so forth. So I changed the range that it is allowed to assign to some obscure numbers like "192.168.1.237 - 192.168.1.240" and I did not seem to have this problem anymore. Not sure if it will work for you or not, but it did for me anyway.

Good luck, hope this helps.

- Xaej

  • 07.30.2007 9:26 AM PDT

I gave my Xbox's static IP addresses and allowed them free reign through the ports XBL used through port forwarding.

XBL Ports
88 UDP
3074 UDP
3074 TCP

  • 07.30.2007 9:59 AM PDT