Xbox One Cannot Access Xbox Live

jpvonhemel

I have been searching and trying to setup pfSense 2.3.1 to allow my Xbox One and PS4 to work with online gaming. Here is what I have done. Seems like the PS4 is working ok at Nat Level 2. The Xbox gives me an error Cannot complete multiplayer tests and does not connect to Xbox Live but it shows open nat.

1. Turned on UPnP/NatPMP

2. Added the ACL Entries for both the Xbox One (192.168.1.11) and PS4 (192.168.1.13)

3. Gave both Xbox One and PS4 Static Mappings in DCHP Server.

4. Added an NAT Outbound Rule for Each of the Static IPs.

5. I have not manually forwarded any ports to either consoles as I thought UPnP/PMP would take care of this for me.

Screenshots are attached. Getting frustrated and have to take a break. Will throw some beer/booze/whatever money your way if you can help me to get The Xbox One up and running in multiplayer.

Thanks,
Jerold
![Screenshot 2016-05-24 11.25.50.png](/public/imported_attachments/1/Screenshot 2016-05-24 11.25.50.png)
![Screenshot 2016-05-24 11.25.50.png_thumb](/public/imported_attachments/1/Screenshot 2016-05-24 11.25.50.png_thumb)
![Screenshot 2016-05-24 11.30.06.png](/public/imported_attachments/1/Screenshot 2016-05-24 11.30.06.png)
![Screenshot 2016-05-24 11.30.06.png_thumb](/public/imported_attachments/1/Screenshot 2016-05-24 11.30.06.png_thumb)

jpvonhemel

I've forwarded the Xbox Live Ports to my Xbox One and I am still getting Cannot Complete Multiplayer tests.

My next step later this morning is to run it straight to my cable modem to see if it works that way.

jpvonhemel

The xbox one multiplayer works when I bypass pfsense and go straight to the router.

I backed up and restored pfSense to factory default and simply turned on UPNP and allowed port mapping and the Xbox works, so there is a rule or something else that is blocking the Xbox.

Will troubleshoot that next.

jpvonhemel

Once I reloaded my config file, suddenly the xbox one is working. I have no idea why and I did not change any of the settings after restore. Very odd. Maybe it was a hardware reboot that fixed it.