Bell Home Hub 4000 Does Not Support XBOX Gaming when Wired

[andrewnorris]

Just switched over to a Bell Fibe 1.5Gbps plan, and have been running into a very weird issue with my Home Hub 4000. 

When I plug my XBOX into the Home Hub (base configuration) via Ethernet to the 10G LAN port (or any LAN port), I get the following error when I go to XBOX Settings > Network, it says NAT Type: Unavailable. I run the “Test NAT type” and it gives me the error: “Can’t get a Teredo IP address”. This problem prevents Xbox Live to work and some multiplayer games like Call of Duty Warzone to not be able to connect at all.

Weird thing is that when I unplug from Ethernet and switch the XBOX to Wi-Fi, it says NAT Type: Open and everything works as expected, but with more latency and lower speeds.

I've tried every combination of Ethernet wires, turning on a DMZ, port forwarding, but no luck.

XBOX's support (https://support.xbox.com/en-CA/help/Hardware-Network/connect-network/xbox-one-nat-error#troubleshoot...) says what's needed is to:

• Allow Teredo tunneling
• Allow IPv6 tunneling

As far as I can see, there's no option for either in the Home Hub Advanced Tools and settings.

If someone from Bell or another frustrated XBOX & Bell customers have found a work around, please let me know.

[Luca]

Doesn't make sense that it was working perfect before changing modems from a new isp. I've seen many posts about this, you'd think bell would be aware of the issue and try to implement a fix. 

[dks]

While I can't speak for Bell, I know that it is their policy that they do not support third party equipment. In other words, we get the modem and have to make it work for our own equipment ourselves. An xbox falls into that category. Or at least that is how Bell has seen it in the past. If you have not tried it, a router behind the Giga Hub may be a possible solution, as has been suggested earlier. 

[Luca]

I've tried both a router and a switch, still not working. It's a modem problem, as I stated it was working on other isp the same morning before the switch to new isp. 

[Vanadiel]

Does the XBOX receive an IP? That would be the first thing to check for, as no flashing lights on the LAN ports of the modem are not normal.

[Luca]

Yes, both xboxs have ips 

[Vanadiel]

Under advanced network settings in the xbox, try setting 1.1.1.1 as DNS server.

Just to rule out any DNS issues: Setup DNS XBOX 

[Luca]

I will try that this evening after work and update you. Thanks 

[Vanadiel]

Pending on the results of that, you also mentioned you have tried a router I am assuming behind the home hub.

While the home hub unfortunately does not support VPN natively, and neither does the XBOX, if the router you used supports VPN services that would be a third option.

[Luca]

I've thought of using a VPN, but I'm worried about latency issues. I'd like to get this resolved considering I'm not the only person having this issue with this home hub from bell. I'm also hoping I hear back from my request for an escalation from tech support as well. It's a real downer when your hoping everything is just plug and play then it turns out to be a big issue. I'm sort of regretting leaving rogers at this point. It's frustrating. 

[Luca · Accepted solution]

so heres an update on what i've found to be the issues. Firstly, for some reason XBOX and the new gigahub 4000 will not connect on cat5e, but my pc will connect with cat5e with zero issues. I ran a temp cat6 cable to one of the xboxs and it connected, done. The second Xbox was running through a POE connection since the bedroom its in doesn't have any network outlets. Considering before i had rogers cable internet, POE ran perfectly since power lines are copper like cable lines. For this connection i also connect a cat6, it was picking up the xbox showing as connected in the hub, but wasn't getting any internet. So abit of googling, i come to find that the giga hub is not compatible with POE UNLESS you get a special switch. So, to fix this, i will just fish a cat6 cable to the room and problem solved. Hopefully others that have ran into this issue will have some better clarification now.

[dks]

This is an excellent piece of "try and see" research. Thank you. I have flagged it as an accepted solution. My own experience with Power Over Internet (POE) has not been good, particularly in an older home with older wiring dating from the 1950's. I also suspect that length of the wiring run may also be a factor. Please report your results of the "fishing expedition", too. 

[Luca · Accepted solution]

I have found and solved the fix thanks to xbox tech support over the phone. I'll just recap. After running the new cat6 cables, the modem port was showing connection going through to the xbox....BUT still nothing when i went into the network settings in the xbox itself. Heres the fix from xbox support and it worked! Go into network, advanced settings, go to dns settings, and then for primary enter 8.8.8.8. And for secondary enter 8.8.4.4 after hitting select, go back 1 screen and you will be back online! 

[Vanadiel]

I bet 1.1.1.1 would work also.

[Luca]

Either way, it's back up and running. I've got a happy 11 year old who can get back on fortnite and I can get back into my games haha. Glad this worked out. Hopefully others will find this useful.