lag

[Thonger]

honestly i'm getting kinda tired of beating this dead horse...
but i'm still having really bad lag issues.

if i can't solve this i'm seriously considering uninstalling this game, for good. what's supposed to be "fun" is just frustrating, 90% of the time. and i seriously should do something better with my time if i'm not having fun.

ISP is time warner broadband.

so here's what's been done:

- got a new computer, about 5 mo old (at least solved the hardware lag issue)
- was having connectivity problems via broadband, so had the ISP send their technician to test the line, recheck and test the connection at the street
- i run no router
- i reset the cable modem when it's really bad (cable modem is less than 4 months old, and i had the same issues with the ISP supplied modem), and it doesn't really seem to fix anything
- i reboot when i have a lot of lag issues, also doesn't really fix anything
- i try to minimize the # of processes running in the background while i run 42, via tcp manager and admin on cmd (turning off windows updates and some other windows tcp connections)

some suggested that i was having packet loss issues, so i ran a packet loss test on pingtest.net from hawaii to dallas, tx and go the following results:

try 1: 103 ms, 5 ms jitter, 0% packet loss
try 2: 104 ms, 4 ms jitter, 0% packet loss
try 3: 259 ms, 22 ms jitter, 0% packet loss
try 4: 113 ms, 17 ms jitter, 0% packet loss
try 5: 103 ms, 5 ms jitter, 0% packet loss
try 6: 100 ms, 5 ms jitter, 0% packet loss
try 7: 99 ms, 3 ms jitter, 0% packet loss
try 8: 101 ms, 12 ms jitter, 0% packet loss
try 9: 99 ms, 4 ms jitter, 0% packet loss
try 10: 103 ms,7 ms jitter, 0% packet loss

i've been having lag issues nearly the entire time i've been playing 42/dc, through 3 different computers and many different cable modems. the only things that seem to be common between all of them is my ISP has never changed, and the servers I visit for 42/dc rarely change. if there's a problem it's so intermittent, ISP techs can't figure it out, because every time they run a speedtest via ookla they get normal pings and transfer rates (as indicated by my test on pingtest.net). but every few seconds the ping spikes.

and once in awhile, i'll have zero lag, and i'll play this game the way it was meant to be played. but that's less than 10% of the time.

any thoughts? is this a server side lag issue? or is the signal bottlenecking somewhere on the way to EA117? it doesn't seem so.

[Mali Mrav]

server side lag
it isnt you me or others
its the server

[Trench]

its the server

But then everyone would have it, and they don't.

so i ran a packet loss test on pingtest.net from hawaii to dallas, tx and go the following results

The information you want to see first is the results of "tracert.exe 8.12.64.130" from your Windows machine, because that will expose which of the routes between you and Dallas actually account for the slow-down. It may even show you that when the ping seems radically faster/slower, it's because the traffic is taking a different route entirely.

And yes, if the issue actually was at the server host OS, it would show that too, since the drastic time difference would all be in the last hop to the server, rather than somewhere in the middle of the route.

There are so many factors in how the traffic gets from point to point that it would be strange to assume the issue could only be at one end or the other. But no need to guess, just take a trace route and look.

Maybe the NSA forgot to put everything back together right when tapping your undersea cable.

-Trench

[S.O.S]

Sounds like the problem is your internet connection. Check your modem status by going to 192.168.100.1 (for most modems, can be different and you need to Google it). Look under Signal. Your downstream Signal to Noise Ratio should be better than 25 (around 40 is good), power level within -8 to 8 dBmV (0 would be ideal), upstream Power Level around 40 dBmV. Also check the correctable and uncorrectable errors, the less the better. If any of the numbers are out of range, your cable connection is bad. Could be a loose/bad cable, too many splitters etc.

[pistol]

You're in Hawaii. I wouldn't expect the best. Nor from Mali in Europe.

I'm on the East Coast and I haven't seen any lag recently. But I don't expect a ping of 10 either.

[zanshin1]

IMO.....theres been alot of server lag lately.....in game hiccups....

but at least few times a week.....my ping flies....like im in europe...and im not, tyvm

idk if those dueches meesin wit ya again or not....buuuuuuuuuuuttt

