Death Warrant Forums

iv had some verry big packet loss problems which cant be solved by resetting the routor or reloading the server "on the 2nd server havent tryed the first" i have don a tracert and these are the results

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

D:\Documents and Settings\Andrew>tracert 208.100.49.220

Tracing route to ip220.208-100-49.static.steadfast.net [208.100.49.220]
over a maximum of 30 hops:

1 13 ms 99 ms 99 ms api.home [192.168.1.254]
2 23 ms 22 ms 35 ms 217.32.147.100
3 23 ms 24 ms 27 ms 217.32.147.142
4 32 ms 28 ms 49 ms 213.120.181.110
5 30 ms 28 ms 29 ms 217.32.25.22
6 35 ms 34 ms 38 ms 217.32.25.178
7 28 ms 78 ms 31 ms acc1-10GigE-1-2-0.sf.21cn-ipp.bt.net [109.159.25
1.70]
8 32 ms 32 ms 32 ms core1-te0-4-0-2.ealing.ukcore.bt.net [109.159.25
1.1]
9 32 ms 55 ms 39 ms transit1-xe11-0-0.ealing.ukcore.bt.net [62.6.200
.110]
10 32 ms 32 ms 49 ms t2c1-ge8-0-0.uk-eal.eu.bt.net [166.49.168.17]
11 42 ms 51 ms 32 ms t2c2-p3-0-0.uk-lon1.eu.bt.net [166.49.208.210]
12 34 ms 36 ms 34 ms t2a1-ge7-0-0.uk-lon1.eu.bt.net [166.49.135.110]

13 112 ms 121 ms 122 ms linx1.lon00.steadfast.net [195.66.225.48]
14 232 ms 103 ms 116 ms ip245.67-202-117.static.steadfast.net [67.202.11
7.245]
15 123 ms 123 ms 139 ms vl994.core3.chi01.steadfast.net [208.100.32.9]
16 127 ms 138 ms 122 ms ip220.208-100-49.static.steadfast.net [208.100.4
9.220]

Trace complete.
if any one would tell me how to fix the roblem or tell me whats wrong i would be verry thankfull.

I use ping plotter to do trace routes . It will show your pl in the first column. I don't see any listed there . They have 3 versions one is free ware . You can download it HERE.
Ping Plotter.com

Well I am guessing by the hops your in the UK. When do you have the packet loss in game. Is it in the beginning or in the later waves? It looks like it takes you 99ms to go from your machine to your router and it should only take 1ms. Once you leave your router your fine until hop 13 where you jump on linx1.lon00.steadfast.net and hit 122ms. From there your about the same to the server. If you are in fact from the UK then I would think that's about normal considering the distance.

I would look at your nic card because the 1st thing that jumps out at me is the 99ms from machine to router which is probably in your room or close by. It could be a bad cable as well.

If your having pl in the later waves of the game I would look at your ps. I only say this because I had an issue where in wave 9-15 I couldn't see any weapons fire or monsters. I had a 500w ps and it must have had problems. Went to a new 850w and problem solved. The bad news was I replaced everything in my computer 1st and the last thing I ever thought would cause the problem was the ps. So whenever someone says pl in their post I always throw out check the ps.

Hope this helps

his first column is 13ms . What do the second two columns represent ?

also using tracert

To trace a path and provide network latency and packet loss for each router and link in the path, use the pathping command.

http://www.microsoft.com/resources/docu ... x?mfr=true

DW_Bomzin wrote:his first column is 13ms . What do the second two columns represent ?

Each hop is tested 3 times when doing a tracert and this is called round trip times or RTT for short. In this case his 1st attempt was 13ms but both the 2nd and 3rd attempt was 99ms. This tells me there is an issue from his machine to his router or vice versa. When I do a tracert to anything my RTT to my router are usually 1ms for all 3 tests. Although sometimes I will get a 5ms or 8ms in my 1st RTT but the 2nd 3rd are always 1ms.

Although 99ms is not really a big problem as his RTT's are better during each hop until hop 13. But even at 100ms+ it shouldn't cause huge pl. That is why I asked when the pl starts. Is it as soon as he starts playig the game or is it after wave 9 or 10.

Hmm. Still shows pl the other way . Looks like I may have issues.

I always look at the 3rd RTT as the 1st and 2nd can have problems but by the 3rd test the route has been established. If you look at your tracert on hop 10 your ping is 78ms on the 1st test but then on the 2nd it jumped up to 152ms but came back to 77ms on the 3rd test. On Pingplotter both of us have a problem in Chicago. But if I do another test using pingplotter everything looks better and hop 11 clears up. Just depends on traffic and routing at the time of test.

IMO the Chicago backbone is the problem for both of us. There's just to much congestion in Chicago.

I just noticed I'm not routed through Dallas before I go to Chicago. It's a straight line from Tampa through Atlant to Chicago. Brighthouse must have made a change to their routing table :cheers:

Karma was seeing different routing last night also with a large ping increase.