For those who continue to have issues, have you already tried the port forwarding workaround?
Even FFXI and WoW had this method to get past, er... <cough>.. local issues.
Test it. You may be surprised at the results.
For those who continue to have issues, have you already tried the port forwarding workaround?
Even FFXI and WoW had this method to get past, er... <cough>.. local issues.
Test it. You may be surprised at the results.
Port Forwarding (and DMZ) are ways around the local network firewall/structure. If the port range is limited (or not listening) you can manually forward them outside of the firewall of the router (DMZ allows you to white list a device to operate outside the network firewall/rules completely).For those who continue to have issues, have you already tried the port forwarding workaround?
Even FFXI and WoW had this method to get past, er... <cough>.. local issues.
Test it. You may be surprised at the results.
It doesn't hurt to ensure the port range is forwarded and definitely give it a shot, but most routers will have the range (3000-50000ish I think) already open and listening to host(s) (unless the router is old, there is a dual NAT, firmware is corrupted or bad on the router). You can also try to set a DMZ (USE WITH EXTREME CAUTION AND UNDERSTAND THE RISKS) or static your IP to try to gain favorable LAN related results.
The more efficient you can make the network, the more it works in your favor. QoS, Turning off b/g (if on wifi) and prioritizing your connection (advanced settings on the router) are all good ideas.
For wifi, make sure that you have it so the computer can't turn off the card to save power and make sure that your wifi card is at 100% power as well (Windows 8 users this is very important. I also turn off minimum power consumption to ensure the card is at full draw all the time). When changing settings on your network adapters remember that mileage varies and heat is your worst enemy (specifically laptops/wifi).
I've been troubleshooting since about a week after 2.1 released. My ISP (AT&T U-verse) claims no other users have informed customer care of having issues with this game. I've shown them trace routes detailing most issues going through nodes owned by Cogentco. AT&T U-verse says, if there aren't any other issues with my network (true), there's nothing they can do to help me. SE NA chat support has been helpful in teaching me how to troubleshoot. I didn't know that port forwarding, DMZ mode, or open DNS were real words prior to December. Learning is fun. Google DNS did have some positive results...not enough to make current end game content completely playable, but it's something.
I've said something similar in other posts on this forum (and others): having to constantly troubleshoot, waiting for a patch to magically fix everything, and hounding all forms of customer service to no resolution has nullified the fun I used to have playing this game.
Cogentco is another backbone that has a horrible reputation. I'm pretty sure they let fires rage at their nodes they suck so bad.I've been troubleshooting since about a week after 2.1 released. My ISP (AT&T U-verse) claims no other users have informed customer care of having issues with this game. I've shown them trace routes detailing most issues going through nodes owned by Cogentco. AT&T U-verse says, if there aren't any other issues with my network (true), there's nothing they can do to help me. SE NA chat support has been helpful in teaching me how to troubleshoot. I didn't know that port forwarding, DMZ mode, or open DNS were real words prior to December. Learning is fun. Google DNS did have some positive results...not enough to make current end game content completely playable, but it's something.
Yeah, I hate calling ISP's. 90% of the people you talk to have no idea what's going on. If I have to talk to my ISP, I will bomb the CS rep with jargon and raw information till they send me to T2 where I'll do the same till I get to Engineering. They can change (called prioritization) your route path to avoid crappy backbones. No one likes to do it and they DEFINITELY don't talk about it (they don't want to be bombed with requests and put load on another backbone that's probably reserved for commercial/VIP tier clients). Essentially, you need to get into contact with at least entry level Engineering Support. There, they should know enough to understand what you're saying and put the W/O in.
I LOLd so hard at the fires bit. Ty for that.Cogentco is another backbone that has a horrible reputation. I'm pretty sure they let fires rage at their nodes they suck so bad.
Yeah, I hate calling ISP's. 90% of the people you talk to have no idea what's going on. If I have to talk to my ISP, I will bomb the CS rep with jargon and raw information till they send me to T2 where I'll do the same till I get to Engineering. They can change (called prioritization) your route path to avoid crappy backbones.I'm pretty sure I'll never be able to talk to Engineering. Most CS reps at U-verse want me to pay $15 a month extra to go through Connectech, claiming that's the highest tier of customer support they offer. Uhm...no. Unfortunately, I can unsub from this game a lot easier than getting out of a contract with AT&T. Bigger unfortunate is that the only other broadband ISP in my area is notoriously worse than AT&T.
I've dealt with AT&T over their network routes before (lolMaBell freaking monopoly to this day) and they are a pain to convince it's their bad (excel sheets GB's large. traceroute -n <IP> for DAYS). You can ask them to open up a trouble ticket and send it to their applications support team (Engineering) for back end review. Make sure the CS rep notates exactly what's going on, what you want, what your expectations are, your contact information, and data to corroborate your issue if need be.I LOLd so hard at the fires bit. Ty for that.I'm pretty sure I'll never be able to talk to Engineering. Most CS reps at U-verse want me to pay $15 a month extra to go through Connectech, claiming that's the highest tier of customer support they offer. Uhm...no. Unfortunately, I can unsub from this game a lot easier than getting out of a contract with AT&T. Bigger unfortunate is that the only other broadband ISP in my area is notoriously worse than AT&T.
When I have to call Rackspace (UGHHHHHHHHH you think Square is bad call Rackspace. Makes Square look like UNICEF) I usually have all the data compiled and available to be reviewed and sent. I'm also firm about what I'm requesting but not aggressive. Having a cool CS rep goes a long way in getting issues resolved. It's been my experience that if you're pissed and it flows over to the CS rep, odds are that ticket will get created under "Administrative" "Historical Reference" and closed out.
|
![]() |
![]() |
![]() |
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.