Another high ping help request

TotallyNotABot

TotallyNotABot

New member
Hey so, we never had this issue before alpha 15.2 but ever since that update, whenever my friends join my co-op server, their pings tend to hover at around 150-450 and every 30 minutes or so they tend to spike into the hundreds of thousands. This has made the game unplayable. I would like some help in resolving this issue. I'm not really good at fixing these types of issues by myself.

What I know:

I'm aware that it most likely isn't the games fault, and that it's most likely just a coincidence that these problems appeared after the 15.2 update.

This problem is not caused by any computer specs failing to meet the requirements.

My router never has these problems on any other programs and restarting it does not help with my friends connections.

I am connected by a high quality Ethernet cable, and my friends are as well.

The server is not dedicated.

Verifying the game files did help my friends a little bit, but the ping still persists.

The ping problems only affect 2 of my friends and they both happen to use the same internet provider and live nearby, so it might not even be a problem on my end at all. Although this is probably unlikely.

My ports have not been opened, although this never was a problem before. If this is needed, could you please explain how to open/forward them?

The server is not dedicated.

So, uh yeah. I'd like some simple instructions on what I can do, and how to get any more information if needed. Just remember to explain anything to me as if I was a novice. Because I am.

Any help is appreciated.

 
Last edited by a moderator:
Read the sticky FAQ. I cover a lot of this in great detail there. Many tips and troubleshooting steps for you to help narrow it down.

 
C:\Users\Robert Dudley>tracert 192.168.1.70

Tracing route to 192.168.1.70 over a maximum of 30 hops

1 6 ms 9 ms 7 ms 192.168.0.1

2 16 ms 24 ms 20 ms 142.254.130.81

3 35 ms 48 ms 38 ms 70.125.216.93

4 24 ms 18 ms 28 ms agg22.artntxaf01r.texas.rr.com [24.175.49.233]

5 24 ms 28 ms 38 ms agg23.crtntxjt01r.texas.rr.com [24.175.36.224]

6 * * * Request timed out.

7 * * * Request timed out.

8 * * * Request timed out.

9 * * * Request timed out.

10 * * * Request timed out.

11 * * * Request timed out.

12 * * * Request timed out.

13 * * * Request timed out.

14 * * * Request timed out.

15 * * * Request timed out.

16 * * * Request timed out.

17 * * * Request timed out.

18 * * * Request timed out.

19 * * * Request timed out.

20 * * * Request timed out.

21 * * * Request timed out.

22 * * * Request timed out.

23 * * * Request timed out.

24 * * * Request timed out.

25 * * * Request timed out.

26 * * * Request timed out.

27 * * * Request timed out.

28 * * * Request timed out.

29 * * * Request timed out.

30 * * * Request timed out.

Trace complete.

what should I do know? I see a lot of timing out there, so i can only assume that this is the problem. But again idk what to do now.

Teach me O SylenThunder

 
I'm going to guess you're on wifi based on your initial ping. If you're the host, that's bad. 7 Days uses pretty heavy bandwidth, and most consumer ISP equipment doesn't have the overhead to support it. Numbers are still in an acceptable range, so we'll leave that alone for this trace. (If you are not using wifi, that's a sign that there is a bad cable, or a lot of interference along the cable. It's not a serious issue yet, but might be soon.)




Hop 5 is where the stream dies, though this doesn't really mean anything in your specific test. You're tracing to an internal address, so it's not really going anywhere. It's almost amazing that it took the route outside of your local network.

You'll need to trace your friends external IP address.

Using your trace as an example, 192.168.0.1 is your modem/router, and 142.254.130.81 is your external IP. have your friend run "tracert 142.254.130.81" and send you the results.

Then you can go the other way with their IP.

 
For kicks, here is what I get.....

Tracing route to 142.254.130.81 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1

2 9 ms 10 ms 8 ms 96.120.41.97

3 12 ms 10 ms 11 ms 68.86.140.53

4 14 ms 14 ms 14 ms 68.86.122.169

5 22 ms 21 ms 23 ms 68.86.90.45

6 22 ms 21 ms 28 ms 68.86.82.158

7 20 ms 25 ms 20 ms as7843.350ecermak.il.ibone.comcast.net [75.149.230.70]

8 57 ms 55 ms 55 ms 107.14.17.197

9 55 ms 55 ms 55 ms bu-ether24.chctilwc00w-bcr00.tbone.rr.com [66.109.9.40]

10 52 ms 55 ms 56 ms agg1.dllatxl301r.texas.rr.com [66.109.6.89]

11 53 ms 55 ms 55 ms agg1.crtntxjt01r.texas.rr.com [24.175.49.1]

12 59 ms 55 ms 55 ms agg1.artntxaf01r.texas.rr.com [24.175.36.225]

13 67 ms 70 ms 66 ms agg1.artrtx2801h.texas.rr.com [24.175.49.232]

14 53 ms 54 ms 53 ms 142.254.130.81

Trace complete.

 
Alright thanks, and yes I do use an Ethernet cabel, but it's a little old so maybe thats the issue
Click to expand...
Yeah, usually a cable connection should be under 3ms. I'm going through two switches and about 70 feet of cable, and can still keep it down that low. If you're getting those numbers with an old cable, the line is likely degrading and the insulation isn't up to par. That will cause a higher ping, and degradation of the signal data packets.

 
You must log in or register to reply here.
Back
Top