or clientport xxx in the console and then net_start if you already connected to a server when you do it.
2009/5/4 Steve Colebourne <steve.colebou...@gmail.com> > +clientport 27006 in launch options :) > > turb0z wrote: > > How would one go about doing this? > > > > -----Original Message----- > > From: hlds-boun...@list.valvesoftware.com > > [mailto:hlds-boun...@list.valvesoftware.com] On Behalf Of MONDO > > Sent: Monday, May 04, 2009 10:41 AM > > To: Half-Life dedicated Win32 server mailing list > > Subject: Re: [hlds] TF2 - Concurrent Connections from one public IP > blocked > > > > Using a different port on the player side should resolve this. The > default > > port is 27005, so simply have the 2nd PC use port 27006 and you should > have > > no further problems. > > > > On Mon, May 4, 2009 at 11:31 AM, turb0z <tur...@undergamer.com> wrote: > > > >> I also just confirmed with this person that if they click "cancel" on > the > >> "retrying" connection box before the timeout occurs, they were able to > >> successfully join the server. Seems pretty bass ackwards, but that was > > his > >> workaround yesterday. He confirmed this on four systems (two on one > > public > >> IP) working off of Time Warner Residential and Business class. > >> > >> Seems like it's definitely an issue since he confirmed it on different > >> systems and it wasn't linked to one game server. > >> > >> -----Original Message----- > >> From: hlds-boun...@list.valvesoftware.com [mailto: > >> hlds-boun...@list.valvesoftware.com] On Behalf Of Steve Colebourne > >> Sent: Monday, May 04, 2009 10:27 AM > >> To: Half-Life dedicated Win32 server mailing list > >> Subject: Re: [hlds] TF2 - Concurrent Connections from one public IP > > blocked > >> Not checked since the update, but used to get this a lot a while back. > >> > >> We now run each client behind the same ip on a different client port and > >> get no problems - but as I said, haven't been on tf2 with two machines > >> since said update. > >> > >> Don't know if the above will help or not! > >> > >> turb0z wrote: > >>> Since the last Valve update for TF2, I’ve been getting reports from my > >>> community members that if two people try to join a TF2 server from the > >> same > >>> public IP address, the second person gets a “connection failed after 3 > >>> attempts” message. This has been confirmed on any TF2 server, not a > >>> specific one. This was not the case up until the last update released > > (I > >>> believe Friday). > >>> > >>> > >>> > >>> Anyone else seeing this issue? > >>> > >>> > >>> > >>> -turb0z > >>> > >>> _______________________________________________ > >>> 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 > > > > > > _______________________________________________ > > 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
