Zone crashing and other such wonderful stuff

[N3xus0n3]

<p>Whilst playing Eq2 today I had both of my clients crash on zoning with the same error.</p><p><em>Everquest II has detected an unrecoverable error and must shutdown.</em><em><verify> E:liveeq2gameclientsrcClientNet.cpp (635):m_pCon->GetStatus() == UdpLibrary::UdpConnection::cStatusConnected 0034375dd 00000003</em></p><p>This is the error, which I had two PC's at the same time. I have googled to no avial and have spoken to my ISP about the zoning issue and they can't seem to help as nothing untoward happens to my connection at the time.</p><p>I have been loathe to post as I have never really had any issues before with EQ2 and generally the slight issues I have had have been resolved after a few of the little bugfixes after a big patch. However, this seems like I've a problem somewhere and I could do with a clue or two to point me in the right direction.</p><p>Thanks.</p>

[TSR-DanielH]

<p><cite>N3xus0n3 wrote:</cite></p><blockquote><p>Whilst playing Eq2 today I had both of my clients crash on zoning with the same error.</p><p><em>Everquest II has detected an unrecoverable error and must shutdown.</em><em> E:liveeq2gameclientsrcClientNet.cpp (635):m_pCon->GetStatus() == UdpLibrary::UdpConnection::cStatusConnected 0034375dd 00000003</em></p><p>This is the error, which I had two PC's at the same time. I have googled to no avial and have spoken to my ISP about the zoning issue and they can't seem to help as nothing untoward happens to my connection at the time.</p><p>I have been loathe to post as I have never really had any issues before with EQ2 and generally the slight issues I have had have been resolved after a few of the little bugfixes after a big patch. However, this seems like I've a problem somewhere and I could do with a clue or two to point me in the right direction.</p><p>Thanks.</p></blockquote><p>It looks like it lost connection to our servers in an unusualy way.  Were you able to log in with those charcters afterwards?  How about different characters on the same accounts?</p><p>The fact that this is happening to 2 computers at once is very strange.  Do you have similar hardware/drivers on both machines?</p>

[N3xus0n3]

<p>Nope, no similar hardware in either PC. Which leads me to think that it's either my network connection or my router. But that crash is peculiar.</p><p>And to answer your questions. Once I had rebooted EQ2 all was fine again, until the next time we zoned. No issues logging in with characters.</p>

[TSR-DanielH]

<p><cite>N3xus0n3 wrote:</cite></p><blockquote><p>Nope, no similar hardware in either PC. Which leads me to think that it's either my network connection or my router. But that crash is peculiar.</p><p>And to answer your questions. Once I had rebooted EQ2 all was fine again, until the next time we zoned. No issues logging in with characters.</p></blockquote><p>Have you tried bypassing the router and power cycling your modem?  Those 2 items seem to be the only common link so it would be worth trying.</p>

[N3xus0n3]

<p>Modem router. I've had the same one for a while and never experienced any issues with it before. Yes, I have tried rebooting it. Quite a few times. This issue doesn't go away. Perhaps if someone could translate the code for me I could get a better clue of where to look?</p>

[TSR-DanielH]

<p><cite>N3xus0n3 wrote:</cite></p><blockquote><p> Perhaps if someone could translate the code for me I could get a better clue of where to look?</p></blockquote><p>The UDP being referenced in the error is part of the port structure used by the game to connect.  If it's a modem/router then you may need to set it up for port forwarding in order to proceed.The following site has great information about router configuration:</p><p><a href="http://www.portforward.com/english/routers/port_forwarding/routerindex.htm" target="_blank" rel="nofollow">http://www.portforward.com/english/...routerindex.htm</a>Simply select the router you are using, then select the 'skip this advertisement' button in the upper right, and finally select Everquest 2 on the following page.  You will then be presented with a walkthrough on how to forward the correct ports.  Please respond if you need any further assistance.</p>

[N3xus0n3]

<p><cite>TSR-DanielH wrote:</cite></p><blockquote><p><cite>N3xus0n3 wrote:</cite></p><blockquote><p> Perhaps if someone could translate the code for me I could get a better clue of where to look?</p></blockquote><p>The UDP being referenced in the error is part of the port structure used by the game to connect.  If it's a modem/router then you may need to set it up for port forwarding in order to proceed.The following site has great information about router configuration:</p><p><a rel="nofollow" href="http://www.portforward.com/english/routers/port_forwarding/routerindex.htm" target="_blank">http://www.portforward.com/english/...routerindex.htm</a>Simply select the router you are using, then select the 'skip this advertisement' button in the upper right, and finally select Everquest 2 on the following page.  You will then be presented with a walkthrough on how to forward the correct ports.  Please respond if you need any further assistance.</p></blockquote><p>As I specified at the beginning of my post, there are two PC's involved. It isn't possible to port forward to two seperate PCs.....</p>

[N3xus0n3]

<p><strong>RESOLVED</strong></p><p>And we shall use the following words here so if anyone searches a similar problem they can solve it.</p><p>Netgear DG834 Everquest 2 zoning crash. EQ2 <strong>DG834 v2</strong> modem router issue.</p><p>This issue is caused because netgears latest firmware version apparently causes the DG834 v2 to act as a hub rather than a switch. Although I don't fully understand how the problem manifested itself in this instance I would suggest that perhaps the transfer between the intelligent switch and the dumb hub caused timeout issues when making the initial connection to a zone server, but that would be for more technical people than myself to decide.</p><p>This is resolved by rolling your modem drivers back to a previous version. I am now using version 105 with no issues.</p>

[TSR-DanielH]

<p><cite>N3xus0n3 wrote:</cite></p><blockquote><p><strong>RESOLVED</strong></p></blockquote><p>I'm happy to hear that you resolved the issue and it's interesting that the netgear firmware would do that.  Thank you for posting that information.</p>