Julie2017, For anyone to be able to offer you any help, you will need to post some more information, for example, consider the following as a minimum starting point: 1. How are you connecting to your router/superhub? WIFI/wired connection? 2. In either situation, what 'species' of network technology are you using? For example, 10/100 wired ethernet, gigabit ethernet, WIFI 'G', 'N' or 'AC', and on which frequency range, eg "2.4ghz" or "5ghz"? 3. Are there other computers, tablets, phones or networked gadgets on your network, and are they using the internet at the same time? 4. I'm no gaming person, but I presume the Fifa publishers provide tools either within the game or instructions to follow in these cases. What were the results? I'd be interested in ping response times and packet loss, for example.
Some general thoughts - port forwarding is obviously a good thing, but obviously it is quite important that you ensure you are forwarding the right ports. While not always recommended for security reasons, you may be better off using UPNP instead (can be enabled on router) to allow the game on the XBox to automatically manage the port forwarding.
On the assumption you also have a PC or laptop running windows in your household, you may want to check your connection to EA. I crafted a useful PING command to check out the connection between you and EA: C:\Users\andrewb>ping -n 50 -l 1450 easo.ea.com
Pinging easo.ea.com [220.127.116.11] with 1450 bytes of data: Reply from 18.104.22.168: bytes=1450 time=117ms TTL=110 Reply from 22.214.171.124: bytes=1450 time=117ms TTL=110 Reply from 126.96.36.199: bytes=1450 time=117ms TTL=110 Reply from 188.8.131.52: bytes=1450 time=118ms TTL=110 Reply from 184.108.40.206: bytes=1450 time=117ms TTL=110
Ping statistics for 220.127.116.11: Packets: Sent = 5, Received = 5, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 117ms, Maximum = 118ms, Average = 117ms Control-C
(Obviously I stopped this, but it would run for 50 packets). TECHIE ALERT: YOU CAN IGNORE THE NEXT BIT You will also note I've increased the packet size towards the higher end of the default 'ethernet frame size' to better uncover any strangeness. From my home, via a wired connection I noted that for some reason, somewhere between my home and EA is a router which prevents 'larger' (>1500 bytes) packets from getting through, whereas such packets should be broken up and re-assembled (fragmented). I had to reduce the size to 1450 bytes from the original 1500 (1514) default size to get a response - I'm not sure I understand why this is. <END TECHIE BIT>
Either way, the important bit comes at the end: Ping statistics for 18.104.22.168: Packets: Sent = 5, Received = 5, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 117ms, Maximum = 118ms, Average = 117ms
You need to look at the line starting 'Packets' and ensure that the 'Lost' figure is 0 or 0%, and also check that the Min/Max/Avg figures are all fairly similar.
If you have any problems, your last reasonable step is to perform a traceroute: C:\Users\andrewb>tracert easo.ea.com
Tracing route to easo.ea.com [22.214.171.124] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Office-AP [192.168.0.1] 2 * * * Request timed out. 3 8 ms 10 ms 7 ms cosh-core-2b-xe-123-0.network.virginmedia.net [126.96.36.199] 4 * * * Request timed out. 5 * * * Request timed out. 6 12 ms 11 ms 12 ms tclo-ic-3-ae0-0.network.virginmedia.net [188.8.131.52] 7 13 ms 15 ms 13 ms blackhole.prolexic.com [184.108.40.206] 8 15 ms 17 ms 14 ms unknown.prolexic.com [220.127.116.11] 9 17 ms 19 ms 15 ms unknown.prolexic.com [18.104.22.168] 10 113 ms 116 ms 116 ms 22.214.171.124 11 114 ms 115 ms 115 ms unknown.prolexic.com [126.96.36.199] 12 115 ms 114 ms 114 ms 188.8.131.52 13 115 ms 116 ms 114 ms 184.108.40.206 14 117 ms 115 ms 123 ms 220.127.116.11 15 115 ms 116 ms 115 ms easo.ea.com [18.104.22.168]
Don't get too hung up on the 'Request Timed Out' because many of VM's routers are either too busy to respond to traceroutes or configured not too. Provided the last 'hop' in the traceroute with 'virginmedia' in the name does not show a massive jump in timings, or you don't see things going around in circles, then sadly there is not much VM can do. If you do see weird things in VM territory, take it up with 150.
Good luck. Andy
AndyBundy ----------------- I don't work for VM. I am medically 'retired' after working for a large multi-national Telco and have spent fifteen years in WAN/LAN IP Networking, Network Management and IT Support.