DCings....

Have you run a check file on PoL and FFXI files? Possibly a corrupt armor file causes the DC.

Quote:

Originally Posted by Zagen

Have you run a check file on PoL and FFXI files? Possibly a corrupt armor file causes the DC.

Yes. I have. If something is wrong, crucially, I do a File Check to make sure everything on FFXI/PoL is working properly.

Have you run tracerts to the SE servers to which your client is trying to connect when you are having DC issues? People often find a failure in route between their ISP and SE. In other words, it could be an additional party in another state/country that is actually at fault. Sometimes it even boils down to localized security blocking incoming UDP packets or DNS pings from SE that is at fault--if the server/client looses that "heartbeat" connection long enough, you go into disconnection timeout and get dropped from the server.

Without running a full diag on the points between the client and server (firewall logs and such, and can be upwards of 20 hops, depending on location, ISP, hardware involved)...can't proclaim it is purely SE's fault or your ISP's.

If you doubt that theory, check the thread about issues O2 was having back in April/May:
http://forum.square-enix.com/ffxi/th...l=1#post308584

and, here are tracert and ping results to one such SE Server...showing lots of potential points of failure along the way:

Quote:

C:\Documents and Settings\Administrator>tracert ffxi00.pol.com

Tracing route to ffxi00.pol.com [124.150.154.122]
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms <localized IP info stripped for security reasons>
2 9 ms 12 ms 9 ms <localized IP info stripped for security reasons>
3 16 ms 17 ms 18 ms <localized IP info stripped for security reasons>
4 20 ms 23 ms 19 ms xe-5-1-1.chrlncpop-rtr1.southeast.rr.com [24.93.
64.96]
5 25 ms 23 ms 32 ms 107.14.19.48
6 83 ms 79 ms 79 ms ae-3-0.cr0.hou30.tbone.rr.com [66.109.6.36]
7 86 ms 87 ms 87 ms ae-0-0.cr0.dfw10.tbone.rr.com [66.109.6.39]
8 83 ms 85 ms 87 ms ae-3-0.cr0.lax30.tbone.rr.com [66.109.6.0]
9 80 ms 80 ms 79 ms 107.14.19.67
10 80 ms 79 ms 79 ms pacnet.com.any2ix.coresite.com [206.223.143.138]

11 177 ms 177 ms 177 ms gi8-0-0.cr1.nrt1.asianetcom.net [202.147.0.121]

12 186 ms 185 ms 186 ms gi1-0-0.gw1.nrt5.asianetcom.net [202.147.0.178]

13 186 ms 187 ms 185 ms squareco.asianetcom.net [203.192.149.210]
14 177 ms 204 ms 178 ms 61.195.56.129
15 183 ms 184 ms 184 ms 219.117.144.66
16 185 ms 183 ms 184 ms 219.117.144.45
17 187 ms 185 ms 189 ms 219.117.146.129
18 188 ms 186 ms 187 ms 219.117.146.182
19 186 ms 183 ms 183 ms 124.150.154.122

Trace complete.

Pinging ffxi00.pol.com [124.150.154.122] with 32 bytes of data:

Reply from 124.150.154.122: bytes=32 time=188ms TTL=46
Reply from 124.150.154.122: bytes=32 time=192ms TTL=46
Reply from 124.150.154.122: bytes=32 time=183ms TTL=46
Reply from 124.150.154.122: bytes=32 time=184ms TTL=46

Ping statistics for 124.150.154.122:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 183ms, Maximum = 192ms, Average = 186ms

Also note the round trip times there as well.... that's a total of 19 hops, (16 off my local network segments) and the RTT is still under 200 ms...if your lag is higher, you could have even more hops.