What's new

Packet loss again

Status
Not open for further replies.

Crazy Andre

Retired Admin
Joined
May 10, 2010
Messages
8,631
Having issues again with packet loss making it unplayable. Help pls. :)

Code:
Running RC-RP Diagnostics test... 
Retrieving system date and time. 
Mon 10/23/2017 
04:00 PM
 
------- Ping/Traceroute to EU.FROSTGAMING.COM -------: 

Pinging eu.frostgaming.com [164.132.200.17] with 32 bytes of data:
Reply from 164.132.200.17: bytes=32 time=87ms TTL=51
Reply from 164.132.200.17: bytes=32 time=87ms TTL=52
Reply from 164.132.200.17: bytes=32 time=86ms TTL=52
Reply from 164.132.200.17: bytes=32 time=86ms TTL=52
Reply from 164.132.200.17: bytes=32 time=83ms TTL=52
Reply from 164.132.200.17: bytes=32 time=86ms TTL=52
Reply from 164.132.200.17: bytes=32 time=88ms TTL=52
Reply from 164.132.200.17: bytes=32 time=87ms TTL=52

Ping statistics for 164.132.200.17:
    Packets: Sent = 8, Received = 8, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 83ms, Maximum = 88ms, Average = 86ms

Tracing route to eu.frostgaming.com [164.132.200.17]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  FIOS_Quantum_Gateway.fios-router.home [192.168.1.1] 
  2     5 ms     7 ms     3 ms  lo0-100.WASHDC-VFTTP-379.verizon-gni.net [72.66.1.1] 
  3    12 ms    15 ms     *     B3379.WASHDC-LCR-22.verizon-gni.net [100.41.216.226] 
  4     *        *        *     Request timed out.
  5     9 ms     6 ms     7 ms  0.ae8.GW11.IAD8.ALTER.NET [140.222.234.17] 
  6    11 ms    11 ms    10 ms  teliasonera-gw.customer.alter.net [204.148.11.138] 
  7     8 ms    10 ms    10 ms  ash-bb3-link.telia.net [80.91.248.156] 
  8    14 ms    15 ms    14 ms  nyk-bb3-link.telia.net [62.115.141.245] 
  9    13 ms    15 ms    14 ms  nyk-b2-link.telia.net [213.155.130.28] 
 10    14 ms    14 ms    16 ms  be100-154.nwk-5-a9.nj.us [192.99.146.38] 
 11    85 ms    84 ms    84 ms  be100-1298.ldn-5-a9.uk.eu [192.99.146.132] 
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15    86 ms    87 ms    85 ms  ns3038202.ip-164-132-200.eu [164.132.200.17] 

Trace complete.
 
------- Ping/Traceroute to SERVER.REDCOUNTYRP.COM -------: 

Pinging server.redcountyrp.com [178.32.108.245] with 32 bytes of data:
Reply from 178.32.108.245: bytes=32 time=85ms TTL=52
Reply from 178.32.108.245: bytes=32 time=87ms TTL=52
Reply from 178.32.108.245: bytes=32 time=86ms TTL=52
Request timed out.
Reply from 178.32.108.245: bytes=32 time=84ms TTL=52
Reply from 178.32.108.245: bytes=32 time=86ms TTL=52
Reply from 178.32.108.245: bytes=32 time=89ms TTL=52
Reply from 178.32.108.245: bytes=32 time=88ms TTL=52

Ping statistics for 178.32.108.245:
    Packets: Sent = 8, Received = 7, Lost = 1 (12% loss),
Approximate round trip times in milli-seconds:
    Minimum = 84ms, Maximum = 89ms, Average = 86ms

Tracing route to server.redcountyrp.com [178.32.108.245]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  FIOS_Quantum_Gateway.fios-router.home [192.168.1.1] 
  2     5 ms     8 ms     6 ms  lo0-100.WASHDC-VFTTP-379.verizon-gni.net [72.66.1.1] 
  3     9 ms     8 ms    11 ms  B3379.WASHDC-LCR-21.verizon-gni.net [100.41.216.196] 
  4     *        *        *     Request timed out.
  5     9 ms     6 ms     8 ms  0.ae9.GW11.IAD8.ALTER.NET [140.222.234.13] 
  6    10 ms    10 ms    12 ms  teliasonera-gw.customer.alter.net [204.148.11.138] 
  7    11 ms    10 ms    10 ms  ash-bb3-link.telia.net [80.91.248.156] 
  8     *        *        *     Request timed out.
  9    13 ms    15 ms    13 ms  nyk-b2-link.telia.net [213.155.130.28] 
 10    14 ms    15 ms    14 ms  be100-154.nwk-5-a9.nj.us [192.99.146.38] 
 11    83 ms    85 ms    82 ms  be100-1298.ldn-5-a9.uk.eu [192.99.146.132] 
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15    86 ms    90 ms    89 ms  ip245.ip-178-32-108.eu [178.32.108.245] 

