[cod] Problem with Dedicate COD and lan connection

COD System Admin cod at kaleplek.net
Sat Dec 13 08:09:18 EST 2003


All,

 

Thanks for al the answers, i thought so that this would be the problem, i only hoped it was easy to fix... Dammed...... Ok let's hope that this will be fixed....;-)

 

But the about mohaa the AUTH is there because when you have an illegal cd`-key you can't play on my server. So i know there is an AUTH. But i think it works different to the one in COD.

 

He maybe this would be a solution for the COD AUTH. Ryan if you are also in the mailing group can you answer this and give us a little push in the right direction????

Just to be sure i post this one also in the mohaa mailing group. Ryan if you are in both just give the answer here please???



Gr.

Quint



----- Original Message ----- 
  From: Steven Hartland 
  To: cod at icculus.org 
  Sent: Friday, December 12, 2003 18:52
  Subject: Re: [cod] Problem with Dedicate COD and lan connection


  I dont think you quite follow the problem here Jim its not that the server or the client cant
  see the auth server its that when the client connects to the LOCAL server it connects
  using its LOCAL address. Now when the server auths the client it sends the details of
  the client off to the auth server including the LOCAL client address. Part of the auth
  process is the auth server will try to contact the client directly since the address for
  the client sent to the auth server from the game server is a LOCAL address this
  step fails and the client authentication times out. As I said the only solution to this
  would be to have some sort of configuration option in the client that enabled
  it to communicate its REMOTE address to the server, that or change how the auth
  process works.

      Steve
    ----- Original Message ----- 
    From: James Landi 
    To: cod at icculus.org 
    Sent: 12 December 2003 17:34
    Subject: RE: [cod] Problem with Dedicate COD and lan connection


    Make sure that the box can communicate back to Activision's server(s) via ports 20510, 20500 and the game port of 28960.  All ports must be open so you can authenticate your server, report its status to the master server and accept clients to play the game. This is how you show up in the game browser



    By blocking the authentication url your not going to show up on any server list and only should be used when playing via private LAN.



    IW stated anyone blocking or redirecting  this authentication url, will result in your server not being listed on the master server thus you will not show up in any game browser.



    Hope this helps



    -Jim

    Owner Codadmin.com




----------------------------------------------------------------------------

    From: Steven Hartland [mailto:killing at barrysworld.com] 
    Sent: Friday, December 12, 2003 12:25 PM
    To: cod at icculus.org
    Subject: Re: [cod] Problem with Dedicate COD and lan connection



    That's the problem you cant fix it and have it report to the master. The client would need

    to be patched to make this work. MOHAA works as it doesn't have authentication.



        Steve / K

      ----- Original Message ----- 

      From: COD System Admin 

      To: cod at icculus.org 

      Sent: 12 December 2003 17:01

      Subject: Re: [cod] Problem with Dedicate COD and lan connection



      Steven,





      A question who is them??? i own my own server this server is also my firewall and nat translator. And what do you mean by NAT'ed config option on the client??? Don't you mean my iptables rules???

      Please help me because Mohaa works, and this is authenticating me also on EA.....



      Regards

      Quint
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://icculus.org/pipermail/cod/attachments/20031213/1812c561/attachment.htm>


More information about the Cod mailing list