POL 1363 Error

[DarkPrince187]

Since Tuesday night, I haven't been able to get into FFXI (Odin) because of a 1363 error at startup. A couple guys I play in groups with have had the same issue using different ISPs. I called my ISP, they blamed it on SE; SE did the same about my ISP. It's pretty frustrating when the only thing that works on FFXI is the billing (received notice of the bill today). Platform is Windows with 10 MBps connection speed through Madison Telecommunications.

Please help me fix this error.

[RAIST]

Vague communication error---could be something local, but most the time this is due to a network segment in between timing out. Verify your routing is configured optimally for FFXI (port forwarding rules, or test by connecting directly to your router/modem, to bypass the need for forwarding etc.), double check the logs for your security software/devices to make sure they aren't tripping something up when you are logging in (firewall, virus scan, internet security suites, etc.--if using a router, check it's logs as well as many have built-in security that is on strong settings by default).

If all that checks out, you may need to run tracerts to find the point of failure and forward that info to your ISP so they can investigate/take action. Ideally, you'd want to do it to the servers your client is trying to connect with during login (have to run something like netstat or TCPView in the background to see them)--but you may get what you need trying to hit some of the known servers for FFXI. Here are a few you can try:

square-enix.com 202.67.53.202
SE DNS servers (dns1-dns4): 202.67.53.31, 202.67.53.95, 202.67.53.32, 202.67.53.96)
***note the 202.67.53.xxx subnet may be entirely owned by SE, I have not verified this though)

ffxi00.pol.com 124.150.154.122
c000.pol.com 202.67.54.52

If you aren't familiar with tracert and such, you can try forwarding these to your ISP and they should be able to terminal into your modem and do it themselves.

[DarkPrince187]

Talked to a rep from my ISP tonight (he came to the house), and they are determined it isn't on this end. Everything else on the 'net works. I've rebooted computer, modem, and router. 3 full days since I've been able to log in with no other changes to anything else. Used wireless connection first, then hard-wired. Also tried multiple computers. Friends of mine who also play are having the same problem on Odin using different ISPs. Cricket Broadband, Charter, and U-Verse ISPs had the same login issue.

Square did try, I will give them credit for that. But it's real fun paying for a service that I can't use.

[RAIST]

Talked to a rep from my ISP tonight (he came to the house), and they are determined it isn't on this end. Everything else on the 'net works. I've rebooted computer, modem, and router. 3 full days since I've been able to log in with no other changes to anything else. Used wireless connection first, then hard-wired. Also tried multiple computers. Friends of mine who also play are having the same problem on Odin using different ISPs. Cricket Broadband, Charter, and U-Verse ISPs had the same login issue.

Square did try, I will give them credit for that. But it's real fun paying for a service that I can't use.

Often times, these are regional issues caused by a junction servicing that region having issues. It is not SE, and not you---may not be either of your ISP's, but it may be another company's segment at fault. Case in point, the fairly recent thread with issues in the UK of BT/O2 users, that was caused by an issue with the link to BE's segment:
http://forum.square-enix.com/ffxi/threads/22550-POL-Error-Code-0011-3001.-WTF

After a long time of outages, someone finally got them to fess up to what the issue was:
http://forum.square-enix.com/ffxi/threads/22550-POL-Error-Code-0011-3001.-WTF?p=308758&viewfull=1#post308758

just a update

From BE Staff earlier today
Hello everyone,
As many of you know, some customers are still unable to access certain websites. This has been caused by a problem at one of the third party peering platforms we use to route traffic across the internet. Although our partner is working to fix the problem, to enable customers to reach these websites we are putting in place a temporary solution which we hope will fix most, if not all of the problems. We’re sorry for the time it has taken us to get on top of these problems, and for the lack of communication since they began. We really hope to have service back to normal shortly.


And magically O2 say they have "tweaked" it? yeah right lol well happy your all online again

Just know it wasnot the doing of O2 at all but the doing of BE.

Have any traces been run to the actual SE servers that you are trying to connect to to find the downed hops? You can have dozens of hops before you get to SE--any one could be stalling in route to the loby server. Someone has to actually trace the rout to pinpoint the stalling point, then go to whoever is responsible for managing that segment to resolve it. When it last happened to me, it was routing through Nova Scotia, and once before it was an issue with Verizon in Virginia---I live in the southeast and use cable, not FIOS.

[DarkPrince187]

RAIST, you've been quite helpful. Still ticked off that the billing goes through just fine. (insert sarcastic tone here). Can't really think of anything else to do besides what's been suggested.