The only time I've had to use clientport was when I was running something on the same box that was causing a conflict. Two seperate computers using the same outgoing port won't cause a problem because they have different ip addresses. I've done this for years - the server doesn't care - I've connected to my server with five computers at the same time, all using the same outgoing port. Never had a problem with it. The server recognizes that they have different IPs, and doesn't care if the port is the same. Neither does the router. IPs or ports don't have to be unique, but ip/port combinations absolutely must be unique, and they will be unless two computers have the same IP, or your router is doing something stupid.
I wonder if TF2 has some issues with clients using the same port, even with the ip is different? Or vice versa, problems with clients using the same IP but different ports? I would not say this is not a TF2 or L4D/L4D2 bug with srcds. Toss a coin - heads, it's a router problem, tails it's a srcds problem :-) ----- Original Message ----- From: "Richard Eid" <[email protected]> To: "Half-Life dedicated Linux server mailing list" <[email protected]> Sent: Saturday, December 19, 2009 1:40 PM Subject: Re: [hlds_linux] TF2 Multiple clients from the same IP > It sounds like they just need to set an alternate clientport. On one > machine, no changes will need to be made. The second one will need to > have > a launch option added: > > +clientport xxxxx > > I think the default clientport is 27005, which the client that is not > setting a clientport using launch options will be using. The one that > needs > to add this to their launch options can use whatever, but 27006 is a safe > alternative. > > Both clients behind one router connecting to two different servers at the > same time shouldn't experience this issue, but if you have two clients > behind the same router and you're both trying to connect to the same > server, > one of them needs to use an alternate clientport. > > Then again, maybe I'm misunderstanding the problem and this won't solve a > thing. Good Luck! > > -Richard Eid > > > On Sat, Dec 19, 2009 at 4:28 PM, John <[email protected]> wrote: > >> I can vouch for the same problem on my own Left 4 Dead and Left 4 Dead 2 >> servers. My roommate and I can both connect to some dedicated servers, >> however my own and a few others, one of us gets in and the other >> eventually times out and is never able to connect. >> >> Richard Eid wrote: >> > Is your server denying them the connection or is it just a local >> > timeout >> on >> > their end? Have they set +clientport on one of the clients so they >> > both >> > aren't trying to connect through the same port? >> > >> > -Richard Eid >> > >> > >> > On Sat, Dec 19, 2009 at 2:44 PM, Tony Paloma <[email protected] >> >wrote: >> > >> > _______________________________________________ >> > To unsubscribe, edit your list preferences, or view the list archives, >> please visit: >> > http://list.valvesoftware.com/mailman/listinfo/hlds_linux >> > >> >> >> _______________________________________________ >> To unsubscribe, edit your list preferences, or view the list archives, >> please visit: >> http://list.valvesoftware.com/mailman/listinfo/hlds_linux >> > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > http://list.valvesoftware.com/mailman/listinfo/hlds_linux _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
