The old stuck at "Receiving Zone info" issue rears its ugly head once again

[Suzail]

<p>Has anyone got any further ideas about this issue?</p><p>I logged on to permafrost last night with no issues. i decided to recall to Neriak and i get bounced to desktop.</p><p>try to log in again and get stuck at "Receiving Zone Info" wait for 10 mins and get bounced to character select.</p><p>log into one of my alts and log in fine. try my main again with the same problem.</p><p>read about the issue here and delete the cache and char settings ini files. </p><p>Still the same issue.</p><p>Log into my partners pc (who also plays EQ2) and exactly the same issue.</p><p>so its not an ini file or a corrupt file on my pc else i would of been able to log in on my partners PC.</p><p>Its not my network connectivity as i can log in with my other characters.</p><p>this leads me to believe that its an issue on either the login server or the server itself. (it wasnt neriak down because some of my guild friends were in neriak when i logged in with an alt)</p><p>PS the GMs were as much use as a chocolate fireguard as all they suggested was that i deleted and repatched.</p><p>HELP! <img src="/smilies/3b63d1616c5dfcf29f8a7a031aaa7cad.gif" border="0" alt="SMILEY" /></p>

[TSR-DanT]

<ul><li>How often does this happen?  </li><li>Is it something you can make happen every time you play?  </li><li>Is the character still stuck or can you log into it now?</li></ul>

[Suzail]

<p>Hi Dan,</p><p>thanks for replying.</p><p>I have a petition running alongside this also.</p><p>yes i can replicate it all the time. I have not been able to log my Necro in since tuesday. I can log all my other characters in and zone with no problems. I have even tried on a different pc. I have also created a new character in the neriak area and can log that in and out with no issues. I have followed every step asked of my by GMs and TSR staff and still have the same issue. Im hoping the eq2info file that i emailed accross will help.</p>

[TSR-DanT]

Ask them to try logging in on the character.  It's possible this could be a broken character, and if we cannot log in on our side, we can confirm this and send it over to be fixed.Let me know how the ticket goes.