I have my aDSL modem bridged and the box running the server is DMZ'ed so I
can't see how NAT would be a problem. I can host TF2 and any other source
dedicated servers no problem. It might very well be my hosting environment
is the reason but then why would matchmaking still be able to access my
server with no problem with sv_steamgroup in my .cfg but connecting through
Steam Groups or sv_search_key completely blocks any other incoming joins
past the first player. Something changes server side once that first player
joins, I would love to know what and why.

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of William Stillwell
Sent: Friday, November 21, 2008 12:07 AM
To: 'Half-Life dedicated Win32 server mailing list'
Subject: Re: [hlds] Steam Group Server woes

First off, are you running a Nat'd Server?

If you are it won't work..

There is a bug when running any l4d server with the steam Group features on
a nat'd network..

No fix released yet..

I tore down the 8 servers I was running on public users until valve fixes
The nat issue for private steam group users.




-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dustin Peacock
Sent: Thursday, November 20, 2008 11:51 PM
To: 'Half-Life dedicated Win32 server mailing list'
Subject: Re: [hlds] Steam Group Server woes

First of all I'm getting tired of weeding through 50 or so email's a day of
just pure conversation. This is a not a social forum, if you want to chat
then take it to personal emails or some other form of communication.

It's also needed to be spamming the mailing list whenever you encounter a
hacker on your server and want him banned. This is the HLDS mailing not a
VAC mailing list. On top of that it's unfair to encourage a multitude of
admins to black list someone on a single incident that occurred on your
server. Admins should make a decision on bans for player actions on their
servers alone; eventually VAC will catch habitual cheaters.

So please, can we keep the mailing list to helping Valve fix the horde of
issues with L4D dedicated servers right now.

My real problem which has my clients pissed off and is starting to rub me
the wrong way now is the fact that once a single person from our community
group joins the server it seems to lock it from any other players from
joining.

I've tried using and not using sv_search_key, sv_steamgroup_exlusive,
sv_lobby_connect_only. None of it works; once someone from the group joins
the server that's it.

Obviously no one from matchmaking is having a problem because I've already
served more than 400 players from matchmaking today alone. I myself have
been able to join the server from the main menu when there have been 3
players from matchmaking in it. I might just have to remove sv_steamgroup
from my server.cfg but I doubt my clients would even bother to directly
connect or use sv_search_key when they can just join a random dedicated
server.

The whole issue has me baffled and frustrated, my clients can essentially
join anyone else's server (through matchmaking) but mine.





_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
http://list.valvesoftware.com/mailman/listinfo/hlds


_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
http://list.valvesoftware.com/mailman/listinfo/hlds


_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds

Reply via email to