I still have an issue behind NAT and sv_steamgroup_exclusive "0". No members from my steam community can join the server.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of William Stillwell Sent: Monday, November 24, 2008 9:11 PM To: 'Half-Life dedicated Win32 server mailing list' Subject: Re: [hlds] L4D Dedicated server behind NAT problems? This bug only appears when you run the following in server.cfg sv_steamgroup "xxxxxx" sv_steamgroup_exclusive "1" otherwise, l4d behind nat works fine. Again, l4d using above, doesn't allow remote clients to connect via public nat'd ip. Setting exclusive to "1" works fine if your server has a public ip assigned to it. Setting exclusive to "0" works but your server is not at all restricted to the steamgroup, any user can connect and whim. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Richard Eid Sent: Monday, November 24, 2008 11:34 PM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] L4D Dedicated server behind NAT problems? I have a Netgear router in between that computer and the cable modem. I've set up port forwarding for that computer's IP for ports 27000-27050 TCP/UDP. Here's my startup command: *srcds.exe -console -game left4dead +ip myinternalip -port 27015 +map l4d_hospital01_apartment.bsp +sv_lan 0 +sv_pure 2* I've also used that same command line without +ip and -port. SRCDS is good about detecting the IP and it works just as well without those two variables in the command line. It defaults to port 27015 without a -port defined, but that's what I want it on, so I'm good with that. I'm not really doing anything special with my server.cfg. I've used sv_allow_lobby_connections_only 0 and 1 and I get just as much traffic either way. This command was removed and re-added(I think), but the functionality of it remains unclear. Are you hosting the server on the same machine that you're playing Left 4 Dead on? -Richard Eid On Mon, Nov 24, 2008 at 11:00 PM, William Stillwell <[EMAIL PROTECTED]>wrote: > > > To William - you can solve the connecting problem by using +ip > > xxxx.xxxx.xxxx.xxxx and +hostport xxxxx in the startup line. This is > > what I have to do to allow friends to connect, but this doesn't solve > > the problem of it not being detected by matchmaking. > > Already have that, :-) > > I want the matchmaking to work as well... I and just about everyone else > will have to wait :-) > > > _______________________________________________ > 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 _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
