12 replies to this topic

[Misfire]

I am having some problems getting my servers added to the setti list.

I already have my CSS: OB server added, it was added instantly.

Go here and see, http://css.setti.info/servers/full/

96.242.154.103:27015 [ChenZen.org] Deathmatch 24/7 Office/Dust2 NYC |NO AWP/AUTO|

It is there and running fine. However I am trying to add my Obsidian Conflict server but it does not get added.

The ip is
96.242.154.103:27017

Same IP, just different port. I have waited a week and nothing has worked, it is using esteamation 1.8 while the CSS one is using 2.0RC6. I have also tried revemu and same thing. Please help.

I see other obsidian conflict servers up so I know its not a problem, no matter what I can't get it on the list.

http://css.setti.inf...search/obsidian

Can one of the admins add manually please or help me figure out what is wrong.

[Ghost]

Hmm.. weird. Your DM server is just fine, but the Obsidian server fails the verification check. Have you enabled everything in rev.ini and allowed all clients? It usually helps if something's wrong. Allow everything and then work your way narrower if you want to limit something.

[Misfire]

Hmm.. weird. Your DM server is just fine, but the Obsidian server fails the verification check. Have you enabled everything in rev.ini and allowed all clients? It usually helps if something's wrong. Allow everything and then work your way narrower if you want to limit something.

Thanks for the reply ghost. That server is on esteamation 1.8 right now, I just enabled to allow everything in the config and restarted. I know for sure its cracked because I am able to join it with cracked client.

The reason for using an older esteamation is because obsidian conflict runs on an older orange box version.

[Misfire]

Have u guys changed the way it verifies the past few years?

I remember about 2 years ago I put up an obsidian conflict server with the exact method of cracking and it got added to SETTI just fine and fast too.

So its not passing verification now I guess, setti scanner doesnt get in.

I had to work around it, I changed the port of my CSS DM server to 27017, added server, it got added instantly. Then I put the obsidian server onto port 27017 so my OC server is now listed. I didn't want to do this workaround so I hope you guys can figure out whats worng.

[Ghost]

Nice workaround. The workaround works for a while until the next time the server is again tested automatically. So it's not good workaround, after all.

The verification system hasn't changed dramatically. There have been small updates which may have affected to the verification process.

It seems you know what you're talking about, so you could probably try to help solving this issue. The stuff that we need to get to bottom of this is network dump of you joining your patched server with patched client. You can use Wireshark [ http://www.wireshark.org/ ] to capture network data on your connection. Just run the server as usual, then start Wireshark and join the server. Quit the game, stop capturing and then send the network capture by PM. Then it's possible to see what the server and client are "discussing" and why it's different than what Setti's doing right now. Also it'll be nice to see why it's different than the DM server.

[Misfire]

Nice workaround. The workaround works for a while until the next time the server is again tested automatically. So it's not good workaround, after all.

The verification system hasn't changed dramatically. There have been small updates which may have affected to the verification process.

It seems you know what you're talking about, so you could probably try to help solving this issue. The stuff that we need to get to bottom of this is network dump of you joining your patched server with patched client. You can use Wireshark [ http://www.wireshark.org/ ] to capture network data on your connection. Just run the server as usual, then start Wireshark and join the server. Quit the game, stop capturing and then send the network capture by PM. Then it's possible to see what the server and client are "discussing" and why it's different than what Setti's doing right now. Also it'll be nice to see why it's different than the DM server.

Thanks again, I will capture the packets later today and send you the information as requested.

[Ghost]

Great. That'll probably sort couple problems for other server admins too - if the problem is truly obsidian related.

[Misfire]

Great. That'll probably sort couple problems for other server admins too - if the problem is truly obsidian related.

Okay, I just PM'd you the dumps. I'm not sure if its obsidian related but maybe because it is using an older orange box engine.

[Ghost]

Fixed. Maybe it's the old engine.

Good work

[Misfire]

Fixed. Maybe it's the old engine.

Good work

yeah, mark this baby as solved, its working perfect.

[Ghost]

Sieger, thanks, good post.

I think I've found the problem and fixed it. The problem was indeed related to the new v45 update. It's weird that any of the old v34 servers were listed anymore. Maybe they weren't.. as everybody was saying