Waiting for CDKey Authentication [EXE_AWATINGCDKEYAUTH] never stop

Wed Nov 26 11:11:37 EST 2003

Waiting for CDKey Authentication [EXE_AWATINGCDKEYAUTH] never stop

Hi,

I have that really annoying problem. I already wrote a mail similar to 
that one but maybe someone (best from IW) can try to help me this time.

If i want to join some Linux Servers (that i host myself) i cant connect 
because if the cdkey auth problem. You dont see a message that something 
is wrong with the key just a waiting for cd auth message...
I tryed to wait over 400 seconds already but no luck.
Once i got connected after 120 but nothing changed and 20 secs later not 
working again.

The biggest problem is that i also host game servers and i dont what can 
be wrong on the servers. Strange is that most customers can connect with 
any problem but i cant.
I read some post about network problems but I cant see any. Auth Server 
is resolving ok, we have ping under 20ms, no packet loss.

I can show you some logfile examples that show whats going on.
So we start a server all fine but i (141.30.225.46) cant connect because 
  the key problem but others can.
Just to be sure i have reinstalled the game some times with my original 
cd plates and nothing changed for me – same problem.

 >./cod_lnxded  +set net_ip 62.4.70.136 +set net_port 22222 +set ttycon
0 +exec rzg.cfg +set dedicated 2 +set developer 2

COD MP 1.1 build linux-i386 Nov 13 2003
----- FS_Startup -----
Current search path:
/home/enforcer/.callofduty/main
/home/users/rzg/cod/main/zzzzz_Hammer_Fixes_1.2.pk3 (8 files)
/home/users/rzg/cod/main/user_ultrarealism1.pk3 (34 files)
/home/users/rzg/cod/main/pak6.pk3 (3 files)
/home/users/rzg/cod/main/pak5.pk3 (4858 files)
/home/users/rzg/cod/main/pak4.pk3 (1668 files)
/home/users/rzg/cod/main/pak3.pk3 (1992 files)
/home/users/rzg/cod/main/pak2.pk3 (694 files)
/home/users/rzg/cod/main/pak1.pk3 (2642 files)
/home/users/rzg/cod/main/pak0.pk3 (12828 files)
/home/users/rzg/cod/main
/home/users/rzg/cod/main/localized_english_pak1.pk3 (3736 files)
/home/users/rzg/cod/main/localized_english_pak0.pk3 (1204 files)

File Handles:
----------------------
29667 files in pk3 files
execing default_mp.cfg
couldn't exec language.cfg
execing config_mp_server.cfg
couldn't exec autoexec_mp.cfg
Hunk_Clear: reset the hunk ok
Warning: cvar "sv_cheats" given initial values: "0" and "1"
Opening IP socket: 62.4.70.136:22222
Hostname: debian-136
Alias: gs3
Alias: gs3.eliott-ness
IP: 62.4.70.136
--- Common Initialization Complete ---
execing rzg.cfg
g_gametype will be changed upon restarting.
------ Server Initialization ------
Server: mp_brecourt
Hunk_Clear: reset the hunk ok
----- FS_Startup -----
Current search path:
/home/enforcer/.callofduty/main
/home/users/rzg/cod/main/zzzzz_Hammer_Fixes_1.2.pk3 (8 files)
/home/users/rzg/cod/main/user_ultrarealism1.pk3 (34 files)
/home/users/rzg/cod/main/pak6.pk3 (3 files)
/home/users/rzg/cod/main/pak5.pk3 (4858 files)
/home/users/rzg/cod/main/pak4.pk3 (1668 files)
/home/users/rzg/cod/main/pak3.pk3 (1992 files)
/home/users/rzg/cod/main/pak2.pk3 (694 files)
/home/users/rzg/cod/main/pak1.pk3 (2642 files)
/home/users/rzg/cod/main/pak0.pk3 (12828 files)
/home/users/rzg/cod/main
/home/users/rzg/cod/main/localized_english_pak1.pk3 (3736 files)
/home/users/rzg/cod/main/localized_english_pak0.pk3 (1204 files)

