How often is "sometimes"? As long as that doesn't happen every other race, that are just disconnections, random hiccups of your or the other players' internet connections that make the Wii disconnect.

Using LAN instead of WLAN might help a bit (if you currently use WLAN).

This is happening to me as well but more serious, I've been unable to play as every time I find a match I dc from it. Please can someone help me?

Well there's loads of terrible hosts constantly going in (and out) so for now, that's 'normal.'

The newest mkw-ana with its room status view is a good way to identify problematic users-

Maybe suspend bug? Probably very bad Internet.

Also, I don't think he's banned because if you are banned you can't even connect.

As I haven't experienced myself but found while scavenging on this board: if I recall correctly this 'suspend bug' is a profile ban. The specific profile (friend code) is banned and therefore you can not search for worldwides for it. A console ban would probably be the one where you can't connect to the server.

One of my friends has the suspend bug but he has been never banned on Wiimmfi. o:

The "suspend bug" is not a personal thing. And nowadays I think, it is not really a bug, but a workflow and NATNEG issue.

New knowledge of last weeks after watching NATNEG connection statuses and some other packets (so not 100% sure):

Usually in global races, the host communicate with its guests about the suspend status and send suspend=off after race start. But sometimes there are network problems and the communication fails. Reasons are bad network lines or if the host is to busy because of many unresolved NATNEGs. For each missed NATNEG the a player (and mostly the host) becomes proxy and must receive and send much more records. The result is, that line of the host can't send a ll packets and some UDP packet are dropped.

A player is banned, if a moderator things, the he is the reason for an unstable room. In the future the server will help to find the initiator and maybe kicks automatically players.

@Leseratte
Right?

Maybe there are some different meanings for "suspend bug". I meant a technical issue.

What I refer to as the "suspend bug" is more of a feature than a bug: If the host workload is too high from NATNEG failure, when a race begins, the host and all clients will not set suspend to zero (or false), thus making the room unjoinable until the problem resolves. Presumably this is an effort to prevent host overload. However, in many instances, NATNEG never completes successfully, and thus the room stays with suspend set to 1 forever.

There are more problems too; for any room with the suspend "bug", these things can happen:

- Suspend will always go to zero if anyone disconnects, even if the person who disconnects is not the cause of the problem.
- Suspend can also go to zero at the voting screen if people disconnect on it, which has bad consequences (the room will hang if anyone tries to join while voting).
- If someone chooses to quit at the end of a race while the suspend bug is in effect, if they are the first person to press a button out of all players in the room, everything will function normally. If they are last person to press a button, the room will have suspend zero at the voting screen but can still advance if nobody else attempts to join. If they leave somewhere in the middle, the game will hang with half the players on the track, half on the voting screen, with suspend zero, and the room will almost always disconnect after a timeout.

It's hard to say whether the bug exists in the GameSpy implementation of the networking or Nintendo's understanding thereof, however a feature that is designed to help rooms remain stable causes far more harm than good in most cases. The (current) only way to properly resolve it is to disconnect the offending player while the race is in progress, to avoid the consequences of disconnecting them at any other time.