High latency within my network!

[Tek]

Try pulling the plug to the internet and connect to a lan only game. IF this works fine, then you're computer and the server are both sending packets thru the net and when the router recieves them back, the port forwarding takes over and the router is taking your packets that are supposed to come to the client and sending them to the server. I had this problem with hosting Serious Sam 2 over my network in it's early stages. Also if you get errors running ping 127.0.0.1 on the server or your gaming rig, that means that your tcp/ip stack is probably screwed up. You should get 0ms min, max, and avg response time w/ 0% packet loss. If it's anything other then that, there's a serious problem w/ ur tcp/ip on that machine.

[13CentKiller]

Thanks Tek, I think I got 8ms once when I did that 127.0.0.1 ping. I have a fix that will reset my TCP/IP stack. I will try running that.

I have internet optimizers that I think interupt the flow of data, but wasn't 100% sure until now. We will see.

Cheers. And Megadrive, your help was amazing too. That DNS fix looked promising, but my ISP said thats not what I'm looking for, so I went no further. On the other hand, they havn't been able to fix the problem myself.
So there you go...:sleep:

Cheers again! Both of ya':cool:

---

"Three o'clock is always too late or too early for anything you want to do."

[13CentKiller]

After weeks of badgering, walls of text, emails in the hundreds, PM's, game troubleshooting, countless numbers of forums I am now registered with and will never post again on, just to read that one thread that might be of interest. I have finally figured out the problem.

Ultimately, it was the CPU, I'm sure someone mentioned that as well. Dual Core, no more!

The information was getting lost between the 2 cores somehow. And setting Battlefield 1942's affinity to CPU 0 fixed the problem. No more high pings, no more disconnects, no more freezing, connection problems and the like.

Thanks for all your help, your support was much apreciated. Thanks for the effort.

I hate to say it, but....

Naaa, I won't
*cough* Intel next time? *cough*:angry:

Cheers guys:cool:

---

"Three o'clock is always too late or too early for anything you want to do."

[mangadrive]

That figures haha. Thats pretty much why I quit networking and went back to music/art. I'd rather starve and have fun than diagnoss sh!* that has too many varibles and at some points impossible to diagnose all at once....

but glad you worked it out and sorry I was limited help.. but hey I'm a sucker for trying.

---

[13CentKiller]

If it won't for your posts, I would have never tried setting the processes to separate cores.

So thanks for that:)

Cheers:cool:

---

"Three o'clock is always too late or too early for anything you want to do."