Port Forwarding on Youfibre

Hi Tez, my name is Rodrigo. I'm an Independent Advisor and a member of the Microsoft community and I'd love to assist you today.

I am sorry to hear that.

I don't have a tutorial for the Youfibre, but these guides* should be able to help you set your device IP on the DMZ of your router.

https://www.windowscentral.com/xbox-one-dmz-guide

https://www.ubisoft.com/help/connec...article/setting-up-dmz-for-xbox-one/000061024

There is also this complete guide about NAT errors and configuration on the Xbox website, I recommend it:

https://support.xbox.com/help/hardware-network/connect-network/xbox-one-nat-error

----------------------------------------
Setting the DMZ
----------------------------------------

----------------------------------------
A) On your Router
----------------------------------------
1. Make sure to use the ethernet cable connection, it is more reliable than the Wi-Fi one. (If possible)

2. You then, have to assign a static (fixed) IP for your Xbox console on your router, which will enable you to do the next steps

3. Turn on DMZ under the IP you selected for your Xbox Console.

4. Turn on UPnP on your router

By doing that, you'll pretty much have an open and direct connection to the game servers.

----------------------------------------
B) On the Xbox Console
----------------------------------------

Configure the network settings accordingly.

Enter the Settings menu.

Under the General tab, select Network Settings then Advanced Settings.

Take note of the information displayed

Select IP Settings > Manual.

Enter the same IP you configured on your router DMZ.

I hope this helps.

-----
*Note: This is a non-Microsoft website.

The page appears to be providing accurate, safe information.

Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products).

Thoroughly research any product advertised on the site before you decide to download and install it.

I've had a ticket with YouFibre for this exact same thing since November 22, they've been in contact with Microsoft to try and get it resolved. Sadly Microsoft support is the worst I've ever seen, tried logging it with them for 3 months, eventually gave up trying, so don't think YouFibre trying will improve anything.

Either change your console or change your ISP.

Doesnt it get a bit repetitive just running around shooting people Strange?

That's what I've done.

I think really the problem is the game.

The only people that really know for sure are Treyarch. I don't understand how a developer can have so little pride in his work. You spend your time developing a game you presumbaly love and then, when it's released, ignore every single complaint and make
no effort to even engage with the community that pays your wages about the game's problems. I bet there are a ton of game developers that would kill to produce the world's biggest selling game franchise, yet Treyarch and David Vonderhaar don't care - and noone
asks him what's going on. No gaming website or magazine seems to think it worth their time to ask him what's up! The biggest game on the planet!

I've tried everything I can think of. I'm not going to mangle my router settings permanently for one game, but i've opened ports, closed ports, used the DMZ, not used the DMZ, tried all sorts of static IP's, adjusted this and that, I've tried playing with
the worst connection preferences, I've tried playing whiel caning bittorrent. To paraphrase Steve Harley, I've done it all. It doesn't seem to make any real difference, so the problem must lie in the game's coding.

What does it say about the industry that the biggest gaming franchise is so badly served. If it worked I'd enjoy it. I've never had an issue with CoD. Sure there are things that need fixing in the gameplay (quickscoping), but that's small potatoes compared
to being able to play it.

As far as lag compensation goes, for all i know that may be an urban myth. Either I have a terrible connection which is why i lag, or i have a really good connection and i'm throttled back by lag comp. It can't be both.