[cod] And with the patch the problem with NAT is back

[Ron Orrick]

in the hosts file on the Natted box (game server) enter two entries pointing
to the right address...

codmaster.activision.com xxx.xxx.xxx.xxx
codauthorize.activision.com    xxx.xxx.xxx.xxx

If the IP changes, make the changes again. You also have to allow ports
20500 and 20510. The current IP (for both) is 69.146.124.59.

Also, there are several more ports needed for gamespy... I don't know them
right off the top

R

----- Original Message ----- 
From: <cod at kaleplek.net>
To: <cod at icculus.org>
Sent: Friday, February 06, 2004 9:03 AM
Subject: RE: [cod] And with the patch the problem with NAT is back


> Yes this works if you want to use a private server. But i'm using a public
> server and then when i do this i won't show up in any list on the
> internet(ASE/gamespy).
>
> Lets give some background to everyone to put it in the light again :
>
> Internal workstation      Nat Server internal/external
>                            (with cod running on it)
> 10.5.1.123 -------------> 10.5.1.1 / 62.216.16.89 -------> Internet
>
> Connecting from my machine results that the server is seeing that adress
> is local and not remote and connects me not through nat but internal. Then
> the server is asking to authenticate me with my internal address by
> Activision. This is dropped by activision because private spaces are not
> allowed on the internet.
>
> What i'm looking for is a workaround/fix that is saying when it is a
> private range don't Authenticate on the internet everything else do
> Authenticate. Or even better when i can say don't Authenticate ETH1.
>
> Please is there somebody who know how to do this, or can push me in the
> right direction.
>
> Thanks
> Greetz
> Quint
>
>
> > You can add a line in your hosts file that points
> > codauthorize.activision.com at 127.0.0.1
> >
> >   _____
> >
> > From: orr [mailto:orr at cadetmail.uscga.edu]
> > Sent: 06 February 2004 02:30
> > To: cod at icculus.org
> > Subject: RE: [cod] And with the patch the problem with NAT is back
> >
> > I have the exact same problem there, shipmate.  Except i never even got
> > it to work for 1.1 and gave up... i figured patching to 1.2 would fix
> > it. That's not the case, eh?  How do I get my LAN server to stop
> > checking for a cd key (yes, i AM flagging +set dedicated 1)
> >
> > Thx
> >
> > -Tim
> > -----Original Message-----
> > From: Boy_One (COD System Admin) [mailto:cod at kaleplek.net]
> > Sent: Saturday, January 31, 2004 7:08 PM
> > To: cod at icculus.org
> > Subject: [cod] And with the patch the problem with NAT is back
> > Hi all,
> >
> > I posted this before and with your help i got it working to log on to my
> > own server. But now with the patch installed the problem is back. For
> > you who doesn't know my problem a little info.
> >
> > I have a server running on my linux machine at home. This machine also
> > gives me NAT to the internet. Now when i try to connect to it from
> > inside my LAN he tries to AUTH me by activision with my internal network
> > address.
> >
> > Before the patch he timed out and let me in. But now with the new patch
> > it is starting allover again. I know somebody said this was put on a
> > list to look at and maybe solve it. Is this done so and if the answer is
> > yes,  is there a cvar i have to set to let me connect to my server
> > again. Or is my nightmare back... :-( I hope not. Who can help me...
> >
> > Regards
> > Quint
> >
>
>
>
>
>