I've been in IT for 25+ years, now retired... How about you? I was pointing him in the right direction if it was not 343. Everyone blames 343 for every hiccup that happens when much of the time it's a problem with the end users equipment. I'm not going give a 10 page essay on IT, like I said in my second post, call MS and let them track down the problem ....
No offence, but I don't think that you're qualified to say what the reason is. Do you even understand what NAT does? It's probably not best to dish out advice and argue points unless you understand the subject well.
Sure it will, it did it to me... I'd play half way through a game and get kicked continuously. Dropped packets, freeze frame, etc. I checked my NAT and it was strict. I changed some setting in my router and cable modem and have never had the problem again..Like I said its probably the reason unless severs are having problems which isn't continuous.
Check you NAT: type in settings/network, middle of the page. If its not OPEN you'll get these kind of problems. If its moderate or strict that's probably the reason.No, the reason is that Halo 5s servers are unreliable. The average home user shouldn't have to reconfigure their internet just for this game.
Sure, an open NAT is always preferable for gaming, but a strict one won't be causing disconnects.
I agree that an open NAT is preferable, but there are tons of reasons that it could be displaying strict. And packet loss is an entirely different subject... if you do have packet loss then it'll cause all sorts of problems as the dropped packets have to be resent which causes delays.
There's literally hundreds of things that it could be, such as WiFi interference, firewall settings, ISP problems, server problems, etc etc. It's not like our Xboxes have a direct like to each other, they go through dozens of pieces of equipment.
So in other words you can't answer my question. As such, your tacit concession on the matter is accepted.
And no, it's not usually the end users fault, consoles are supposed to be easy to set up. You shouldn't require networking knowledge to get it to work. I have an open NAT, a wired connection, DMZ to the Xbox etc, yet I still get these errors. The fault it with 343, and to be honest people like you don't help the problem. We need to stand together instead of blaming each other, your post does nothing to help the situation. Please try to be helpful in future.
Saying that NAT is "probably the reason" is like saying that an engine management light is probably the reason a car isn't running right! There could be dozens of causes.
The only advice I'd give the OP is that Halo 5 seems to be particularly sensitive to WiFi connections. Switch to wired and you may drop less games. Again though, it's the games fault not the users as all other games work fine on WiFi.