• We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
Sep 20, 2011
4
0
Hello fellow Magickians,

Lately I've been hosting a couple of games and suffered a lot of client disconnects while hosting a game.
Clients would disconnect after 30 seconds to 2 minutes all with the standard disconnect error message.
By this point I already reinstalled the game/steam, drivers, etc, etc but this didn't solve the problem.

So I started packet sniffing my network and discovered a lot of TCP retransmissions were happening during the game.

What worked for me was disabling Jumbo Frames on my NIC and I could host games for hours without issues.

So if you have disconnect issues it might be worthwhile to check if you have enabled Jumbo Frames.

Fixing it:

The somewhat more permanent way:
If you don't need Jumbo Frames.

Go to >>Control Panel\Network and Internet\Network Connections and open the properties of your Network card then select Configure > Advanced tab \
and you'll find a setting called Jumbo Frames you can disable this setting. (or lower the value to a setting that works for you)


The temporary way:
E.g. adjust the MTU value before running the the game.

Run the commands below from a administrative CMD line!

If you have Jumbo Frames enabled you most likely find a MTU higher than 1500
To show your MTU size run the following command:

netsh interface ipv4 show subinterfaces

(Your output might differ)

MTU MediaSenseState Bytes In Bytes Out Interface
------ --------------- --------- --------- -------------
1500 5 0 0 Local Area Connection
9198 1 0 0 Local Area Connection 2 <- in my case #2

To temporary change the MTU settings run the following command:

netsh interface ipv4 set subinterface "Local Area Connection 2" mtu=1500

And after playing the game you could change the MTU back to the previous value of 9198 or whatever your previous setting was.

Hope this helps.
 
Maybe this is why some people keep disconnecting while others have no issues?
Perhaps it's all about whether your ISP supports Jumbo Frames?

Maybe someone from Arrowhead should do a little testing and see if that's the issue and if the net code can be throttled down to not use jumbo frames?