The master server problems seen on this list from people using NAT-based
routers stem from an incorrect outbound NAT configuration.
In basic terms, most NAT routers will modify the source port of an outgoing
connection. For example, your server's source port of 27015 will be
reported as
It cant bind to an ip that it doesnt use, when you forward the ports
directly to the server any connections being attempted on those ports
are translated to your servers local ip so just set it to your local
ip.
Oh, I understand that of course. Problem is, the server doesn't show up in the
--
[ Picked text/plain from multipart/alternative ]
That doesnt necessarily indicate a problem at your end, the master servers
can take a few days to pick up servers sometimes, if ppl can connect to the
server ok by using connect ip:port then there is no problem your end and
the master servers
That doesnt necessarily indicate a problem at your end, the master
servers can take a few days to pick up servers sometimes, if ppl
can connect to the server ok by using connect ip:port then
there is no problem your end and the master servers will add you
eventually depending on the servers
--
[ Picked text/plain from multipart/alternative ]
No, the respawn delay is not configurableyet!
On 9/25/07, Noctaire [EMAIL PROTECTED] wrote:
That doesnt necessarily indicate a problem at your end, the master
servers can take a few days to pick up servers sometimes, if ppl
can
Noctaire:
I can see and was able to connect to your server by direct query but
could not see it by general query in the server browser or in 3rd party
lists (game monitor for example).
http://qsextreme.com/tf/domicile.png
Since the hostport shown in the direct query was 27015 you apparently
I can see and was able to connect to your server by direct query but
could not see it by general query in the server browser or in 3rd party
lists (game monitor for example).
Same thing I'm seeing here. I see that someone else connected by the logfiles,
so I'm guessing that was you. :)
You must use -ip external ip address in the server launch options
for your server to become visible to the general public (not +ip).
http://developer.valvesoftware.com/wiki/Command_line
Kevin -- I just looked through the WIKI you linked to and the -IP/+IP
parameters both do the same; i.e.,
Noctaire
I can relate to your problem although I don't have a solution as of yet.
I have 10 servers on 2 boxes that are on a NAT firewall and people can play
on them fine but they do not show up on the Steam Master Server List (SMSL).
So they essentially sit there empty.
The firewall must doing
--
[ Picked text/plain from multipart/alternative ]
Maybe valve is just using the value you send in +ip as the address for
servers rather than the endpoint address. I assume they would then filter
out private subnets. That would cause this problem. I doubt they are doing
that though.
Nolan
On
FWIW, I'm running a Sonicwall TZ170 on this particular connection.
All in all, it's more than a tad irritating. I've run HLDS behind a
firewall in the past and never experienced this issue and I can't believe
Valve would be so shortsighted as to design the server/trackers such that
they do not
--
[ Picked text/plain from multipart/alternative ]
Heres my server.cfg, hope it helps.
Patrick Shelley
// this is your server name as shown in the server list
hostname BLA BLA BLA BLA
sv_password
// your server password. a pair of double quotes means it is not set and
anyone can join
//
Everytime I've started up a server, the master servers have always had it in
less then 60 seconds. I should qualify that statement by saying that I
currently only run OP4 and HL1MP:S servers. Can't comment on CS, DOD, etc.
- Original Message -
From: Col Grigson [EMAIL PROTECTED]
To:
The only times I've had problems showing up on the master servers, it could
always be attributed to a missing SNAT rule. Bottom line, requests came in
on one of the extra IPs assigned to my firewall, but they went out the
default IP. A SNAT rule would rewrite things so that it properly showed
snip
Important note:
You won't be able to see your own server in the server browser if you have
both the server and your client behind the same router, use a 3rd party
browser like gamemonitor to check and make sure you got all the launch
options set right.
When I was with Quest using a
It cant bind to an ip that it doesnt use, when you forward the ports
directly to the server any connections being attempted on those ports
are translated to your servers local ip so just set it to your local ip.
Noctaire wrote:
Anyone running behind a firewall?
Got the server up and running --
16 matches
Mail list logo
