That did work but ....Come to find out by plugging in my modem directly to my pc rather then my Linksys router, that its the router. I just got a brand new one too .. I even set up a DMZ host. and I get nothing
in the list.....but when I do a direct connect to my pc from the modem I am at the top of the list....... What are all the ports I need to open beside the 27*** ports i heard there might be a 6000 and something port that quake uses. Anyone please help! :twisted:

:Bizump: I still cant seem to get it in the master server I am SSh ing to my xbox from a remote location not on my network and it still wont show up. Please help, I just want people to come to my server.

This is what i found, I have heard there is a way to use a NAT router and have your game listed in the server but this instructions is if you have a good router...I have a linksys and just wanna server.....I have pasted a post from Usenet this explaines why I cant connect but I need one of yalls help trying to figure out how to fix it. Thanks

----------------- Here is what I found-----------
Hey,
>
> for all those who followed that toppic (Quake 3 Server and Router) created
> about 2 weeks ago....
>
> i think i found something on the internet at that url:
> http://pub4.ezboard.com/furbanterrorfrm10.showMessage?topicID=372.topic
>
> [start quote]
> This will only help people who already have forwared thier port 27960 on
> thier masq servers to thier quake servers.
>
> The problem that NAT/MASQ has with Q3 _servers_ behind them is this:
>
> What happens with a Q3 server behind a NAT:
> -Q3 server sends heartbeat to master from port 27960
> -The NAT, intercepts the heartbeat, and masqs it, and pipes it out port
> 61000+
> -The master server sees this heartbeat from 61000 and replies to 61000,
> requesting more info...
> -The NAT doesn't know what to do with this packet, and drops it.
> -Therefore, no reply == no list in Q3 master, and a bad port in the Gamespy
> list.
>
> The server behind the NAT would send a heartbeat to the Q3 master server,
> from its own port 27960. The NAT would pick up that transmit, and make it
> come from 61002(or whatever) on the NAT itself. This is not usuauly an
> issue -- except that in this case, the master server looks at the SENDERS
> PORT to determine the Q3 server's port. This, in the case of masq, a port in
> the 61000+ range, where the server does not reside. Thus, the connection is
> dropped by the maq server.
>
> The work around is simple .. send a heartbeat from the NAT/masq machine
> itself on behalf of the Q3 server, on the right port.
>
> Here is a VERY simple perl script, I've been runing for a few days now.
>
> It sends a heartbeat to the Q3 master server from port 27960, closes down.
> Repeats in 5 minutes.
>
> What happens with the script is this:
> -The NAT ITSELF sends heartbeat to Q3 master from port 27960 to 27950
> -Q3 master responds to port 27960, which is forwared off to the Q3 server
> behind the nat
> -Q3 server behind the NAT replies with config info, and bingo , the server
> in on the Browser lists.
>
> --BEGIN CODE--
>
> #!/usr/bin/perl
> use IO::Socket;
> $port=27960; //server's port
>
> while (1) {
> $sock=new IO::Socket::INET (PeerAddr=>'master3.idsoftware.com',
> PeerPort=>27950, Proto=>'udp', LocalPort=>$port) or die ("Reason: $!\n");
> print $sock "\xFF\xFF\xFF\xFFheartbeat QuakeArena-1\x0A";
> close ($sock);
> sleep(300);
> }
>
> [end quote]
>
> unfortunately my router does not have pearl with it (its a one-floppy-disk
> router) and i
> assume there is not enough diskspace for pearl.
> who has enough C skills to write a program that performs the same funktion?
> maybe with an imput file so the server (or more servers) can be specified?
>
> regards
>
> stefan
>

ok I am off work what do you want me to do.