Trace complete.
 
------- Ping/Traceroute to GOOGLE.COM -------: 

Pinging google.com [172.217.12.238] with 32 bytes of data:
Reply from 172.217.12.238: bytes=32 time=9ms TTL=56
Reply from 172.217.12.238: bytes=32 time=7ms TTL=56
Reply from 172.217.12.238: bytes=32 time=9ms TTL=56
Reply from 172.217.12.238: bytes=32 time=10ms TTL=56

Ping statistics for 172.217.12.238:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 7ms, Maximum = 10ms, Average = 8ms

Tracing route to google.com [172.217.12.238]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  FIOS_Quantum_Gateway.fios-router.home [192.168.1.1] 
  2     6 ms     6 ms     4 ms  lo0-100.WASHDC-VFTTP-379.verizon-gni.net [72.66.1.1] 
  3    14 ms    15 ms    11 ms  B3379.WASHDC-LCR-21.verizon-gni.net [100.41.216.196] 
  4     *        *        *     Request timed out.
  5     9 ms    10 ms    10 ms  0.ae13.GW9.IAD8.ALTER.NET [140.222.236.139] 
  6    10 ms    10 ms     8 ms  pool-96-236-104-66.burl.east.verizon.net [96.236.104.66] 
  7     *        *        *     Request timed out.
  8     9 ms    10 ms    10 ms  72.14.234.135 
  9     8 ms     8 ms     6 ms  iad30s15-in-f14.1e100.net [172.217.12.238] 

Trace complete.
 
IPconfig information: 

Windows IP Configuration

   Host Name . . . . . . . . . . . . : Andre
   Primary Dns Suffix  . . . . . . . : 
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : fios-router.home

Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . : fios-router.home
   Description . . . . . . . . . . . : Killer E2400 Gigabit Ethernet Controller
   Physical Address. . . . . . . . . : 4C-CC-6A-47-00-C9
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::84f7:bf32:1dd7:d90e%7(Preferred) 
   IPv4 Address. . . . . . . . . . . : 192.168.1.161(Preferred) 
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Wednesday, October 18, 2017 4:06:42 PM
   Lease Expires . . . . . . . . . . : Tuesday, October 24, 2017 11:32:07 AM
   Default Gateway . . . . . . . . . : 192.168.1.1
   DHCP Server . . . . . . . . . . . : 192.168.1.1
   DHCPv6 IAID . . . . . . . . . . . : 122473578
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1F-51-4A-5F-B4-75-0E-24-2E-52
   DNS Servers . . . . . . . . . . . : 192.168.1.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Wireless LAN adapter Wi-Fi:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Belkin USB Wireless Adaptor
   Physical Address. . . . . . . . . : B4-75-0E-24-2E-52
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 10:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Microsoft Hosted Network Virtual Adapter
   Physical Address. . . . . . . . . : B4-75-0E-24-2E-52
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 11:

   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Microsoft Teredo Tunneling Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:cc3:17f7:b7bd:fe11(Preferred) 
   Link-local IPv6 Address . . . . . : fe80::cc3:17f7:b7bd:fe11%13(Preferred) 
   Default Gateway . . . . . . . . . : ::
   DHCPv6 IAID . . . . . . . . . . . : 218103808
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1F-51-4A-5F-B4-75-0E-24-2E-52
   NetBIOS over Tcpip. . . . . . . . : Disabled
 
*****Test Complete*****! 
04:03 PM
Mon 10/23/2017
 

Max Bluman

Donator
Joined
Apr 1, 2016
Messages
282
All of your traceroutes and pings look fine to me, the server itself experiences packet loss from time to time due to OVH network. Does it happen once every few hours or is it 24/7?
 

TheGhosT.

