Garrr The Pain!

[BobTheJanitor]

go on broadbandreports.com under tools, run tweak test and line packet loss test, report back with results :p

[snapback]26731[/snapback]

Noooo don't do that. They'll want money to run their tests. If you want to check for packet loss, just go to a command line and type 'ping yahoo.com -t' and let that run for 5 mins or so. Then hit ctrl+c and get the results, it'll tell you what % packet loss you're getting. (anything more than 1 - 2 % is bad... I'm getting anywhere from 4 - 9 % lately, and my game is crapped up like crazy)

[Niteowl]

about your packet loss bob, i was wondering if maybe you got a trojan or spyware sucking up bandwidth? i know i had ping problems, and hat had happened was i got some silly piece of MS code.. from some update.. and it was constantly trying to talk to MS to get an update, a line of communication that i denied, and would result in NASTY lag spikes.

[BobTheJanitor]

Actually, it's probably not me at all. Happens on all the computers in this area. Cox recently updated their line speeds, and they're updating software on their end. Everyone in the general area is having the same packet loss problems. Most of them probably don't notice, though, as packet loss while browsing just means a page takes another second to load. Instead for me it means horrible bloody death.  

[Niteowl]

just thought i'd not that bob's bloody death is my normal playing "skill". *runs for the cc*

[BobTheJanitor]

Yeah I've even tried running for the CC a time or two, where lag doesn't hurt as badly. I end up with my usual CC curse -- marines that can't hit the broadside of an onos and won't go to a single waypoint. Hooray!

[devicenull]

go on broadbandreports.com under tools, run tweak test and line packet loss test, report back with results :p

[snapback]26731[/snapback]

Noooo don't do that. They'll want money to run their tests. If you want to check for packet loss, just go to a command line and type 'ping yahoo.com -t' and let that run for 5 mins or so. Then hit ctrl+c and get the results, it'll tell you what % packet loss you're getting. (anything more than 1 - 2 % is bad... I'm getting anywhere from 4 - 9 % lately, and my game is crapped up like crazy)

[snapback]26767[/snapback]

They don't want money.. I've run their tests a lot without paying

[Kodiac]

http://www.steampowered.com/forums/showthr...threadid=116155

Its a router problem.  I had the exact same thing.

Basically what you do is put +clientport (porthere) and forward that port to the computer via the router.

ie, my brother and I both play on steam, so we had to use different ports: For him, I created a shortcut for the game, and put +clientport 27007 in the command line (any port will do, I just put a port that is most likely not used).  For me, I put +clientport 27008.  Then I forwarded these ports to the appropriate computers and bam:  No more random parse error disconnects.

[snapback]26734[/snapback]

Ummm....Lito, How exactly do i do that? I dont know squat about routers.

[Asal]

Okay, tbh, I don't know what you mean by:

...forward that port to the computer via the router.

Sorry dude.  A little explaining, and I'll clear it all up for us all.

[Lito]

open up your browser and type in 192.168.1.1




a password prompt will come up.  Leave username blank, type in 'admin' (without the '') as the password.

After the screen loads, go to advanced



goto forwarding



Open up steam, goto play games, right click on whatever game you'll be playing, click on "Create Desktop Shortcut".

At the end of the target line add "+clientport [porthere]" replace [porthere] with the port. in the example i used 27006.



click okay.  goto start>run  type in cmd

in the prompt, type in "ipconfig" and take note of the ip address.  This isn't your real ip address, its the ip address assigned to you by the router.  take note of it.



go back to the port forwarding, and forward the port to that ip address.
the port I used was 27006 and my DHCP ip address assigned to me by the router was 192.168.1.100 so it would look something like this:



for your brothers computers use different +clientport [porthere], then forward that port to thier computers.  For example, my brother has the ip 192.168.1.101, and for him i set +clientport 27007.  So i would forward port 27007 to 192.168.1.101 via the port forwarding section of the router.

[Asal]

Kodiac and I are now ready to play.

[johnjacobjingle]

me 3 me 3!  back up and sucking!  man, i tried to play after what was it, 2 weeks off?  something like that?  MAN did i suck.  /cry

[Malevolent]

Yay, ze bros are connected!

[Niteowl]

open up your browser and type in 192.168.1.1
...
for your brothers computers use different +clientport [porthere], then forward that port to thier computers.  For example, my brother has the ip 192.168.1.101, and for him i set +clientport 27007.  So i would forward port 27007 to 192.168.1.101 via the port forwarding section of the router.

[snapback]27056[/snapback]

HOLY CRAP that was a most EXCELLENT and helpful post! title change babay!

[Lito]

Yeah, when you've had internet problems for months on end, you learn your way around the router.

[fatty]

HOLY CRAP that was a most EXCELLENT and helpful post! title change babay!

however you are still lie-to in my book!

[Asal]

Thanks Lito, and everyone else who tried to help. Everyone is up and running, so feel free to throw a few shouts of 'noob' and other such insults my way for letting it last that long.

[SwiftSpear]

Lito wins swiftspear's most helpful post of the period of time between now and the next time someone makes a really helpful post award!  

That post totally makes up for you ruining my node biting skill by telling everone else how to do it