Deprecated: Assigning the return value of new by reference is deprecated in /home/gameadm/public_html/forums/includes/init.php on line 49

Deprecated: Assigning the return value of new by reference is deprecated in /home/gameadm/public_html/forums/includes/init.php on line 97

Deprecated: Assigning the return value of new by reference is deprecated in /home/gameadm/public_html/forums/includes/init.php on line 101

Deprecated: Assigning the return value of new by reference is deprecated in /home/gameadm/public_html/forums/includes/init.php on line 109

Deprecated: Assigning the return value of new by reference is deprecated in /home/gameadm/public_html/forums/includes/init.php on line 120

Deprecated: Assigning the return value of new by reference is deprecated in /home/gameadm/public_html/forums/includes/init.php on line 124

Deprecated: Assigning the return value of new by reference is deprecated in /home/gameadm/public_html/forums/includes/init.php on line 132

Deprecated: Assigning the return value of new by reference is deprecated in /home/gameadm/public_html/forums/includes/init.php on line 201

Deprecated: Assigning the return value of new by reference is deprecated in /home/gameadm/public_html/forums/includes/init.php on line 421

Deprecated: Assigning the return value of new by reference is deprecated in /home/gameadm/public_html/forums/includes/class_core.php on line 2384
<br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in <strong>/archive/global.php</strong> on line <strong>26</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in <strong>/includes/functions.php</strong> on line <strong>3249</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in <strong>/includes/functions.php</strong> on line <strong>3436</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in <strong>/includes/functions.php</strong> on line <strong>3436</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in <strong>/includes/functions.php</strong> on line <strong>3436</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in <strong>/includes/functions.php</strong> on line <strong>3436</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in <strong>/includes/functions.php</strong> on line <strong>3436</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in <strong>/includes/functions.php</strong> on line <strong>3436</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in <strong>/includes/functions.php</strong> on line <strong>3436</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in <strong>/includes/functions.php</strong> on line <strong>3436</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in <strong>/includes/functions.php</strong> on line <strong>3436</strong><br /><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" dir="ltr" lang="en">
<head>
	<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
	<meta name="keywords" content="Quake III Server Behind NAT, vbulletin,forum,bbs,discussion,jelsoft,bulletin board" />
	<meta name="description" content="[Archive] Quake III Server Behind NAT Quake Trilogy" />
	
	<title>Quake III Server Behind NAT [Archive]  - Main</title>
	<link rel="stylesheet" type="text/css" href="http://www.gameadmins.com/forums/archive/archive.css" />
</head>
<body>
<div class="pagebody">
<div id="navbar"><a href="../index.php/">Main</a> &gt; <a href="f-25.html">GameAdmins.com</a> &gt; <a href="f-4.html">Server Setup Forums</a> &gt; <a href="f-12.html">Quake Trilogy</a> &gt; Quake III Server Behind NAT</div>
<hr />
<div class="pda"><a href="?pda=1" rel="nofollow">PDA</a></div>
<p class="largefont">View Full Version : <a href="http://www.gameadmins.com/forums/showthread.php?t=1511">Quake III Server Behind NAT</a></p>
<hr />

<div class="post"><div class="posttop"><div class="username">cyberjunk</div><div class="date">09/03/00, 04:31 am</div></div><div class="posttext">For some reason I can't get my Q3A Server behind a NAT to show up on the Gamespy master.  When I run it ON the server connected directly to the Internet, it shows up no problem.<br />
<br />
I can get to Q3A on the server fine as long as I enter the address manually in GameSpy.  <br />
<br />
Is my Q3A server giving the gamespy Master the internal 192.168.1.120 address defined on the server?<br />
<br />
Any help would be appreciated!<br />
<br />
CyberJunk</div></div><hr />


<div class="post"><div class="posttop"><div class="username">Zxel</div><div class="date">09/03/00, 05:05 am</div></div><div class="posttext">Nope, it's actually NAT that does that, when gamespy goes to ping your external IP address NAT converts it to the local address then promptly blocks it - hehe.  http://63.167.10.249/admincentral/ubb/smile.gif<br />
<br />
Have a friend outside your LAN verify that you're on GameSpy (or post your game servers IP here and I'll check it for you  http://63.167.10.249/admincentral/ubb/smile.gif), nothing to be concerened about, this is how a firewall works.  http://63.167.10.249/admincentral/ubb/biggrin.gif<br />
<br />
Pe@ce to you - i'm out  http://63.167.10.249/admincentral/ubb/cool.gif<br />
<br />
------------------<br />
Jesus Is Lord, Zxel</div></div><hr />


<div class="post"><div class="posttop"><div class="username">celestius</div><div class="date">09/29/00, 11:17 am</div></div><div class="posttext">Btw.. if you want to run a server behind nat you have to configure the port for it so that when someone external tries to get to your server instead of blockin it it will just relay the data back and forth... you should find these settings somewhere in your nat properties called configure special ports (or something similar).</div></div><hr />


<div id="copyright">vBulletin&reg; v3.6.9, Copyright &copy;2000-2012, Jelsoft Enterprises Ltd.</div>
</div>
</body>
</html>