I have found a work around !
I have an iinet Bob 2 Modem.
You should be able to find similar areas in most routers as I adjusted.
I am not exactly sure which part of these settings has done the trick but here is exactly what I did to get 2 Xbox connected nice and Stable.
ON THE CONSOLES
1) set both xboxs to automatic DNS
CLEARED EVERYTHING ON THE ROUTER
1) Removed the static IP set for both xbox's
2) Removed all other static IPs and released all IPs on the router
3) Removed all port forwardings fromthe router that I had set up.
4)Turned off all devices and the router... (full network shutdown)
5) restarted router
START FRESH
6) Restarted Xbox 1 - left network settings in xbox alone so just put it on "automatic" DNS (no static IP in Xbox)
7) logged into router and navigated to the "DHCP list" which showed only the Xbox then ticked to "Fix IP address to Client" (so I set Xbox 1 on the router to a static IP) but left it to auto on the console.
Setup Trigger Ports in NAT
8) went into the routers firewall settings/Network Address Translation(Nat) "configure" and Clicked the link to enable "Special Applications"
which is Trigger Ports so in other modems should be in the same area of your modem config (NAT settings)
trigger port type Public Port
6112 TCP 6112
53 TCP 52-54
53 UDP 52-54
80 TCP 79-81
80 UDP 79-81
3074 TCP 3073-3075
3074 UDP 3073-3075
3544 UDP 3544-3544
4500 UDP 4499-4501
500 UDP 499-501
I got the ports from this post: http://portforward.com/english/applications/port_forwarding/publishers/Electronic_Arts.htm
The first PORT is for Battleog
The rest are for Xbox live and Origin/EA servers
here is a screenshot of how I configured the iinet Bob 2 Modem's Trigger Ports http://screencast.com/t/lAjDyaQGKF
TURN ON QOS and Add Xbox Mac Address
9) in Router settings went to Tab called "Applications" and Clicked on the "configure button" next to QOS
10) QOS was already enabled and setup with the Mapped Forwarding Group of EF to have the highest priority and only VOIP was configured to use it.
11) left it all as it was but knowing VOIP was set to EF and that was the highest priority I made a new Rule for the Xbox
screenshot: http://screencast.com/t/Vaneopp5
Here are the exact settings I used:
Class Interface: Local
Local Mac Address: (added the XBOX Mac address which I got from the Network Settings screen on the Xbox)
Remote address: Any
Traffic Type: Any
Map to Forwarding Group: EF
Remark Upstream DSCP as: EF
Remark Downstream DSCP as: No Remark
Direct to VC: By Routing
screenshot: http://screencast.com/t/trXvPbztT
That is it on the modems, I did not setup anything for Xbox 2
Now Started Xbox 2 First and logged into Live then the Game - it connected no problem (as usual)
Started Xbox 1 and logged into Live
Next I logged into Battlelog from my IPAD which was on 3G so it was not on the same Network...
It detected that I was logged into Xbox Live on my Xbox
Then I logged into Batllefied 4 : IT WORKED no Disconnection From EA !!
Played for hours, No Drop outs, Fast Pings, No connection issues, no rubber banding or Lag on either console..
I cant say for sure if the IPAD part is necessary however I do it know that each time I must start XBOX 2 first and log it in
THEN turn on Xbox 1 AFTER Xbox 2 is logged in..
So I do it in the exact order as listed above and since I have been doing this we have not had a single dropout or issue on either console
So to break it down..
Setup Trigger Ports, this doesn't associate with either Xbox specifically,
Set a Static IP and QOS for only one Xbox ONLY
second xbox leave totally default with automatic DNS
Start and log into the game on the the Automatic DNS Xbox 2 FIRST!
and start and log into your static IP Xbox AFTER the first is logged into multiplayer and you have an EA connection...
If your game has an app such as Battlelog and you have it on your phone or tablet which is on 3G or 4G then log into EA server via that app
with the same account that is playing on the static configured XBOX.
Just log in, dont have to do anything other than connect and it knows you are on your xbox. You can open the "commander" app to be sure.
This seems to help the EA servers route the traffic to that same Xbox without any confusion with the other xbox
( it is possible that this is the only step required out of all above)
I have Xbox 1 Cabled
This worked in test with Xbox 2 wired and also worked with Xbox 2 cable removed: WIFI ONLY
But Cable for both is better if you can...
Anyway I hope this info helps someone else cuz it was driving me insane and it all works perfectly now!!
I was doing this for Battlefield 4 However I am assuming it will work if you do similar steps for FIFA or any other EA Game that is having this same issue
Good Luck 🙂
