What's new
Red County Roleplay

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

High Packet loss only in RC-RP

Status
Not open for further replies.

saucey

Donator
Joined
Dec 11, 2016
Messages
861
yep, only in RC-RP. idk what happened, all of a sudden my packet loss in the server is so high but on other servers/games it doesn't lag like in RC-RP.


does anyone know the problem?
 
Cerberus said:
yep, only in RC-RP. idk what happened, all of a sudden my packet loss in the server is so high but on other servers/games it doesn't lag like in RC-RP.


does anyone know the problem?
Looks like we have the same problem.
 
I just realized that I placed this topic in an incorrect section. Can an admin move this topic to an appropriate section?
 
What fixed the problem for me was flushing my DNS.

1. Windows key + R.
2. Fill in 'cmd', hit enter
3. Type 'ipconfig /flushdns
4. Reboot PC.
 
As per usual, please run this diagnostic tool when the problem is occurring:
viewtopic.php?f=798&t=100322

And for those of you that are just repyling to this thread; please make your own topic with the result. It's not efficient to help multiple people in the same topic and it just causes confusion.
 
fr0st said:
As per usual, please run this diagnostic tool when the problem is occurring:
viewtopic.php?f=798&t=100322

And for those of you that are just repyling to this thread; please make your own topic with the result. It's not efficient to help multiple people in the same topic and it just causes confusion.

Here you go.

EDIT: Flushing my DNS and restarting my whole PC didn't work.

Running RC-RP Diagnostics test...
Retrieving system date and time.
Fri 01/12/2018
06:46 PM

------- Ping/Traceroute to EU.FROSTGAMING.COM -------:

Pinging eu.frostgaming.com [185.198.188.98] with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 185.198.188.98: bytes=32 time=392ms TTL=53
Reply from 185.198.188.98: bytes=32 time=392ms TTL=53
Request timed out.
Reply from 185.198.188.98: bytes=32 time=412ms TTL=52
Request timed out.
Reply from 185.198.188.98: bytes=32 time=406ms TTL=52

Ping statistics for 185.198.188.98:
Packets: Sent = 8, Received = 4, Lost = 4 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 392ms, Maximum = 412ms, Average = 400ms

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

1 <1 ms <1 ms <1 ms 192.168.1.1
2 3 ms 2 ms 3 ms 112.204.32.1.pldt.net [112.204.32.1]
3 2 ms 2 ms 3 ms 122.2.175.166.static.pldt.net [122.2.175.166]
4 2 ms 2 ms 2 ms 210.213.131.97.static.pldt.net [210.213.131.97]
5 147 ms 147 ms 147 ms ae-12.r06.plalca01.us.bb.gin.ntt.net [157.238.179.225]
6 296 ms 298 ms 296 ms ae-15.r02.snjsca04.us.bb.gin.ntt.net [129.250.4.119]
7 148 ms 147 ms 147 ms ae-11.r23.snjsca04.us.bb.gin.ntt.net [129.250.6.118]
8 172 ms 165 ms 165 ms ae-3.r21.sttlwa01.us.bb.gin.ntt.net [129.250.3.125]
9 165 ms 164 ms 165 ms ae-0.r20.sttlwa01.us.bb.gin.ntt.net [129.250.2.53]
10 235 ms 234 ms 235 ms ae-0.r24.nycmny01.us.bb.gin.ntt.net [129.250.4.14]
11 305 ms 305 ms 305 ms ae-9.r24.londen12.uk.bb.gin.ntt.net [129.250.2.19]
12 307 ms 307 ms 308 ms ae-1.r04.londen12.uk.bb.gin.ntt.net [129.250.4.126]
13 * 406 ms 406 ms 185.84.16.242
14 442 ms 493 ms 428 ms 185.198.188.1
15 394 ms 397 ms * 185.198.188.3
16 394 ms 406 ms 394 ms rev.srv3.eu.frostgaming.com [185.198.188.98]

Trace complete.

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

Pinging server.redcountyrp.com [185.145.203.234] with 32 bytes of data:
Reply from 185.145.203.234: bytes=32 time=399ms TTL=52
Reply from 185.145.203.234: bytes=32 time=385ms TTL=53
Reply from 185.145.203.234: bytes=32 time=398ms TTL=52
Reply from 185.145.203.234: bytes=32 time=398ms TTL=52
Reply from 185.145.203.234: bytes=32 time=384ms TTL=53
Request timed out.
Reply from 185.145.203.234: bytes=32 time=384ms TTL=53
Reply from 185.145.203.234: bytes=32 time=398ms TTL=52

