Lag Issues w/2 on Network

[ekoo]

Howdy, all.

I was hoping to get some help with an issue that my brother and I are having on his network with BF2. I'm visiting him at his home for a while, and we're trying to play BF2 together over his network. Both systems run it fine when we're in our respective homes and not together on the same network.

His net connection is solid, fast, and plays fine when one person (either one of our systems) is loaded into BF2. However, when the second person joins BF2 on the same network, both systems "lag" in the way of "you're pointing this way, no, now you're facing the other way" ... etc.. basically, choppy lag that unzooms your ironsight view, switches your weapons back after swapping, and generally makes vehicles undrivable. Overall, it is not playable.

I've searched all over for help, we've both tried disabling the Wireless Zero service, disabled VOIP, disable EAX, set out connection rate to "Cable/DSL", manually updated punkbuster, etc... Anything that I could find, I tried. Nothing has worked.

We're running DSL through a Netgear Rangemax 240 wireless router. However, we're both using wired connections and no one is on the wireless. It's locked down with WEP.

Any ideas on what might be causing this unplayable "lag" that is happening?

Thanks in advance.

[imported_Tren]

Re: Lag Issues w/2 on Network

Well first of all your using DSL.....not a good idea, especially for 2 people. Second, having it transmitting wireless doesn't help.

I suggest to turn off the wireless if possible, and for the future (if your going to be doing a lot of this "2 people playing" thing) upgrade to cable.

Good luck.

P.S. Next time please post things like this in the BF2 Support forum.

[Nightf1yer]

Re: Lag Issues w/2 on Network

Well first of all your using DSL.....not a good idea, especially for 2 people. Second, having it transmitting wireless doesn't help.

I suggest to turn off the wireless if possible, and for the future (if your going to be doing a lot of this "2 people playing" thing) upgrade to cable.

Good luck.

P.S. Next time please post things like this in the BF2 Support forum.

I have 2 PC's 1 Laptop and an xbox360 running perfect through my router with DSL
Ohh and the lappy is wireless... and BF2 plays fine.
So why suggest DSL is not good???

[Homie]

Re: Lag Issues w/2 on Network

Moved: http://www.totalbf2.com/forums/showthread.php?t=75729

[imported_Tren]

Re: Lag Issues w/2 on Network

Well I dunno...I didn't say it wasn't good, I just said that it may not be able to support 2 people running BF2. I only say that because my DSL wouldn't.

Sorry I couldn't help more...Maybe you should try some connection tweaking?

[ekoo]

Re: Lag Issues w/2 on Network

Thanks for the replies, and sorry for posting in the wrong forum.

I have quite a hard time believing it's the DSL. It's very fast, and I can play other online games or pull big downloads down while he's playing BF2 and he gets none of this choppiness. (first thing that I checked). It's only when we're both trying to play at the same time. I've also read many other threads about people experiencing the same thing with BF2, but with cable.

I'm only visiting here for a few days, so it's no big deal, we were just hoping to do a little playin' while I was in town. :hmm:

Thanks again.

[edit: no spell gud]
[edit: we're also both running wired to the router, but I'll try disabling the wireless, thanks]

[Talus]

Re: Lag Issues w/2 on Network

Well, you might want to consider Port Triggering on the following ports:

80,4711,1500-4999,1024-1124,29900-29901,27900,16567,28910,55123-55125

[ekoo]

Re: Lag Issues w/2 on Network

Thanks again, I was looking up which ports needed to be open, thanks for saving me the time :). I'll give that a try.

Thanks for the help, we've seemed to have solved the problem. :banana:

The firmware for the router was a bit outdated, so updated that and then opened up the recommended port triggering that you mentioned.

All is well now, except he's now getting a punkbuster error which is an entirely different monster, but I think we've got a fix for that going in now

Thanks again.