As other have noted above, some people are still having an issue connecting matchmaking. I am one of them.
I am running the latest Halo:MCC update on two Xboxen. When connecting to Halo: MCC multiplayer matches, I usually cannot connect. Occasionally I luck out, but generally the status just displays (in order):
Searching for Players…
Connecting to Session…
Failed to Connect
Connection to Session…
It then repeats – Usually starts back on “Searching for Players…” but sometimes “Searching for More Players.” This repeats over and over. I’ve literally had this screen up for hours with no successful connections.
Internet connection: AT&T U-verse (dual-line multiplexed DSL), super stable, 45 Mbps down/6 Mbps up. Usually less than 50ms ping.
Router: Netgear R7000 Nighthawk. Configured to receive a public IP via IP Passthrough from the AT&T gateway device, which has its own router.
Internal network topology: 802.11ac 5 Ghz, 802.11n 2.4 Ghz, both supplied from Netgear router. However, I only use wireless for tablets, typically, as I have cat6 directly to every room, connected to a TP-Link TL-SG1016 1 Gbps switch, which is uplinked to the router.
I have five 360s attached via wired network on the current production build.
I have TWO Xbox Ones. Both are on different pre-release builds. They are:
6.2.12521.0 (xb_rel_1503.150305-1449) fre
6.2.12692.0 (xb_rel_1504.150311-2200) fre
I see the same behavior on both Xboxen.
Both are usually connected via wired connection.
When connected to my Netgear router, I have Open NAT, but when connected directly to the AT&T gateway’s built-in router, I’m Strict NAT (more on that in Troubleshooting Steps).
All other multiplayer games are 100% successful. Examples of games I’ve played extensively are:
Dragon Age: Inquisition
Plants vs. Zombies Garden Warfare
Troubleshooting Steps I’ve Taken:
- Disconnecting one of the Xbox Ones from the network altogether
- Rebooting/factory resetting AT&T gateway, Netgear router, and the TP-Link switch
- Hard-rebooting the Xbox
- Connecting via wireless instead of wired
- Changing the MAC address of the Xbox to pull a different IP address from the router’s DHCP
- Disabling all the anti-DDoS and anti-port scanning settings on the gateway
- Resetting all the UPnP port forwarding settings on the router
- Bypassing the TP-Link switch and connecting directly to the Netgear router
- Bypassing the entire internal network and connecting directly to the AT&T gateway’s router.
- Bypassing my ISP and connecting to my Verizon MiFi.
- Resetting the Xbox’s local storage.
The ONLY thing that has consistently worked is going to my MiFi (although that’s obviously not a solution). All the other troubleshooting steps seem to have no effect. Occasionally, after messing with things long enough, it’ll start working for a few sessions, but I’ve never been able to successfully repro whatever steps made it work. So I’m kind of thinking it has to be an ISP issue of some kind, maybe? It doesn’t make sense, though, why every other game works fine. Or why it’s apparently somewhat intermittent. I do know, however, that I’m not the only person who has experienced something like this, as seen here.
I’m willing to take beta bits or whatever to help troubleshoot this.