east server

Since there aren't 20 threads on it, I would have to say no.

Common reasons that you can't connect to the servers, experience disconnects, or just have lag in general...

1. You don't have the three .exe files for the client set to run as administrator.
2. You don't have the game directory set as an exception in your security softwares.
3. Your network adapter driver is out of date and needs to be refreshed.
4. Your local area network settings are improperly configured.
5. You have more than one firewall and don't realize it.
6. Your firewall settings are too strict. (Very common with ZoneAlarm and Commodo firewall.)
7. Your router is configured improperly.
8. you have a bad network cable.
9. You're using a wireless network connection. (Which leads to another huge list.)
10. You have a lot of traffic on your local network that is bogging your router/modem down.
11. There's a fault in your router.
12. There's a fault in your modem.
13, You have a bad phone cord plugged into your modem.
14. There's an issue with your house wiring.
15. There's an issue with your outside wiring.
16. A squirrel chewed on your phone line at the pole and it's raining. (I've had this happen personally.)
17. A switch/router at the CO for your ISP is having an issue.
18. One of the many hubs between you and PWI is having an issue. (most common)
19. There is heavy sunspot activity. (has happened within the past two years)
20. There's a regional router outage. (Has happened several times, most recently just a couple of weeks ago.)

That's just a few. The more details you give, the better I can narrow it down and tell you what the issue is.

Post a copy of a traceroute to the server.

stargatez wrote: »

traceroute goes from us to PWI so if it shows high on the end of the list (which would be PWI's end), means it is coming from PWI because the server runs in reverse order, from PWI to your home or office, so it is hanging from the start.

ok, a traceroute follows the path from your PC to the server.

For example, your typical traceroute goes like this...
Hop ~ Location
1 ~ Your Router/modem
2 ~ Your ISP's CO that your router/modem connects to.
3 ~ Your ISP's regional router for your area
4 ~ A router/hub on the internet path that your signal is taking to the servers
5 ~ A router/hub on the internet path that your signal is taking to the servers
6 ~ A router/hub on the internet path that your signal is taking to the servers
7 ~ A router/hub on the internet path that your signal is taking to the servers
8 ~ A router/hub on the internet path that your signal is taking to the servers
9 ~ A router/hub on the internet path that your signal is taking to the servers
10 ~ A router/hub on the internet path that your signal is taking to the servers
11 ~ A router/hub on the internet path that your signal is taking to the servers
12 ~ The regional hub that PWE's ISP is connected to
13 ~ PWE's ISP (You will not get a ping response from this location or any past it for security reasons so they will time out.)
14 ~ PWE's Central Router
15 ~ Load balancing hubs/firewalls/ect.
16 ~ Game servers.

And if you post that info, it can help narrow down where the problem is.
Here's an example...

E:\PWI~Files>tracert -h 16 pwieast2.perfectworld.com

Tracing route to pwieast2.perfectworld.com [74.201.183.27]
over a maximum of 16 hops:

  1    <1 ms    <1 ms    <1 ms  dsldevice.att.net [192.168.1.254]
  2     8 ms     8 ms     7 ms  76-250-208-3.lightspeed.livnmi.sbcglobal.net [76.250.208.3]
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     9 ms     8 ms     9 ms  12.83.32.133
  6    16 ms    16 ms    16 ms  151.164.99.129
  7    16 ms    16 ms    16 ms  gar3.cgcil.ip.att.net [12.122.79.85]
  8    34 ms    33 ms    34 ms  cr84.cgcil.ip.att.net [12.122.132.210]
  9    35 ms    35 ms    35 ms  cr2.cgcil.ip.att.net [12.123.7.250]
 10    37 ms    36 ms    35 ms  cr1.n54ny.ip.att.net [12.122.1.1]
 11    33 ms    32 ms    32 ms  gar14.n54ny.ip.att.net [12.122.105.25]
 12     *        *        *     Request timed out.
 13    33 ms    33 ms    35 ms  border1.pc2-bbnet2.nyj001.pnap.net [216.52.95.73]
 14     *        *        *     Request timed out.
 15     *

In my case, Hops 3 and 4 are router hubs in Ohio that are set to ignore ping requests so I never get a response from them, hop 12 is a new one that I'm not used to seeing, but the ping response on the other side of it is good, so it must be set to not respond as well. If it were dropping packets, I would see some large numbers in there.
My in-game ping is showing 78ms on Dreamweaver right now and I'm not getting any lag or disconnects.