I just grabbed the 1.9.3 version of the dedicated server and client. i have each set up on thier own computer. I already run cs:source, hl2:dm, tf2, and other mods of source games on the system running the standalone dedicated server. I play the client versions of the above on a separate computer where i have steam installed.

I have read the installation instructions, gone through each the fixes (including the reinstall several times) listed in the wiki FAQ and searched these forums (for about 2 hours or so).

when i try to connect my gaming pc (running steam and teh client) to my server pc (running srcds) i get the "Disconnect: server uses different class tables" error. I've never had any other version of sourceforts to conflict and i'm not trying to connect to a server with an unknown version.

I can run a listen server from my gaming pc (by my self) with no issues and I have successfully connected to other internet-not-mine dedicated servers (reported with version 1.9.3 in steam servers list) so i believe the issue is with the dedicated server files. None of my other srcds dedicated servers (including hl2:dm) have any issues so it isn't a network or conflicting software issue - in fact i'm not getting any errors reported by the server whatsoever.

However I've never seen this error before (aside from these forums, which mostly direct to the wiki/faq/install instructions) and i'm really not sure how to fix it.

Has anyone else had this issue or bad luck with the 1.9.3 dedicated server? anyone had the class tables error persist through the known fixes and/or only ever used the 1.9.3 version?

As i mentioned, i'm running both boxes (server and client) so i should have any trouble testing any thoughts you guys might have.

Thanks in advance, i'm really hoping to get sourceforts working as it seems like a fantastic mod!

Please check if you really updated Sourceforts to 193, this error usually happens only if the client-/serverbinaries are not compatible. If you are sure that you updated everything correctly download http://mirror.player.to/sourceforts/193binaries.7z and extract it to both server's and client's sourceforts/bin directory.

Thank you for your quick response i'll definitely try the binaries in that link when I get home. I assumed since i never had run sourceforts before (and did not have any other/older binaries to update) that they would match. At one troubleshooting attempt I even copied the files from the client (which appears to work with internet servers) straight into the server directory to make sure they were the same.

Thanks again and i'll post the results if the file in that link worked as soon as i can try it *fingers crossed*

-- soucpan

If it doesn't work my 2nd guess is that you don't run the server from the same path where srcds_run is located. You have to launch it via ./srcds_run -game sourceforts +map.... (linux)

well, i took the server.dll and replaced it from the above archive (didn't touch the client pc) and everything seemed to work great!

i'm quite curious as to why these binaries (client.dll and server.dll) are different from the ones packages in the zip archives on the main download site? both say their 1.9.3, but for example there's almost 1.5 megs of difference in file size alone between the two client.dll files. i couldn't tell too much difference between the two with a quick look in a hex editor or too much difference between the strings. i'll poke around some more when i have time

but for now i fired up the server the same way i had before with the replacement server.dll - then fired up steam on my client pc connected and was in the game!

Thanks again for your help any ideas as to the differences between the dll's in the zip files listed and the binaries you linked to? (i also noticed that the mirror with those binaries was the only one to offer the setup as an exe)

time to play some sourceforts! w00t!

i know, it's my server any my setup app

these binaries contain a patched scoreboard.

sweet talk about top tier support! One more quick question: do i still need to replace the client binary since everything worked upon replacing the server binary?

thanks for all your help and for your hard work.

-- soupcan