Got a new modem and can't stay in game

[Chaos523]

I've literally been at this for the last 5 hours.  I've been searching everywhere,  Portforward.com and other sites.  I had no problems before we switched to a new wireless modem.  Now I can log in just fine but once in I will sometimes appear w/o any health or power and sometime I will have health and power but I can never interact with the environment.  I can stay logged in for about a minute before getting dumped to the character select.  I've logged in on characters on other servers and get the same thing.I've forwarded every port I can find posted that belongs to EQ2 and I get the same problems.  I can play other online games no problem it's just EQ2.The modem is a thomson dcw725 if it matters.  Nothing else has changed with the system.  I'm at wits end, have had a real bad day and just want to play some EQ.

[Chaos523]

Ok, I did fix it last night.  It wasn't the forwarding it was the firewall, if it's turned off it works fine.  Just not too high on keeping it off while I play.  Anyone know of a way around this w/o disabling the firewall?

[Wingrider01]

<cite>Chaos523 wrote:</cite><blockquote>Ok, I did fix it last night.  It wasn't the forwarding it was the firewall, if it's turned off it works fine.  Just not too high on keeping it off while I play.  Anyone know of a way around this w/o disabling the firewall?</blockquote><p>If I found the right manual, take a look at page 40 concerning port triggers</p><p>from the knowledge base</p><p><b>EverQuest</b> II LaunchPad and Patch ServersA TCP connection is initiated from the LaunchPad client port > 1023 to patch.station.sony.com at 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. <b>EverQuest</b> II Patch: A TCP connection is initiated from the <b>EverQuest</b> II client port > 1023 to patch.everquest2.com, ablpatch.everquest2.com, abepatch.everquest2.com, or rrpatch.everquest2.com at port 7010<b>Everquest</b> II Game ClientUDP connections are initiated from the <b>EverQuest</b> 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 <b>EverQuest</b> II servers. </p>

[Chaos523]

I've also found that I can turn off the firewall to get in game and then turn it back on right after and I'm fine to play as long as I like.

[Wingrider01]

<cite>Chaos523 wrote:</cite><blockquote>I've also found that I can turn off the firewall to get in game and then turn it back on right after and I'm fine to play as long as I like.</blockquote>That is a work around, setting up the port triggering correctly on the modem's firewall will allow you to keep the firewall active and play the game. Drawback with your method is one night you may forget to turn the firewall back on after you stop playing, in addition it opens up any other machine that is on the network while you are playing.

[Chaos523]

It's off for not even a minute.  I turn it off right before I hit "play" and turn it back on right after I'm in the game and it's smooth sailing.