Member
Joined
Oct 17, 2017
Messages
36
Max Bluman said:
All of your traceroutes and pings look fine to me, the server itself experiences packet loss from time to time due to OVH network. Does it happen once every few hours or is it 24/7?
Not 24/7 for me.
However, I receive daily bullshit when server has more than 90 players which is absolute nuts :thumbdown: . I want this to be fixed for real. :alcoholic:
 

Mike Swain

Member
Joined
Oct 27, 2017
Messages
19
I used to have this problem where my ping kept going over 800 and more when it ussually was the normal 100-150
I did this and it helped me.
Windows 7 though. Also I checked if all drivers were working.
Step 1

Click the "Start" button on the Windows 7 taskbar and click the "Search" box. Type "regedit" in the "Search" box and tap the "Enter" key.

Step 2

Navigate to the "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Multimedia\SystemProfile" directory in the "Registry Editor" window that appears.

Step 3

Double-click on the "NetworkThrottlingIndex" key. Type "FFFFFFFF" into the "Value data" field of the window that appears.

Step 4

Click the "OK" button. Click the "X" located in the upper-right corner of the "Registry Editor" window to close the window. Reboot the computer.

This worked for me now my ping hasn't reached even 200.
Also see if all you networking drivers are working, if not then try to find a way to turn the driver on.
 

Max Bluman

Donator
Joined
Apr 1, 2016
Messages
282
Mike Swain said:
I used to have this problem where my ping kept going over 800 and more when it ussually was the normal 100-150
I did this and it helped me.
Windows 7 though. Also I checked if all drivers were working.
Step 1

Click the "Start" button on the Windows 7 taskbar and click the "Search" box. Type "regedit" in the "Search" box and tap the "Enter" key.

Step 2

Navigate to the "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Multimedia\SystemProfile" directory in the "Registry Editor" window that appears.

Step 3

Double-click on the "NetworkThrottlingIndex" key. Type "FFFFFFFF" into the "Value data" field of the window that appears.

Step 4

Click the "OK" button. Click the "X" located in the upper-right corner of the "Registry Editor" window to close the window. Reboot the computer.

This worked for me now my ping hasn't reached even 200.
Also see if all you networking drivers are working, if not then try to find a way to turn the driver on.
This won't do anything LOL.
 

TheGhosT.

Member
Joined
Oct 17, 2017
Messages
36
Packetloss also increases due to mods too.
I removed some mods when I had 6.49PacketLoss and it reduced it to 3.10 which still lagged me but worked better than the old packetloss.
This probably happens due to ENB and HUD mods.
 

Mike Swain

Member
Joined
Oct 27, 2017
Messages
19
Max Bluman said:
Mike Swain said:
I used to have this problem where my ping kept going over 800 and more when it ussually was the normal 100-150
I did this and it helped me.
Windows 7 though. Also I checked if all drivers were working.
Step 1

Click the "Start" button on the Windows 7 taskbar and click the "Search" box. Type "regedit" in the "Search" box and tap the "Enter" key.

Step 2

Navigate to the "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Multimedia\SystemProfile" directory in the "Registry Editor" window that appears.

Step 3

Double-click on the "NetworkThrottlingIndex" key. Type "FFFFFFFF" into the "Value data" field of the window that appears.

Step 4

Click the "OK" button. Click the "X" located in the upper-right corner of the "Registry Editor" window to close the window. Reboot the computer.

This worked for me now my ping hasn't reached even 200.
Also see if all you networking drivers are working, if not then try to find a way to turn the driver on.
This won't do anything LOL.
It actually did for me. When I was playing everyone was either AFK or sliding around crazy and my ping was over 400 and more, after I did these steps my ping is around 100-180 Max and I have no issues wtih packetloss or ping. It wasn't playable untill I did that.
 

Crazy Andre

Retired Admin
Joined
May 10, 2010
Messages
8,631
Max Bluman said:
All of your traceroutes and pings look fine to me, the server itself experiences packet loss from time to time due to OVH network. Does it happen once every few hours or is it 24/7?
Random, every few hours. Was so bad at one point during summer I couldn't get on for almost an entire month. :lol:
 

Giga

Donator
Joined
Dec 4, 2010
Messages
18,945
Location
MNL
The recent server migration should hopefully rectify the issue. If you are still having packet loss issues with the server, please forward your concern in the given thread or submit a new thread in the Host Support board for better organization.
 
Status
Not open for further replies.
Top