Ping Bouncing And Port Forwarding
#1
Posted 21 December 2015 - 05:13 PM
Why the HELL is my ping bouncing up and down on some routers and not others?
My home router is the WORST one for doing this, sometimes kicking my ping up to 3k or higher, and then dropping down to like, 28. It's causing me to lag hard.
So to fix this, I'm going to port forward to see if that helps.
This brings me to my second problem:
What ports do I need to use for this? I've seen a few threads on them but everyone seems in disagreement about the UDP. I've snagged a thread that listed the following that came from the PGI staff:
TCP 45461
TCP 45464
UDP 21000 to 30000
The other variants were well within the UDP's ranges but I would like to be clear. I know this will help my gaming experience anyways on my laptop but I'd like to make sure that this will also help with my ping.
Nobody is on my network when I've experienced the ping issues. No streaming, downloading, or anything as my dad is an IT director and set all the computers to only check for and download updates when told. That includes all tablets and phones and computers. I handled the gaming consoles as well as the DirectTV receivers.
Please help me!! I barely get a single match in before my ping becomes an issue. I have a cooling fan that keeps the core temp of my laptop down. That was the original issue. My FPS never gets lower than 19 unless the ping starts bouncing. I played a solid (don't judge me) 8 hours for the last CW event for Battle for Tukayidd on a router that didn't bounce my ping and my ping stayed pretty static (between 31-48).
Help!!!!!!
#2
Posted 21 December 2015 - 06:32 PM
#3
Posted 21 December 2015 - 08:56 PM
Also, remember that some of the servers you are connecting to are in the EU and some in NA. I know I usually get <35ms ping to the NA servers, and around 130ms for the EU, which is about right since I am in the midwest.
Last night I noticed my ping to EU servers jumped to about 400ms, so I cycled power on my router and refreshed my dns cache and things settled back down.
#4
Posted 27 December 2015 - 07:39 PM
I don't know enough about how to fix ping and a recommendation for it by most of my gaming friends was port forwarding.
I don't have the EU or Oceanic Servers selected as choices because of the ping issues (as much as I liked playing with some of the guys on those) making it impossible to play due to constant 'Rubber Banding'.
I first thought it was due to someone streaming and (neighbor kid lied to my folks and was grounded from internet at his house so he jumped on ours. Told his folks, got the mac address of his computer and blocked the mac address. Very happy parents lol) it was due to that but I dealt with that.
I have tried running a wire and I do know that fixes the solution instantly but I'd really rather not sit in the basement every time I want to play MWO. It's cold down there lol Plus I want to solve the issue, just in case it's affecting the rest of my family. They wouldn't notice the ping bouncing other than the internet slowing down. My dad is a Technology Director but he doesn't game and the PC he uses to work from is hardwired in so he has no issues with that. My sister however does homework on her laptop.
The ping bouncing is constant, regardless of the time of day. I'm in Indiana so for me, the NA servers shouldn't be skyrocketing up to around 3k ping. I could understand the EU or Oceanic but whenever I check the quick play button, it's between the 38-47 ish areas.
I believe me, I don't blame people for giving me advice on something I messed with. If port forwarding is bad, I'm all ears on better solutions that are safer. Especially if I can use the solution for a blanket effect on any connected devices. I'm going to go refresh the DNS cache now though and the router power cycle.
Is that a temp solution or just a monthly maintenance thing? I know quite enough to be dangerous with this sort of thing but I'd be lying if I said I understood what I was doing. I just know the port forwarding worked but from your responses, I'm all for a better solution.
Edit: Rang a ping test too from the command prompt. Used the 70.42.29.75 IP and got 75% packet loss twice but one packet reached the host, got a reply from an IP of 70.42.24.132 but destination host was unreachable. Same thing for for the second test which had an IP of 70.42.24.196. However, when I pinged those two IP addresses, I had 0% loss and got statistics from them.
Going to do the DNS clearing and power cycle now.
Edited by Liam Salem, 27 December 2015 - 07:51 PM.
#5
Posted 28 December 2015 - 06:40 AM
Heavy packet loss is a surefire sign something needs to change. If your pingtest.net results are bad (and you may want to test once every 10 minutes for an hour to have a large amount of test results), I'd start by looking at your wireless adapter and the wireless router. Either you're really far away from it and the signal isn't strong enough, there is too much interference on the channel you're on, or the radio on either the adapter or router is starting to fail.
Namebench will help you pick the best DNS servers to ensure you will not be using something borked.
#6
Posted 28 December 2015 - 02:07 PM
Liam Salem, on 27 December 2015 - 07:39 PM, said:
Im gonna pick this bit out, why would you sit the in the basement? Is that where the router is located?
Sounds like you could be too far away if that's the case, and the problem would only be worse if your using a cheapo router.
#7
Posted 28 December 2015 - 07:41 PM
Having the router itself in the basement is a very bad idea. Think of your router's wireless coverage as a sphere. If the sphere is on the bottom, half the signal is in the ground. Always best to have the router in the midpoint of your coverage area (ie. ground floor).
If you have a newer cell, download Ookla speed test from the play store or itunes and run the tests where your PC is. Try to find a spot where you reliably get a decent download/upload speed. I was able to move the relative's desk 10 feet to the other side of the basement and all the packet loss went away (less overheard metal).
Best solution is get the router out of the basement if you are dead set on wireless. Your dad has no issues because like you say he is wired, but no wonder everyone else has packet loss.
Oh, and change your wireless securty to WPA2 or something to keep that neighbor from jacking your bandwidth in the future. Blocking his MAC only temporarily stops him.
Good luck.
#8
Posted 28 December 2015 - 07:54 PM
DV McKenna, on 28 December 2015 - 02:07 PM, said:
Im gonna pick this bit out, why would you sit the in the basement? Is that where the router is located?
Sounds like you could be too far away if that's the case, and the problem would only be worse if your using a cheapo router.
I thought I was using a cheap router. Trust me on this, that was the first thing I checked. It's not a high end one by any means but it's not towards the lower end. When I checked out it's rating, it's neither bad nor good.
I do think the distance thing might be an issue but even while sitting literally, 10 feet from it, I still have the ping bouncing being an issue. Plus at my school, I was able to play (and sad as this is to admit) 8 hours straight on their connection for the second battle of Tukayidd without any issues and had a solid 3 bars almost the whole time.
I've run through a few things, including a tracert in the command prompt to MWO's above listed servers (both the 75 and 74 ones) and they both failed at the EXACT same spot, which is the 70.42.24.132 IP for the 70.42.29.75 server IP and 70.42.24.196 IP for the 70.42.29.74 server IP. However, whenever I ping 70.42.24.132 & .196, I was able to successfully tracert them.
Rang the pingtest.net thing and I KNOW for a fact I have Java installed and I think I may have located the source of my problem. My computer isn't registering my connection in the Network and Sharing center as a private one and has dumped me onto public. Firewall issues. However...this brings up a whole new issue. I can't access my wireless connection to administer a type to it to get it over to private connection.
When viewing the Network and Sharing Center, right under where it says "View your basic network information and set up connections" it says 'Unknown', then below that, says 'The dependency service or group failed to start'.
I've hunted across the internet for a list of the services that need to be activated for that to work because I did mess with services a while ago to kill bloatware that was on my computer (googled every single last one of them and checked several sites before killing the services) I have been unable to find a proper list because every Microsoft-moron/employee seems to think that resetting your router will fix this. It never has and I've even factory reset the ***** at least four times because my sister thinks she knows how to work it, the most recent time being two months ago. I've had the ping bouncing issue for a while now, prior to that reset.
Long story short is, I think there's a service i set to disabled, that needs to run, so that the firewall will recognize my Wi-Fi connections and allow me to work this.
I'll still run all the other tests, just because I don't like how the tracert fails at the same point each time, at IP's listed by the community, but when tested at those points, I have zero issues, both with when I ping and tracert them.
@Golrar: if that were an option, moving the router, believe me that it would have been moved. I'm half tempted to run a signal booster to the upstairs. I honestly am being lazy with my laptop. However, I do get the sphere reference and I'm going to see what I can do to move it closer.
Going to check all my drivers too and services to to double check if I missed something or if somethings out of date already.
#9
Posted 28 December 2015 - 08:52 PM
Found out one of my PCI Bus slots doesn't even have a driver installed while going through everything. Did some netsh refreshing as well. Downloading drivers currently so I'll redo those as well. So far, it seems, since I started digging into this, I've just been finding more and more issues...
#10
Posted 29 December 2015 - 07:35 AM
Liam Salem, on 28 December 2015 - 08:52 PM, said:
Found out one of my PCI Bus slots doesn't even have a driver installed while going through everything. Did some netsh refreshing as well. Downloading drivers currently so I'll redo those as well. So far, it seems, since I started digging into this, I've just been finding more and more issues...
Here's another thing you should Google that I forgot to mention: InSSIDer. Basically, it'll tell you how strong your signal actually is and how crowded the channel(s) you are using is. There is a slightly older version out there that is free to use, but I think the newer version went to a cheap pay model (maybe not, but I seem to recall something about it...).
If you think Windows might be part of the problem, you may want to completely uninstall anything to do with wireless networking that isn't built directly into the OS and then grab a fresh copy from your laptop's manufacturer to reinstall it. Having had a Dell Vostro and HP Envy before my current Gigabyte notebook, I feel comfortable saying that this is a better option that simply attempting to find bits and pieces to add/subtract/switch on/switch off. Maybe you don't like it and consider it bloat, but most manufacturers are not very 'advanced user' friendly (which goes double for regular users who think they are advanced users).
Further, unless you completely reformatted and installed a clean copy of the OS, you may want to consider that some of these components that manufacturers add are custom-written and don't uninstall nicely or will conflict with a base copy of drivers they're made from. I can recount many a tale where even simple things like screen brightness bring about conflict. Then, in that sense, you definitely want the manufacturer version of the driver OR you want to install the OS from scratch.
#11
Posted 29 December 2015 - 09:16 PM
I'll fix my firewall to allow MWO and then go about the other fixes if that doesn't solve it.
#12
Posted 30 December 2015 - 05:40 AM
Traceroute giving you stars * * * just means its filtered. There are lots of devices out there that are configured not to respond to or to filter out things like that (ping included).
Honestly, you're going in two separate directions. The first direction, with the pings and traceroutes, is "can I even get to this IP?" The answer is already a resounding 'yes'. The second direction is "I have severe packet loss or other connectivity issues" which is what you should be focusing on here. You can play online, your connection just goes into the dumps. All of my previous suggestions to check the devices related to the connection stand now that we know the trouble happens between the first two nodes (laptop and router).
#13
Posted 05 January 2016 - 11:57 PM
Oh, and yeah, make sure there is nothing on or blocking the vents/heatsink/fan on your router. Just sayin.
Edited by Golrar, 05 January 2016 - 11:58 PM.
#14
Posted 06 January 2016 - 10:44 PM
As for the driver updates, I'm going to go through services to find out if that is why I was having issues. I uhh...may have forgotten to update Windows in a few months which may be causing my hardware drivers to lag behind.
I'm going to do a test run of the game tomorrow where I can run several games, one after the other, and test out my connectivity. Ran tracert and ping again from command prompt. tracert has the same issues BUT when I ping the IP's now, it's not consistently 75% loss anymore. It did go to 50% loss at one point but then it went up to 100% loss at one point.
I'm thinking possibly, the router needs to go for an upgrade. However, I'd rather not drop the money on the router unless I know it's the issue. Considering I have to still do the reinstall, I'll wait until after I playtest to see if fixing those services has solved my issue. Because I'm still getting major packet loss, I doubt it will but here's hoping.
Still going to run the rest of your suggestions though. Hopefully one of those will work. If nothing solves the issue or the like, then the router must be changed. Everyone's help is much appreciated. Hopefully this gets solved tomorrow. I'd really like to play again...
#15
Posted 08 January 2016 - 10:29 PM
Routers are not that bad on price any more. I would recommend a Netgear or Buffalo for ease of use and reliability if you do get a new one.
5 user(s) are reading this topic
0 members, 5 guests, 0 anonymous users