Luigi Auriemma

Our server has been up and running for over 2 years and then all of the sudden I can't restart it at all. I get this:

DNS
...........DW_AUTHORIZING
Database: Assets Sync Started
Database: Assets Sync Finished
dvar set cl_paused 0
dvar set long_blocking_call 0
dvar set sv_network_warning 0
dvar set cl_network_warning 0
dvar set loc_language 0
dvar set loc_forceEnglish 0
dvar set language english
dvar set com_errorTitle Error
dvar set com_errorMessage Dedicated server authentication failure.

********************
ERROR: Dedicated server authentication failure.

Ive tried changing the IP and still get the same problem. Ive tried an old install that didn't have the callvote fixes, stats fixes, etc, from the lpatcher and still it won't start and I just get this:

Server not running.

Any ideas?

don't have idea.
isn't possible that Activision/Demonware have banned your server?

I guess it's not the case because otherwise the mesage would have been more detailed so I go for the technical problem, maybe the dns can't be resolved or something similar

Ive tried changing some DNS settings, but still have the same problem. Bah...

Same problem here since 2 days.

Not a firewall or dns problem, i can even ping the demonware servers .

codwaw log
--------------

bdLog[15114]: ../DemonWare/bdNet/bdUPnP/bdUPnP.cpp(334):
WARNING: Cannot shutdown class as it is already uninitialised!
bdLog[15114]: ../DemonWare/bdNet/bdNet.cpp(651):
WARNING: Socket bind failed, but subsequent close succeeded!
bdLog[15114]: ../DemonWare/bdNet/bdNet.cpp(651):
WARNING: Socket bind failed, but subsequent close succeeded!
bdLog[15114]: ../DemonWare/bdNet/bdNet.cpp(432):
WARNING: Failed to do IP and NAT discovery using stun.us.demonware.net
bdLog[15114]: ../DemonWare/bdNet/bdNet.cpp(432):
WARNING: Failed to do IP and NAT discovery using stun.eu.demonware.net
DNS
.DW_AUTHORIZING
********************
ERROR: Dedicated server authentication failure.

********************

Tcpdump log to demonware servers(my ip hidden)
---------------------------

11:22:04.835270 IP xxxxx> 209.170.122.47.3074: Flags [.],
ack 5, win 46, options [nop,nop,TS val 581303 ecr 417836753], length 0
11:22:05.071136 IP 209.170.122.47.3074> xxxxx: Flags [P.],
seq 5:16, ack 161, win 54, options [nop,nop,TS val 417836812 ecr
581303], length 11
11:22:05.071147 xxxxx> 209.170.122.47.3074: Flags [.],
ack 16, win 46, options [nop,nop,TS val 581362 ecr 417836812], length 0
11:22:05.071150 IP 209.170.122.47.3074> xxxx: Flags [F.],
seq 16, ack 161, win 54, options [nop,nop,TS val 417836812 ecr 581303],
length 0
11:22:05.071178 IP 9xxxx> 209.170.122.47.3074: Flags [F.],
seq 161, ack 17, win 46, options [nop,nop,TS val 581362 ecr 417836812],
length 0
11:22:05.166595 IP 209.170.122.47.3074> xxxxxx: Flags [.],
ack 162, win 54, options [nop,nop,TS val 417836836 ecr 581362], length 0

Best regards

ok this is definitely not a dns problem because the IP is correct and there is an exchange of data.

at the moment I don't remember how it's encrypted the data so don't know what they should contain and why the master server says that you must stay out.

have you done something different lately?
maybe allowed people with invalid cdkey or similar stuff?

Im a game isp and theres some cracked codwaw servers but most are originals and i have the same issue with any waw server with any ip(differents vlans). I dont think its a ban but just tested in my UK network(first one was in france) and auth is ok , servers start so... i have no idea. The problem started in saturday and there was no changes in my network as far as i know btw im contacting my datacenter just in case they made some changes in their backend.

have you tried to contact the demonware and the support of the game?

Yes, and had no reply.

Working again...

gnugeek what did you do to get it working again?

For me it was a temporary fix, but now I am out of working IPs. For example my colocation provider has allocated a block of ips for me. Here is an example:

99.99.99.194 - 99.99.99.198

To temporary fix this demonware crap I had to change the PC IP (Primary IP) of the machine to a different IP. So for example I would change it to:

99.99.99.195

This would then somehow authenticate my server with Demonware again, but would only work for 1 week.

Another week would go by and I would have to repeat the process. Well... the problem now is that I am down to my last IP which is 198 and I am willing to be on Sunday it will stop authenticating with Demonware.

I have contacted my provider who hosts my server at their datacenter and they have allocated me a secondary block of ips on a totally different ip range. To prepare myself for this ticking time bomb I have tested all 5 of these new allocated secondary ips, but none will authenticate with demonware even when I set the primary PC IP to a new IP that my provider gave me. I have tried contacting demonware which has virtually no contact info as well as activision, but I get no reply back.

I saw this thread http://www.fpsadmin.com/forum/showthread.php?t=17444 but, I don't think thats what were looking for.

All I really play is CoD5 so this is really dissapointing for me.

so if you change the IP it works... it sounds as a banning/blocking at 100%

Yea, but I had my provider give me a completely new ip range. First one starts with 66. This new one is 213 for example. Completely different ranges and none of the 213 have ever started a game server. Just makes no sence to me.

Well apparently were not the only ones having this problem. To view the problem check out this thread: http://www.facebook.com/topic.php?ui...10&topic=20545. Saw some guy from Europe had the same problem with his server and even a GSP is requesting assistance: http://www.facebook.com/topic.php?to...310#post124885.

aLuigi I know you mentioned in the past that your not familiar with CoD5, but I think I have narrowed this down enough in which you could really help. So my apologies if I am asking too much from you.

I got an idea that is similar to what you did for me with CoD4 with changing mods = no to mods = yes

When I changed my dedicated server's target line on the shortcut to set dedicated 1 from set dedicated 2 it tells the server that this is strictly for lan mode. Well the funny thing is I can still see/ping this server from Xfire, people who added this server to their favorites can still see it, and I can still rcon into it.

The problem is if I or anyone else connects they will get the following error:

"Server Not Authenticated"

Here is what it looks like from the CoDWaW console window:

SERVER: Adjusted client ping by 290 ms to 110 ms
Client 1 connecting with 110 challenge ping from 86.93.44.82:28960
rejected connection internet client when server is not authenticated

aLuigi would you be so kind to make another lpatcher for this so that the executable thinks set dedicated 1 is actually set dedicated 2? I am thinking this would do the trick and let people in by overiding demonware completely.

The line to search for would be "LAN client: set GUID to %u"

or

"rejected connection internet client when server is not authenticated"

So if you could set that to not reject for internet people connecting to LAN I think it may do the trick.

Also was thinking that setting dedicated 2 to actually be set dedicated 0 (a listen server) with an lpatcher since listen servers automatically authenticate with demonware.

Thanks aLuigi.

sorry but at the moment I can do nothing, no time and no desire

Its cool aLuigi. I actually was able to finally have somebody from Treyarch respond to my tweets and he ended up getting our servers fixed on the authentication! So they are all back to normal now! Woot! :D

Thanks Anyhow, aLuigi!