An error has occured on the game server. (30002)

[Grit]

Hey!!! Didn't realize that you had replied!

Needless to say I get dumped (dc'd) so frequently it's becoming almost a deal breaker /cry.

But here is the info...

Background
Platform: Laptop running Windows7 64 bit, NVIDIA 280M, 4gig ram
ISP: Charter
Type of Internet Connection: Cable @ 16MBPS but on my Wireless G Linksys
Date & Time: Weekdays starting at 9PM - 11PM
Character Name: Neo Earth
Race: Hylander
World: Wutai
Class/Skill Rank: 38 MRD
Physical Level: I think it's 33

Symptoms
Almost always crashes with a minute of first logging in. During leaves, behest, running about... I get a crash no matter what I am doing. In fact it crashed last night about 5 times before i gave up. After this occurs It dumps me out to select a character. I do... and it crashes again. At this point it drops me into the initial ffxiv screen and if i log in... it crashes. Bottom line, if it crashes at all, i have to close the client completely before I can attempt a re-connect.

Having said this... i hope there is some way to figure this out cuz I love the game and looking to stick it out.

Is there ANYTHING i can look up, do etc...? I'm a software dev so don't be afraid to ask the tech details or to find some crazy log file.

Having a wireless connection can make a world of difference when it comes to diagnosing this problem.

Go into your network adapter settings and check if you have more than one preferred network. If you have two active preferred networks, your computer may be trying to grab DHCP addresses from both, causing connection problems in FFXIV.

If you have more than one network in range, make sure that "Connect when in range of this network automatically" is unchecked on the one that you aren't using.

If you only have one network in range, then it's back to the drawing board. This solution is mostly a shot in the dark.

You can also try connecting your computer directly to your modem, instead of going through a wireless access point. If this corrects the problem, then it lies somewhere in your wireless configuration.