No Response from the FINAL FANTASY XI server

[Kayn]

connection timed out.

followed by error Code POL-0250 No response from the server.

this started last thursday, many people are having issues like this, for some it just goes away, it is not my ISP provider because everything else is all rigth. the most frustrating thing is that i cant stay logged in for more than 2-3 minutes or ill get the red ball of disconnection (but my send and recieve arrows will act as im not disconnecting, and i can still see the ls chat as normal, and some stuff still moves but not all.) and i cant even play with some friends that just joined the game and need help.

hope at least i can get some, "yes we are having issues with the servers right now, we are working on it" out of this, because im 100% shure it is not my ISP.

[RAIST]

check your router and firewall logs--I had this kind of thing happen to me once and found two IP's from SE that were getting blocked:

124.150.152.96
124.150.152.99

Make sure the port forwarding is setup properly if you are using it:
TCP/UDP traffic on ports 25, 80, 110, 443, and 50000-65535
(think port 53 is needed too, for DNS stuff, not sure)

These are IP blocks I've seen leased by SE. If IP's in these ranges are still getting blocked, then
they need to be whitelisted:

202.67.53.0 /24 (202.67.53.1 to 202.67.53.255)
202.67.54.0 /24 (202.67.54.1 to 202.67.54.255)
202.67.62.0 /24 (202.67.62.1 to 202.67.62.255)
124.150.152.0 /24 (124.150.152.0 to 124.150.152.255)

[Kayn]

i have ports forwarded as per a recomendation of an admin in another thread, still no luck. i have never white listed IPs before so i dont really know how to do that. can this happen like out of nowhere? i've played for years and never had any issues before :/

[RAIST]

yes... the 124.xxx.xxx.xxx IP's started showing up after an update around the new year...forget exactly when. Threw my system through a tailspin and I was stuck in a zoning loop at port windurst until I found the blocked IP's (would start zoning on login and then get the failed response from server message and had drop back to the launch screens).

Many home use routers won't allow you to create a whitelist for IP's, so you would probably need to look at your local firewall logs/config first (Windows Firewall, ZoneAlarm, etc.) The first thing to check is your locally installed firewall's log--if it is capturing the IP, than it is getting past your router and is blocked at the PC. If you can't find it at the PC level, then check your Router's log to see if it is getting blocked there. Then you know where you need to unblock the IP and or port. If it is a port not alreay enabled for forwarding, just add that port to the forwarding to see if it resolves it. The log may represent the incoming port ID in different ways--it may be in a seperate colomn, or just be appended to the IP address (124.150.152.96:53 means traffic on port 53 from 124.150.152.96).

Whitelisting is different per firewall, so you will have to poke around your settings for a section allowing you to enable/allow certain sites/IP addresses access and add the IP's--usually it is in an advanced menu so you may not see it until you go into the advanced config section. Sometimes you can allow ranges too.

One of the biggest things that sometimes trips apps up on the home routers is their built-in firewall--so need to rule that out first. You might need to look in the Advanced section under WAN. There may be options to configure SPI Firewall and NAT Filtering. Start with NAT first--change it from secured to open and see if it resolves it. If not, try disabling the next option (may be a check box to disable ALG, SIP, something a long those lines, under the NAT filtering section). If tweaking NAT doesn't resolve it, then look into disabling the router's firewall--MAKE SURE YOU HAVE A LOCAL FIREWALL RUNNING ON YOUR SYSTEM FIRST (Windows firewall, ZoneAlarm, etc--lots of free options out there). You can also try enabling the router to respond to pings also--again, make sure you have a locally installed firewall before disabling the router's security completely.