Crashing to char select during zoning on AB.

[Xethren]

<p>This happens about a third of the time I zone during play. I two box on the same machine and it's only been happening for the past week or so.</p>

[TSR-DanielH]

<p>A crash to character select like the one you're reporting is usually caused by a port issue with the router.  I would advise bypassing your router and plugging your computer directly into the modem as a first step.  If you try that and it corrects your issue then you'll need to configure your router if you wish to continue using it.The following site has great information about router configuration:<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>

[Xethren]

<p>Im a bit confused by the website, It doesnt list the D Link DIR-600 so i went with the 615.</p><p>I didnt know which ports to put where under TCP or UCP so i followed the example, which was only for the first three sets, so I have my ports set up like</p><p>TCP -> 7000, 7010, 9700-9703, 32800-33000</p><p>UCP -> 3016-3021, 9100</p><p>Is this correct? My ping still tends to fluctuate between 100 and 400.</p>

[TSR-DanielH]

<p><cite>Xethren@Antonia Bayle wrote:</cite></p><blockquote><p>Im a bit confused by the website, It doesnt list the D Link DIR-600 so i went with the 615.</p><p>I didnt know which ports to put where under TCP or UCP so i followed the example, which was only for the first three sets, so I have my ports set up like</p><p>TCP -> 7000, 7010, 9700-9703, 32800-33000</p><p>UCP -> 3016-3021, 9100</p><p>Is this correct? My ping still tends to fluctuate between 100 and 400.</p></blockquote><p>Small correction: 32800-33000 is also UDP.  I have included the full list of port info below:</p><p>EverQuest II LaunchPad and Patch Servers A TCP connection is initiated from the LaunchPad client port > 1023 to patch.station.sony.com port 7000. A UDP connection is initiated from the LaunchPad client port > 1023 to sdlaunchpad1.station.sony.com and sdlaunchpad2.station.sony.com port range 3016-3021 and 9700-9703.EverQuest II Patch:A TCP connection is initiated from the EverQuest II client port > 1023 to patch.everquest2.com, abepatch.everquest2.com, laepatch.everquest2.com, or amspatch.everquest2.com at port 7010. Some of the above patchers resolve to multiple IP addresses, so if you have a strict outbound firewalling policy, be sure to check for all IP addresses using a DNS lookup tool.EverQuest II Game Client:UDP connections are initiated from the EverQuest II client port >1023 to servers on UDP ports 9100, and UDP ports in the range 32800-33000. Additionally, ICMP messages type 0 (echo reply), 3 (unreachable), 8 (echo request) and 11 (expired) should be permitted bi-directionally between the client PC and the EverQuest II servers.EverQuest II Servers Subnets:There are multiple IP addresses for the Patch and LaunchPad clusters, and they may change as the network demands, so check often using a DNS lookup tool if you provide a specific firewall rule for these services. The EverQuest II server IP addresses are currently in these subnets: 64.37.158.*, 199.108.11.*, 199.108.12.*, 199.108.13.*, 199.108.202.*, 199.108.203.*, 195.33.135.*</p><p>Did you try simply bypassing the router before attempting to forward ports?  That will tell us whether or not the router is the issue here.</p>