06-19-2013, 12:33 AM
Well whatever it's waiting on the client for, it must have been doing it out of order or unexpectedly. I'll see if I can tell from a packet sniff. If the client is the common factor then the problem must be in what the server was waiting for. Soft restarting the server must have forgotten to clean up completely, leaving this messed up after the soft restart. If I can't figure it out, I'll try protoproxy.