server protocol 40.39 expected 40.41

(doggerip) #1

Hi everyone, I get an error when trying to join on my server : I get the following message
ignored - protocol 40.39 expected 40.41
time out

I can’t find a solution, could you please help me ?

Thanks in advance, best regards

(Crytiqal) #2

Update your client/server to latest version

(doggerip) #3

Thx
Yes i tried to

(Qbix) #4

…

(doggerip) #5

Yes Server are already up to date …

Sorry I’m french and my english is awfully bad

(Smooth) #6

Can you check the details of the dedicated server brink.exe.

The latest version (as of June 27th) should be 1.0.23226.47907:

(doggerip) #7

Here are the Brink.exe details, I assume it’s OK ?

(Crytiqal) #8

Is that from your client or your server?

(doggerip) #9

yes, it’s the server-side .exe

P.S : I edited all my posts with the help of my new translator
:slight_smile:

(Crytiqal) #10

And what is your client brink.exe? :wink:

(HugePinball) #11

Yes, your server exe is the correct version.

The client-side brink.exe should be the same version (1.0.23226.47907) but a little larger filesize (5.40 MB).

EDIT:
Hmm… I just did a few tests and the only way I can get the same error you posted above is if I’m running old dedicated server files and trying to connect with an up-to-date client. Maybe you didn’t update all of your dedicated server files?

The dedicated server files updated in the last patch are:


Filename            File Size   File Version      Modified    CRC32
brink.exe           5,599,560   1.0.23226.47907   6/23/2011   0ff749e1
gamescriptx86.dll   1,090,376   1.0.23226.47907   6/23/2011   d9c042da
gamex86.dll         6,906,184   1.0.23226.47907   6/23/2011   26a64aa2
base\pak000.sdmd2   106,246                       6/23/2011   5923d351
base\pak000.sdpk2   498,268,578                   6/23/2011   d56a017d
(Singh400) #12

Either your client or server isn’t up to date. Redo the updates.

(mongolosaure) #13

Thanks for your replies guys,

After a more in-depth conversation with Doggerip, it appears clearly that the problem he was having was caused by the update not being applied yet when he tested his server.

It took him some time to realize that simple fact because other issues mixed with this one and rendered proper troubleshooting nearly impossible.

But these issues were caused by the server reseller, not by SD’s programming :slight_smile:

Again thanks everyone !