Client communication failure

EZCChaos · Post by **EZCChaos** » Tue Apr 20, 2004 3:50 pm

On etpro 3.0.0/3.0.1 servers I get instant 999 ping that goes down on some servers if i'm the only one there but otherwise I get kicked for 'client communication failure.' What does this mean and how do I fix it?

Leviathan · Post by **Leviathan** » Wed Apr 21, 2004 2:29 pm

i had same Problem a fev minutes ago, but Server restart has fixed it...

No idea, what caused the Error

EZCChaos · Post by **EZCChaos** » Wed Apr 21, 2004 10:45 pm

sadly that doesn't solve my problem and I can't play matches until I find hte solution to this.

Post by **bani** » Wed Apr 21, 2004 11:25 pm

sounds like your network settings are wrong. snaps, cl_maxpackets and/or rate etc.

EZCChaos · Post by **EZCChaos** » Sun Apr 25, 2004 10:41 am

why do networks settings that work perfectly with shrub or normal ET and etpro2.0.7 fail to work with ETPro 3

EZCChaos · Post by **EZCChaos** » Tue Apr 27, 2004 10:38 am

someone said punkbuster needs to be updated to solve this but a fresh reinstall didn't help. does anyone know the answer to this?
Btw, rate snaps and cl_maxpackter aren't the problem (25000.20.30)

Post by **bani** » Tue Apr 27, 2004 10:45 am

try connecting to the quaketheism server 69.93.136.70:27969 and see if you get the problem.

EZCChaos · Post by **EZCChaos** » Tue Apr 27, 2004 2:09 pm

I did connect there and well I can tell i'll have that problem there when the server is populated but when its just me I start as a 999 ping and go down.

EZCChaos · Post by **EZCChaos** » Wed Apr 28, 2004 5:23 pm

I also got kicked for cl.snap.servertime<cl.oldFrameServerTime once when the same thing happens that normally kicks me for client communication failure.

Post by **bani** » Wed Apr 28, 2004 9:28 pm

EZCChaos wrote:I also got kicked for cl.snap.servertime<cl.oldFrameServerTime once when the same thing happens that normally kicks me for client communication failure.

'cl.snap.servertime<cl.oldFrameServerTime' should be impossible as it would mean time is going backwards.

it would seem to point to severe network problems...

EZCChaos · Post by **EZCChaos** » Fri Apr 30, 2004 11:07 am

I also get kicked for configstring>MAX_CONFIGURATIONS quite a bit if any of these errors are related?

Post by **bani** » Fri Apr 30, 2004 11:56 am

configstring>MAX_CONFIGURATIONS is an etmain bug. it means your client was dropping packets while connecting. usually means a poor network connection to the server.

EZCChaos · Post by **EZCChaos** » Fri Apr 30, 2004 2:17 pm

But how come I only get these errors to etpro3.0.0/3.0.1 and not etpro 2.0.7 or shrub?