Ping statistics for 185.145.203.234:
Packets: Sent = 8, Received = 7, Lost = 1 (12% loss),
Approximate round trip times in milli-seconds:
Minimum = 384ms, Maximum = 399ms, Average = 392ms

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

1 <1 ms <1 ms <1 ms 192.168.1.1
2 6 ms 7 ms 2 ms 112.204.32.1.pldt.net [112.204.32.1]
3 2 ms 3 ms 3 ms 122.2.175.166.static.pldt.net [122.2.175.166]
4 2 ms 2 ms 2 ms 210.213.131.97.static.pldt.net [210.213.131.97]
5 147 ms 146 ms 147 ms ae-12.r06.plalca01.us.bb.gin.ntt.net [157.238.179.225]
6 296 ms 296 ms 296 ms ae-15.r02.snjsca04.us.bb.gin.ntt.net [129.250.4.119]
7 148 ms 149 ms 150 ms ae-11.r23.snjsca04.us.bb.gin.ntt.net [129.250.6.118]
8 174 ms 165 ms 170 ms ae-3.r21.sttlwa01.us.bb.gin.ntt.net [129.250.3.125]
9 165 ms 164 ms 164 ms ae-0.r20.sttlwa01.us.bb.gin.ntt.net [129.250.2.53]
10 232 ms 232 ms 232 ms ae-0.r24.nycmny01.us.bb.gin.ntt.net [129.250.4.14]
11 298 ms 298 ms 298 ms ae-9.r24.londen12.uk.bb.gin.ntt.net [129.250.2.19]
12 299 ms 299 ms 299 ms ae-1.r04.londen12.uk.bb.gin.ntt.net [129.250.4.126]
13 399 ms * 398 ms 185.84.16.242
14 * * 420 ms 185.198.188.1
15 385 ms 385 ms 385 ms 185.198.188.3
16 398 ms 398 ms 398 ms 185.145.203.234

Trace complete.

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

Pinging google.com [122.2.215.180] with 32 bytes of data:
Reply from 122.2.215.180: bytes=32 time=5ms TTL=58
Reply from 122.2.215.180: bytes=32 time=2ms TTL=58
Reply from 122.2.215.180: bytes=32 time=2ms TTL=58
Reply from 122.2.215.180: bytes=32 time=5ms TTL=58

Ping statistics for 122.2.215.180:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 5ms, Average = 3ms

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

1 <1 ms <1 ms <1 ms 192.168.1.1
2 2 ms 2 ms 2 ms 112.204.32.1.pldt.net [112.204.32.1]
3 2 ms 2 ms 2 ms 122.2.175.166.static.pldt.net [122.2.175.166]
4 4 ms 4 ms 4 ms 210.213.131.58.static.pldt.net [210.213.131.58]
5 2 ms 2 ms 2 ms 210.213.128.69.static.pldt.net [210.213.128.69]
6 2 ms 2 ms 2 ms 210.213.132.33.static.pldt.net [210.213.132.33]
7 2 ms 2 ms 2 ms 122.2.215.180.static.pldt.net [122.2.215.180]

Trace complete.

IPconfig information:

Windows IP Configuration

Host Name . . . . . . . . . . . . : Joshua-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : local

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . : local
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : FC-AA-14-B2-4D-A0
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::e54c:6cfd:3c7d:dbad%12(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.2(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Friday, January 12, 2018 1:28:59 PM
Lease Expires . . . . . . . . . . : Saturday, January 13, 2018 1:28:58 PM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 133999124
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1E-8C-C5-9C-FC-AA-14-B2-4D-A0
DNS Servers . . . . . . . . . . . : 8.8.8.8
8.8.4.4
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.local:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : local
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 10:

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:9d38:90d7:3480:1b5b:8f33:df17(Preferred)
Link-local IPv6 Address . . . . . : fe80::3480:1b5b:8f33:df17%2(Preferred)
Default Gateway . . . . . . . . . : ::
DHCPv6 IAID . . . . . . . . . . . : 251658240
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1E-8C-C5-9C-FC-AA-14-B2-4D-A0
NetBIOS over Tcpip. . . . . . . . : Disabled

*****Test Complete*****!
06:48 PM
Fri 01/12/2018
 
The control test (Google) wasn't a great comparison since traffic never left your ISP's network.

Please run the tool again the next time it happens, but also run this;
tracert 185.59.221.20

Show me the results of both. From your test resutls, it seems like there's a lot of congestion between your ISP and NTT. Could be due to peak traffic hours.
 
Status
Not open for further replies.
Back
Top