[cod] help me :(

[Ivo Silva]

Are you both setting up your +ip?

Something like this "./cod_lnxded +set dedicated 2 +ip 24.199.16.170( place here your ip, not this one) +set net_port 28959 +set ttycon 0 +exec server_sd1.cfg"

In the +ip put your net ip(the same ip that you will try to connect) and not this on, this is an example!

And did you both, placed in the /etc/hosts this "192.168.100.200 codauthorize.activision.com codauthorize" ????

Check those things please... ;)

- Ivo Silva


  ----- Original Message ----- 
  From: James Kreuziger 
  To: cod at icculus.org 
  Sent: Monday, November 24, 2003 6:52 AM
  Subject: RE: [cod] help me :(


  I can vouch for having the same sort of problem Nathan.  I can get a Linux server running, I just 

  can't connect to it.  I get the dreaded "Awaiting CD key authorization" message.  I've even opened 

  up the server as the DMZ host on the router.  No dice.  



  Funny thing.  I can setup a dedicated server on my Win XP box, not have to open up a SINGLE port 

  On my router OR on ZoneAlarm, and it works fine.  I setup a MOHAA server on the Linux box tonight 

  and had absolutely zero problems.  I'd like to get the Linux CoD server running, even if it was just on my LAN.  

  Even that doesn't work.



  -Jim

  -----Original Message-----
  From: Nathan Peters [mailto:natedog550 at hotmail.com] 
  Sent: Sunday, November 23, 2003 4:20 PM
  To: cod at icculus.org
  Subject: Re: [cod] help me :(



  I've got somethin' sorta similiar.  I got my server to run finally.  It says that it resolved to my external ip:20510 and also to 20500.  But when i try to connect to it internally it waits for CD authorization and never connects.  And for the heck of it i went into the internet listed servers and it showed up.  So i connected to it but it just sat there.  And it gave the ip:-1989  But it never talked about cd authorization.  And -1989 , what's up with that number?  Neways, I opened up the 20510 and 20500 and 28960 on my router but it still isn't workin'.  My internal network is 125.125.125.xxx  Can anyone help me also?  Thanks.

  ----Original Message Follows---- 

  From: "mike" 

  Reply-To: cod at icculus.org 

  To: 

  Subject: [cod] help me :( 

  Date: Mon, 24 Nov 2003 00:07:15 -0000 

  MIME-Version: 1.0 

  Received: from icculus.org ([66.219.41.214]) by mc5-f37.hotmail.com with Microsoft SMTPSVC(5.0.2195.6713); Sun, 23 Nov 2003 16:07:24 -0800 

  Received: (qmail 23587 invoked by alias); 24 Nov 2003 00:07:11 -0000 

  Received: (qmail 23580 invoked from network); 24 Nov 2003 00:07:10 -0000 

  X-Message-Info: JGTYoYF78jFM12/rZpK5KqMzNlalFtQl 

  Mailing-List: contact cod-help at icculus.org; run by ezmlm 

  Precedence: bulk 

  X-No-Archive: yes 

  List-Post: 

  List-Help: 

  List-Unsubscribe: 

  List-Subscribe: 

  Delivered-To: mailing list cod at icculus.org 

  Message-Id: <200311240002.hAO023Xo005465 at mnjhost.com> 

  X-Mailer: Microsoft Office Outlook, Build 11.0.5510 

  Thread-Index: AcOx1L934cst8QlmTBOavEerXgELLgASYPeQ 

  In-Reply-To: <00cf01c3b1d5$5db0e3d0$0501a8c0 at deltacity> 

  X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 

  Return-Path: cod-return-542-natedog550=hotmail.com at icculus.org 

  X-OriginalArrivalTime: 24 Nov 2003 00:07:24.0566 (UTC) FILETIME=[F03AE360:01C3B21E] 

  Hi all 

  Please forgive me but I have got my COD server running and it seems ok. It 

  has resolving to blaa blaa and looks ok. 

  But I cannot connect, I have a internal network running on 192.168.42.1 etc 

  but how can I check that its bonding to the external number? 

  Sorry if this seems simple but maybe its just late. I have setup a ut2003, 

  sof2, ut, star wars, etc server with no trouble...But this ones really doing 

  my head in. 

  Any thoughts would be great :) 

  mnj 





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

  Groove on the latest from the hot new rock groups! Get downloads, videos, and more here. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://icculus.org/pipermail/cod/attachments/20031124/0e89d881/attachment.htm>