[=sBs=SEANY]

But seriously, my connection and ping are usually great between Canada (east of Toronto) and Dallas. When I do get hit by lag on the server, it's often debilitating spikes (this accounts for all times I have ever been knifed). There is a thread somewhere from last year where a few of us were running traceroutes and seemed to find a common denominator in the last hops of the gt network in Dallas, but I recall we couldn't pinpoint any specific server.

Like Trench said though, next time you start getting lag do a quick minimize (or console+"exit" if your pc is slow), open a cmd prompt and do a traceroute to the server. That should show you where the problem lies, but just remember, the NSA already knows everything, it's too late.

[i_am_not_your_father]

Are you running any antivirus software on the background? If so, disable it at least when you play DC. Have you paid attention to any correlation between the time of the day when you play and when the lag occurs? Consider that the server gets the busiest after 7PM eastern time (at least when I used to play) which is about 3PM your time zone? What time do you normally play? If it is after 5-6pm, your time, thats probably the most net congestion you will experience on your end as people are off work, assuming you live in the suburbs.

[Thonger]

Trench, results of the tracert:


Tracing route to 8.12.64.130 over a maximum of 30 hops

1 8 ms 10 ms 8 ms 142.254.191.109
2 19 ms 26 ms 17 ms xe-0-0-12.hnllhiqe01h.hawaii.rr.com [24.25.230.9]
3 9 ms 9 ms 18 ms 72.129.46.22
4 56 ms 59 ms 59 ms agg31.lsancarc01r.socal.rr.com [72.129.45.0]
5 59 ms 63 ms 63 ms bu-ether16.lsancarc0yw-bcr00.tbone.rr.com [66.109.6.102]
6 65 ms 65 ms 65 ms 0.ae1.pr1.lax00.tbone.rr.com [107.14.17.250]
7 60 ms 61 ms 68 ms ix-24-0.tcore1.LVW-Los-Angeles.as6453.net [66.110.59.81]
8 81 ms 85 ms 86 ms 66.110.59.102
9 87 ms 87 ms 86 ms et-2-1-0.dal34.ip4.gtt.net [89.149.184.177]
10 91 ms 90 ms 89 ms as20473.xe-5-1-2.cr1.dfw1.us.as4436.gtt.net [69.31.63.238]
11 89 ms 89 ms 89 ms 8.12.64.130

Signal to Noise Ratio:
37 dB 37 dB 37 dB 38 dB

Power level:
1 dBmV 0 dBmV 0 dBmV 1 dBmV

Upstream power level:
42 dBmV 41 dBmV 43 dBmV 44 dBmV

Total Unerrored Codewords 11005724163 11005724885 11005725381 11005725826
Total Correctable Codewords 3932 3585 3181 2913
Total Uncorrectable Codewords 667 516 561 523

IANYF:

I'm on Hawaii time,
I play usually after work M-F 1700-2000
On weekends, it could be any time there's server population.

I'm running AVG antivirus. But you'd think if it was software side updates or resident programs the lag would be consistent, and it's really not.

Thanks for the insight guys.

[Mali Mrav]

thong i remove my avast and there is no lag anymore

[Trench]