File Handles:
----------------------
29667 files in pk3 files
Sys_LoadDll(/home/enforcer/.callofduty/main/game.mp.i386.so)... failed
Sys_LoadDll(/home/users/rzg/cod/main/game.mp.i386.so)... ok
Sys_LoadDll(game) found **vmMain** at  0x48a6add4
Sys_LoadDll(game) succeeded!
------- Game Initialization -------
gamename: main
gamedate: Nov 13 2003
0 teams with 0 entities
-----------------------------------
-----------------------------------
Resolving codmaster.activision.com
codmaster.activision.com resolved to 63.146.124.59:20510
Sending heartbeat to codmaster.activision.com
SV packet 62.197.75.223:28960 : getinfo
Hitch warning: 2660 msec frame time
Warning: cvar "scr_allow_vote" given initial values: "1" and "0"
SV packet 67.23.100.117:28960 : getinfo
SV packet 80.222.115.253:28960 : getinfo
SV packet 81.79.133.224:28960 : getinfo
SV packet 213.251.108.27:28960 : getinfo
SV packet 81.49.72.247:28960 : getinfo
SV packet 217.42.178.59:28960 : getinfo
SV packet 80.199.171.58:28960 : getinfo
SV packet 141.30.225.46:2688 : getstatus
SV packet 141.30.225.46:2688 : getstatus
SV packet 141.30.225.46:2688 : getstatus
SV packet 80.137.111.188:28960 : getinfo
SV packet 80.248.116.164:28960 : getinfo
SV packet 212.20.141.66:-18618 : getstatus
SV packet 217.225.5.108:28960 : getinfo
SV packet 217.238.97.159:28960 : getinfo
SV packet 81.84.112.133:28960 : getinfo
SV packet 217.238.93.29:28960 : getinfo
SV packet 172.180.66.3:28960 : getinfo
SV packet 62.79.142.167:28960 : getinfo
SV packet 217.120.118.210:3202 : getstatus
SV packet 68.10.176.57:28960 : getinfo
SV packet 141.30.225.46:2693 : getstatus
SV packet 141.30.225.46:2693 : getstatus
SV packet 141.30.225.46:2693 : getstatus
SV packet 141.30.225.46:2694 : getstatus
SV packet 81.128.39.32:-32662 : getinfo
SV packet 80.160.94.80:17292 : getinfo
SV packet 141.30.225.46:28960 : getchallenge
Resolving codauthorize.activision.com
codauthorize.activision.com resolved to 63.146.124.59:20500
sending getIpAuthorize for 141.30.225.46:28960
SV packet 24.10.47.97:28960 : getinfo
SV packet 80.36.58.80:28960 : getinfo
SV packet 63.146.124.59:20500 : ipAuthorize
SV packet 141.30.225.46:28960 : getchallenge
sending getIpAuthorize for 141.30.225.46:28960
SV packet 63.146.124.59:20500 : ipAuthorize
SV packet 141.30.225.46:28960 : getchallenge
sending getIpAuthorize for 141.30.225.46:28960
SV packet 62.80.116.156:28960 : getinfo
SV packet 63.146.124.59:20500 : ipAuthorize
SV packet 211.242.234.14:28960 : getinfo
SV packet 217.42.165.218:28960 : getinfo
SV packet 141.30.225.46:28960 : getchallenge
sending getIpAuthorize for 141.30.225.46:28960
SV packet 63.146.124.59:20500 : ipAuthorize
SV packet 80.222.115.253:28960 : getinfo
SV packet 210.82.111.67:-9474 : getinfo
SV packet 213.15.69.3:8272 : getstatus
SV packet 194.251.249.103:27243 : getstatus
SV packet 220.70.179.59:28960 : getinfo
SV packet 81.204.170.19:10245 : getinfo
SV packet 80.13.60.37:28960 : getinfo
SV packet 68.2.198.22:-32503 : getinfo
SV packet 66.153.61.227:-4682 : getstatus
SV packet 217.85.240.233:16701 : getinfo
SV packet 213.224.141.87:28960 : getinfo
SV packet 24.202.80.233:28960 : getinfo
SV packet 217.149.102.82:10532 : getstatus
SV packet 68.164.152.122:28960 : getinfo
SV packet 68.110.74.76:28960 : getinfo
SV packet 213.17.38.18:-387 : getinfo
SV packet 62.243.148.217:28960 : getinfo
SV packet 172.180.66.3:28960 : getinfo
SV packet 80.181.205.126:1145 : getinfo
SV packet 66.124.225.44:28960 : getinfo
SV packet 213.203.74.206:3831 : getstatus
SV packet 194.251.249.103:27243 : getstatus
SV packet 150.101.114.202:-2647 : getstatus
SV packet 217.211.109.109:28960 : getinfo
SV packet 24.202.80.233:28960 : getinfo
SV packet 80.201.194.146:28960 : getinfo
SV packet 213.203.74.206:28960 : getchallenge
sending getIpAuthorize for 213.203.74.206:28960
SV packet 63.146.124.59:20500 : ipAuthorize
SV packet 213.203.74.206:28960 : getchallenge
sending getIpAuthorize for 213.203.74.206:28960
SV packet 63.146.124.59:20500 : ipAuthorize
SV packet 62.195.48.46:23014 : getstatus
SV packet 81.76.160.103:28960 : getinfo
SV packet 213.203.74.206:28960 : getchallenge
sending getIpAuthorize for 213.203.74.206:28960
SV packet 63.146.124.59:20500 : ipAuthorize
SV packet 213.203.74.206:28960 : getchallenge
sending getIpAuthorize for 213.203.74.206:28960
SV packet 63.146.124.59:20500 : ipAuthorize
SV packet 68.18.88.133:-15434 : getinfo
SV packet 220.70.179.59:28960 : getinfo
SV packet 213.203.74.206:28960 : getchallenge
sending getIpAuthorize for 213.203.74.206:28960
SV packet 63.146.124.59:20500 : ipAuthorize
SV packet 217.123.76.114:28960 : getinfo
SV packet 81.83.113.196:28960 : getinfo
SV packet 210.82.111.67:-7813 : getinfo
SV packet 213.203.74.206:28960 : getchallenge
sending getIpAuthorize for 213.203.74.206:28960
SV packet 63.146.124.59:20500 : ipAuthorize
SV packet 213.203.74.206:28960 : getchallenge
sending getIpAuthorize for 213.203.74.206:28960
SV packet 63.146.124.59:20500 : ipAuthorize
SV packet 62.194.233.77:28960 : getinfo
SV packet 213.203.74.206:28960 : getchallenge
sending getIpAuthorize for 213.203.74.206:28960
SV packet 63.146.124.59:20500 : ipAuthorize
SV packet 80.110.10.192:28960 : getinfo
SV packet 80.163.37.125:1484 : getstatus
SV packet 61.63.48.124:16896 : getinfo
SV packet 217.42.178.59:28960 : getinfo
sending getIpAuthorize for 212.194.177.31:28960
SV packet 63.146.124.59:20500 : ipAuthorize
SV packet 212.194.177.31:28960 : connect
SVC_DirectConnect ()
Client 0 connecting with 100 challenge ping

The last guy can connect without any problems without any reason i see.
I dont see any problem why it behaves that way.

Some more details.

About the Server:
    Server is visible on game spy.
    Server is located in France.
    Server is an Dual System with high memory support in Kernel.

About the Players.

The Player that can connect i dont know. Its a customer.
The 141.30.225.46 is me.
Im using the key from an original German version.
My Network setup is a kind of tricky. My internal ip is not the internet
  ip. I also have 2 external ips.
But the rigth ip is authed – it is the one i use on SNat for that
connection so no problem as far as i can see.
I can join some other Servers also some in USA. Im not sure that they
all check the key but some will do i think.

It looks that i dont have that Problem on Windows based Servers.

Maybe you can explain little more how auth is working
(if not because security - well)

So it is working for most of our customers but not for me who is sitting 
behind an linux router. (Yes my setup is ok i can play on non key 
checking servers and other games and stuff - if you want you can see an 
tcpdump)
I also know a person with same problem and direct connected windows machine.

If you need more details please let me know but man I really want to get 
this problem solved.

Cya and THX for ANY ideas.
Daniel

PS: you are very welcome to make any test you like we also can talk
about monitored ssh access.