Harshlands. Lag and dc's since update 197

Have not heard anything about that so far. Lets try to see where the problem is.

Could you please provide us with a trace route from your computer to our servers?

1) In XP, click on Start > click on Run > type in "cmd"
2) On this screen type in (exactly as it is typed here): pwieast1.perfectworld.com (You can use any of the IP addresses to our servers listed below. Try several.)
Please note there is a space between "tracert" and "pwieast1.perfectworld.com"
3) Wait for the traceroute to complete.
4) Right Click on the window
5) Select the "Select all" option
6) Hit "Enter"
7) You will now be able to paste the text into your reply.

1) In Vista, click on the Windows icon/Start > click on Search > type in "cmd"
2) On this screen type in (exactly as it is typed here): pwieast1.perfectworld.com (You can also use any of the IP addresses to our servers listed below. Try several.)
Please note there is a space between "tracert" and "pwieast1.perfectworld.com"
3) Wait for the traceroute to complete.
4) Right Click on the window
5) Select the "Select all" option
6) Hit "Enter"
7) You will now be able to paste the text into your reply.

Harshlands IP addresses.

29000:74.201.183.20
29000:74.201.183.17
29000:74.201.183.18
29000:74.201.183.19

it seems Brakkie and I have the same service provider. and are having the same problem.... could this be not be a coincidence?....
heres my trace


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



Tracing route to pwieast1.perfectworld.com [74.201.183.17]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms login.router [10.0.0.2]
2 47 ms 46 ms 46 ms dsl-242-128-01.telkomadsl.co.za [41.242.128.1]
3 46 ms 46 ms 46 ms 196.43.33.121
4 46 ms 46 ms 46 ms 196.43.33.121
5 59 ms 57 ms 59 ms 196.43.10.130
6 59 ms 59 ms 57 ms 196.43.33.5
7 329 ms 332 ms 329 ms ams-ip-dir-globalc-pos-4-0-1.telkom-ipnet.co.za
[196.43.18.38]
8 416 ms 418 ms 419 ms so-0-2-0.ar2.AMS2.gblx.net [64.210.21.45]
9 410 ms 416 ms 409 ms 67.17.192.54
10 403 ms 403 ms 411 ms border1.pc2-bbnet2.nyj001.pnap.net [216.52.95.73
]
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.

darthpanda16 wrote: »

South Africa and Israel have been having networking issues for the past week or so.
We can't explain it, or fix it, just document it. Such is life on the interwebs.
Internet traffic is like car traffic on a freeway. Sometimes all is well, things go smooth. Other times, there is construction, detours, or complete traffic jams.
Both of your trace routes are stopping at our game server firewalls.
You all can try other tests from here:
http://ping.eu/
http://www.speedtest.net/
Try multiple tests to different locations around the globe.
Call your ISP, and ask how many hops they are from the backbone that they get service from. Post that info here.
Hope that helps you all a little bit! b:pleased

Thanks for the help or trying to help anyways, hehe.

Question: I did a tracert with Lost City server (which i play on now) and this is what it looks like:

Tracing route to pwigc3.perfectworld.com [64.74.134.58]
over a maximum of 30 hops:

1 9 ms 1 ms 1 ms 10.0.0.2
2 13 ms 11 ms 12 ms dsl-241-0-01.telkomadsl.co.za [41.241.0.1]
3 12 ms 11 ms 11 ms 196.43.35.73
4 12 ms 12 ms 11 ms 196.43.35.73
5 34 ms 32 ms 32 ms 196.43.10.130
6 33 ms 33 ms 32 ms 196.43.33.5
7 392 ms 390 ms 390 ms ash-ip-dir-equinix-pos-4-0.telkom-ipnet.co.za [1
96.43.18.30]
8 360 ms 358 ms 358 ms pos2-0.cr02.ash01.pccwbtn.net [63.218.94.17]
9 345 ms 345 ms 343 ms cr1-eqix-peer.wdc005.internap.net [206.223.115.1
29]
10 347 ms 345 ms 346 ms cr2-cr1.wdc005.internap.net [66.79.146.202]
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 * 349 ms * cr2.lax009.inappnet.cr1.phx007.internap.net [66.
79.147.181]
18 358 ms 357 ms 357 ms cr2.sje007.inappnet.cr2.lax009.internap.net [66.
79.147.5]
19 346 ms 358 ms 346 ms cr1-cr2.sje007.internap.net [66.79.146.189]
20 346 ms 346 ms 345 ms core3.sje.inappnet-28.cr1.sje007.internap.net [6
6.79.148.130]
21 360 ms 358 ms 358 ms border2.t7-1-bbnet1.sje004.pnap.net [66.151.144.
20]
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.

So why does it do the "request timeout" thing, but it works?

I also did a few tracerts with other sites and most went all the way thru. One didn't, but the website works o.O.

Could this problem have something to do with the update? And or PWI's firewalls? (not pointing fingers or blaming or anything, just trying to look at the options b:victory)

Sorry if I'm a total noob =P

Thanks for the help/effort.

Can you all please post and vote in this thread here for us?

http://pwi-forum.perfectworld.com/showthread.php?t=481412\

Thanks!

b:victory

Your hops (each domain listed) is a pretty high number, plus you are getting hundreds of milliseconds on some of those hops before you get to our firewalls.

It isn't anything we can fix on end.

I hate dealing with networking issue myself when I'm playing games, I understand your all's frustrations. b:surrender