So ~40ms to tunnel under the Pacific, and then ~40ms to get from LA to Dallas. Both of which seem pretty reasonable, and I would have said is "no issue" for coming from Hawaii. (Not that I have any experience using the Pacific cable.) If that's not normal for Hawaii to the mainland, maybe we'll see that in one of the future TRACERTs. (i.e. Future trace showing Hawaii to LA notably quicker than what's shown here.)

I'd compare this to what you see when it's lagging heavy, and run three or four of them back-to-back when you're lagging. Since the issue could be very short-lived (but frequent to make you notice), so multiple traces will help up the odds that you'll see what's happening even if the issue was intermittent and didn't affect necessarily all of the TRACERT runs.

For what it's worth, what you showed seems to match what I get trying to reach you from North Texas right at this moment:

Tracing route to xe-0-0-12.hnllhiqe01h.hawaii.rr.com [24.25.230.9]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms FIOS_Quantum_Gateway.fios-router.home [xx.xx.xx.xx]
2 4 ms 4 ms 4 ms xxxxxxxxxxx.xxxxxxxxxx.verizon-gni.net [xx.xx.xx.xx]
3 7 ms 6 ms 6 ms 172.102.51.78
4 * * * Request timed out.
5 37 ms 36 ms 36 ms 0.ae1.XL3.LAX15.ALTER.NET [140.222.227.15]
6 41 ms 36 ms 34 ms TenGigE0-6-0-5.GW5.LAX15.ALTER.NET [152.63.112.254]
7 33 ms 33 ms 34 ms tba.customer.alter.net [152.179.21.134]
8 39 ms 39 ms 39 ms bu-ether24.tustca4200w-bcr00.tbone.rr.com [66.109.9.27]
9 40 ms 39 ms 39 ms agg1.tustcaft01r.socal.rr.com [66.109.6.65]
10 36 ms 39 ms 39 ms agg10.lsancarc01r.socal.rr.com [66.75.161.49]
11 83 ms 83 ms 84 ms agg1.milnhixd-ccr01.hawaii.rr.com [72.129.45.1]
12 88 ms 99 ms 99 ms xe-0-0-12.hnllhiqe01h.hawaii.rr.com [24.25.230.9]

Trace complete.

-Trench

[slogvn]

Some unsolicited advice: Ditch the AV programs altogether and start using Firefox with NoScript installed. I still keep the free version of Malwarebytes around to run the occasional manual scan on downloaded files, but that's it. With a little common sense you shouldn't ever have to worry about viruses again.

[Thonger]

Tracert / ping results after heavy lag today:

Tracing route to 8.12.64.130 over a maximum of 30 hops
1 8 ms 8 ms 8 ms 142.254.191.109
2 20 ms 21 ms 21 ms xe-0-0-12.hnllhiqe01h.hawaii.rr.com [24.25.230.9]
3 10 ms 10 ms 10 ms 72.129.46.22
4 58 ms 59 ms 59 ms agg31.lsancarc01r.socal.rr.com [72.129.45.0]
5 60 ms 63 ms 63 ms bu-ether16.lsancarc0yw-bcr00.tbone.rr.com [66.109.6.102]
6 58 ms 81 ms 57 ms 0.ae1.pr1.lax00.tbone.rr.com [107.14.17.250]
7 63 ms 60 ms 61 ms ix-24-0.tcore1.LVW-Los-Angeles.as6453.net [66.110.59.81]
8 85 ms 84 ms 86 ms 66.110.59.102
9 87 ms 88 ms 86 ms et-2-1-0.dal34.ip4.gtt.net [89.149.184.177]
10 91 ms 90 ms 90 ms as20473.xe-5-1-2.cr1.dfw1.us.as4436.gtt.net [69.31.63.238]
11 89 ms 90 ms 89 ms 8.12.64.130

Ping for about 1 min:
Pinging 8.12.64.130 with 32 bytes of data:
Reply from 8.12.64.130: bytes=32 time=90ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=90ms TTL=50
Reply from 8.12.64.130: bytes=32 time=90ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=90ms TTL=50
Reply from 8.12.64.130: bytes=32 time=90ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=91ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=90ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=91ms TTL=50
Reply from 8.12.64.130: bytes=32 time=90ms TTL=50
Reply from 8.12.64.130: bytes=32 time=90ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=95ms TTL=50
Reply from 8.12.64.130: bytes=32 time=94ms TTL=50
Reply from 8.12.64.130: bytes=32 time=90ms TTL=50
Reply from 8.12.64.130: bytes=32 time=90ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=90ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=90ms TTL=50
Reply from 8.12.64.130: bytes=32 time=91ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=90ms TTL=50
Reply from 8.12.64.130: bytes=32 time=90ms TTL=50
Reply from 8.12.64.130: bytes=32 time=90ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=91ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=91ms TTL=50
Reply from 8.12.64.130: bytes=32 time=90ms TTL=50
Reply from 8.12.64.130: bytes=32 time=90ms TTL=50
Reply from 8.12.64.130: bytes=32 time=91ms TTL=50
Reply from 8.12.64.130: bytes=32 time=90ms TTL=50
Reply from 8.12.64.130: bytes=32 time=90ms TTL=50
Reply from 8.12.64.130: bytes=32 time=90ms TTL=50
Reply from 8.12.64.130: bytes=32 time=90ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=90ms TTL=50
Reply from 8.12.64.130: bytes=32 time=90ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=90ms TTL=50
Reply from 8.12.64.130: bytes=32 time=91ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=90ms TTL=50
Reply from 8.12.64.130: bytes=32 time=90ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=97ms TTL=50
Reply from 8.12.64.130: bytes=32 time=90ms TTL=50
Reply from 8.12.64.130: bytes=32 time=90ms TTL=50
Reply from 8.12.64.130: bytes=32 time=90ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=90ms TTL=50
Reply from 8.12.64.130: bytes=32 time=90ms TTL=50
Reply from 8.12.64.130: bytes=32 time=90ms TTL=50
Reply from 8.12.64.130: bytes=32 time=90ms TTL=50
Reply from 8.12.64.130: bytes=32 time=90ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=90ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=90ms TTL=50
Reply from 8.12.64.130: bytes=32 time=90ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=90ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=90ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50
Reply from 8.12.64.130: bytes=32 time=90ms TTL=50
Reply from 8.12.64.130: bytes=32 time=90ms TTL=50
Reply from 8.12.64.130: bytes=32 time=89ms TTL=50

Ping statistics for 8.12.64.130:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 89ms, Maximum = 97ms, Average = 89ms

almost the same results, on heavy lag
ping more or less consistent, with 0% packet loss

is there any way to test the performance of my video card?

[Trench]

This is the route I was seeing trying to traceroute back your direction, about 20 minutes later:

Tracing route to xe-0-0-12.hnllhiqe01h.hawaii.rr.com [24.25.230.9]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms FIOS_Quantum_Gateway.fios-router.home [xx.xx.xx.xx]
2 4 ms 4 ms 4 ms xxxxxxxxxxx.xxxxxxxxxx.verizon-gni.net [xx.xx.xx.xx]
3 11 ms 4 ms 9 ms 172.102.49.202
4 * * * Request timed out.
5 49 ms 80 ms 31 ms 0.ae2.XL4.LAX15.ALTER.NET [140.222.227.21]
6 40 ms 33 ms 34 ms TenGigE0-7-0-9.GW5.LAX15.ALTER.NET [152.63.112.141]
7 35 ms 34 ms 34 ms tba.customer.alter.net [152.179.21.134]
8 36 ms 36 ms 39 ms bu-ether14.tustca4200w-bcr00.tbone.rr.com [66.109.6.130]
9 34 ms 39 ms 41 ms agg1.tustcaft01r.socal.rr.com [66.109.6.65]
10 86 ms 86 ms 86 ms agg1.kmlahi0701r.hawaii.rr.com [72.129.45.3]
11 85 ms 86 ms 83 ms agg10.milnhixd01r.hawaii.rr.com [72.129.45.40]
12 98 ms 101 ms 101 ms 72.129.46.23
13 86 ms 88 ms 86 ms 24.25.231.22
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.

[Mali Mrav]

here thong

Dear god do not get Avg, or Norton or any other shit av that will corrupt into your registry.
Boot safe mode, delete temp data, defrag, then go back to nornal mode, start ccleaner, revo, and mbam (malwarebytes),
go through revo and uninstall applications that you do not remember installing or that are adware.
Go in ccleaner and turn off all startup items. all scheduled tasks, all applet items. delete temp, clean registry.
Then go msconfig and turn off non microsoft 3rd party services, reboot, start mbam, go to setting and enable rootkits,
before you run it open an admin cmd and type "sfc /scannow", run that and run mbam at the same time (both will take about an hour).
after both finish reboot through mbam if it finds things otgerwise just reboot. Next grab tsa adware removal tool (tsa = tech support all),
run that, reset all browsers, go through each browser and remove any bad extensions and homepage settings. run updates,
run ccleaner one more time. lastly go through program data, app data, and program files directories and remove directories related to malware.
If you cant get it like that then back up and restore.
this is the av that i use and i have no problems

[S.O.S]

Looked at your ping when you were complaining about lags today. It was rather steady at about 90. Didn't see any spikes. So your internet connection is not the problem. Likely something running in the background is the culprit. Start task manager while you are having lags, see what's using a lot of cpu and memory. I see 30-40% usage on my i5-4690K based system. Disable AV and firewall when playing should help you rule out whether they are the issues. You said your PC is new, what are the configurations?

[Thonger]

went thru Mali's suggestions to turn off resident programs running on restart/startup.

also just now figured out how to turn off other stuff that I probably don't need or want like the Windows 10 upgrade reminder, etc.

we'll see if it makes any difference.

thanks for all the suggestions.

[Mali Mrav]

https://gyazo.com/297d1ee41a8c17fa553a7bf0baa91596
https://gyazo.com/732dff8ca72253cbbc863e91c8dd5cfe
https://gyazo.com/c70bdc70dbd77b2dc09b7d2f6c93996f

[Thonger]

(btw, the 76 processes was when 42 was running)

PROCESSES



SERVICES

[Mali Mrav]

click on show all process and then post a pic so i can see all of them

[Trench]

This is the route I was seeing trying to traceroute back your direction, about 20 minutes later:

Sorry, had to go back to work and ran out of time to complete that post. Back on February 21, the route shown when I tracerouted back to your address had only a single hop inside Hawaii. i.e. We went from California, to a router in Hawaii, to your address:

9 40 ms 39 ms 39 ms agg1.tustcaft01r.socal.rr.com [66.109.6.65]
10 36 ms 39 ms 39 ms agg10.lsancarc01r.socal.rr.com [66.75.161.49]
11 83 ms 83 ms 84 ms agg1.milnhixd-ccr01.hawaii.rr.com [72.129.45.1]
12 88 ms 99 ms 99 ms xe-0-0-12.hnllhiqe01h.hawaii.rr.com [24.25.230.9]

The traceroutes I took today when you were having lag all showed something different. In addition to taking multiple hops inside Hawaii, my traceroute never does receive an answer from your modem like it did the day before:

9 34 ms 39 ms 41 ms agg1.tustcaft01r.socal.rr.com [66.109.6.65]
10 86 ms 86 ms 86 ms agg1.kmlahi0701r.hawaii.rr.com [72.129.45.3]
11 85 ms 86 ms 83 ms agg10.milnhixd01r.hawaii.rr.com [72.129.45.40] (different router for entering Hawaii, which is not unusual and can just be load balance)
12 98 ms 101 ms 101 ms 72.129.46.23 (didn't go straight to your modem; unexpected since 72.129.45.1 router had been able to go straight there)
13 86 ms 88 ms 86 ms 24.25.231.22 (still didn't go to your modem; even more unexpected)
14 * * * Request timed out. (can't see, don't know)
15 * * * Request timed out. (can't see, don't know)
...

The "request timed out" just means we didn't get a ICMP TTL Expired back from the next hop, so we don't know who it was. We're guessing it was either supposed to be your modem or yet another new router in the 24.xx.xx.xx network, but we don't hear anything back from either one.

Given that you're having issues, seeing your traffic pass through three times as many Hawaii routers on it's way back to you (and maybe more, if we could see past 24.25.231.22) makes me /want/ to suspect this difference is related to the issue. But let's see if the route goes back to the way it was, and/or what the route looks like when you feel like the lag isn't there for a bit.

Certainly agree with SOS, Mali and everyone that local workstation-side software can create lag symptoms. The route your traffic takes across the world is just the more interesting possibility (to me), because that's been my problem several times. And it's always frustrating before and even after you know it, because it's something you have no hand in creating or solving.

-Trench

[Thonger]

Mali:

[Thonger]

Trench,

I'm going to pretend I'm smart enough to decipher what you just wrote. lol.

But it sounds like the paths between my IP and EA117 has a bottleneck somewhere. Is my tracert going to be identical to yours (in reverse)? That is, does the signal coming back to me return through its original path or does it take the path you're seeing from your end?

[Mali Mrav]

thong add me on facebook so i can tell u something
https://www.facebook.com/ante.nespava
so we can figure what is your problem
dont take it personaly

[Mali Mrav]

why u have a lot of servises running?
i have 30 running maybe u need to shut some down look on google every services and disable it if u dont want him to be running