Welcome to The Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads

Bad In-Game Ping


youthedog
 Share

Recommended Posts

So, I've got this problem with CS:S where I get high ping in-game (100-180) where my normal ping is (30-80).

I recently reinstalled windows which seemed to fix the problem temporarily but it's back again.

1. Not my router.

2. Not my modem.

3. Not my ISP.

4. Winslows is being annoying as fuck.

 

Can anyone help :\?

Link to comment
Share on other sites

If you recently reinstalled Windows, you may have a ton of extraneous useless services running in the background that are slowing down your game. Disable the ones you don't need up (obviously look up what they are individually before making a decision) and see if that makes a difference.

Link to comment
Share on other sites

updating your NIC drivers?

 

did you try any of the cfg files that tweak with your network settings?

cl_cmdrate 66

cl_updaterate 66

rate 25000

 

If you're running Windows 7 or Vista, try optimising the TCP/IP network stack. A lot of stock settings aren't the greatest out of the box.

Link to comment
Share on other sites

updating your NIC drivers?

 

did you try any of the cfg files that tweak with your network settings?

cl_cmdrate 66

cl_updaterate 66

rate 25000

 

If you're running Windows 7 or Vista, try optimising the TCP/IP network stack. A lot of stock settings aren't the greatest out of the box.

Already optimized it, all css net settings are the perfect, and shouldn't cause any problems.

If you recently reinstalled Windows, you may have a ton of extraneous useless services running in the background that are slowing down your game. Disable the ones you don't need up (obviously look up what they are individually before making a decision) and see if that makes a difference.

Done this too, one of the first things. The thing is, when I started playing after I reinstalled, it was fine. Now it randomly starts lagging again. I've talked to my ISP and they've reset my modem, done latency tests from their server directly to the modem and it's fine.

 

Link to comment
Share on other sites

So these settings were changed?

Enabled ECN?

High restrictive autotuning for TCP Window Size?

Enabled RSS?

Enabled TCP Chimney for offload processing?

Disabled Heuristics for autotuning?

Changed the congestion provider to CTCP?

Disabled RFC 1323 timestamps?

Enabled DCA (Direct Cache Access) for your NIC?

 

These settings can impact your connectivity. I would suggest checking these settings out.

 

As well, it's possible that the network nodes needed to connect to a server has changed and that is why your ping has gone up.

 

This happened to me with League of Legends. I used to have low 50s and now I have low 1xx ping (usually 130).

Remember your ISP can test from their server (which probably have better/more stable nodes they can ping/tracert to) to your modem and still get good pings.

 

Consider the following:

Microsoft Windows [Version 6.1.7601]

Copyright © 2009 Microsoft Corporation. All rights reserved.

 

C:\Windows\system32>ping 198.144.153.132

 

Pinging 198.144.153.132 with 32 bytes of data:

Reply from 198.144.153.132: bytes=32 time=80ms TTL=56

Request timed out.

Reply from 198.144.153.132: bytes=32 time=80ms TTL=56

Reply from 198.144.153.132: bytes=32 time=79ms TTL=56

 

Ping statistics for 198.144.153.132:

Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),

Approximate round trip times in milli-seconds:

Minimum = 79ms, Maximum = 80ms, Average = 79ms

 

 

Ping statistics for 168.144.82.120:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 79ms, Maximum = 80ms, Average = 79ms

 

C:\Windows\system32>ping 198.144.159.130

 

Pinging 198.144.159.130 with 32 bytes of data:

Reply from 198.144.159.130: bytes=32 time=90ms TTL=56

Reply from 198.144.159.130: bytes=32 time=89ms TTL=56

Reply from 198.144.159.130: bytes=32 time=90ms TTL=56

Reply from 198.144.159.130: bytes=32 time=82ms TTL=56

 

Ping statistics for 198.144.159.130:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 82ms, Maximum = 90ms, Average = 87ms

 

Each of these nodes are in Toronto, notice how each have unique pings. One is high as 90 ping, low as 80.

 

To show the variance, I will select a location further east in Canada

 

C:\Windows\system32>ping 198.27.88.177

 

Pinging 198.27.88.177 with 32 bytes of data:

Reply from 198.27.88.177: bytes=32 time=84ms TTL=59

Reply from 198.27.88.177: bytes=32 time=85ms TTL=59

Reply from 198.27.88.177: bytes=32 time=85ms TTL=59

Reply from 198.27.88.177: bytes=32 time=84ms TTL=59

 

Ping statistics for 198.27.88.177:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 84ms, Maximum = 85ms, Average = 84ms

 

C:\Windows\system32>ping 142.4.202.125

 

Pinging 142.4.202.125 with 32 bytes of data:

Reply from 142.4.202.125: bytes=32 time=97ms TTL=58

Reply from 142.4.202.125: bytes=32 time=96ms TTL=58

Reply from 142.4.202.125: bytes=32 time=98ms TTL=58

Reply from 142.4.202.125: bytes=32 time=97ms TTL=58

 

Ping statistics for 142.4.202.125:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 96ms, Maximum = 98ms, Average = 97ms

 

Let's come closer to home to Seattle:

C:\Windows\system32>ping 208.43.144.33

 

Pinging 208.43.144.33 with 32 bytes of data:

Reply from 208.43.144.33: bytes=32 time=101ms TTL=56

Reply from 208.43.144.33: bytes=32 time=102ms TTL=56

Reply from 208.43.144.33: bytes=32 time=100ms TTL=56

Reply from 208.43.144.33: bytes=32 time=101ms TTL=56

 

Ping statistics for 208.43.144.33:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss

Approximate round trip times in milli-seconds:

Minimum = 100ms, Maximum = 102ms, Average = 101ms

 

The ping drastically increases...

However, if I ping to Montreal, I have similar pings to Toronto. Biggest gap of 7 ms.

The point of all this is to explain that, each server (node) you connect to MAY have routing issues (especially if it's based on your ISP's own backbone, typically it isn't)

If it happens to hook up to a decent backbone (the server) and your ISP, then you will get a better ping.

Link to comment
Share on other sites

If you're running Windows 8, it can easily be the drivers which aren't up-to-date.

 

My laptop which runs windows 8 has network driver issues which causes my ping to sky rocket whenever i download the smallest file.

Edited by Tommo
Link to comment
Share on other sites

Enigma that means every server then, as each servers ping when up at least 60ms, I'll try updating my chipset and network controller drivers to see if that'll do anything. I did follow a guide to enable network options, I'll take an ss of the thing when I get home.

 

cmd.png

Edited by youthedog
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share