below is the firewall details, could someone with the relevant knowledge please translate this into ISA Rules??
EverQuest II LaunchPad and Patch Servers A 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.
EverQuest II Patch:
A TCP connection is initiated from the EverQuest II client port > 1023 to patch.everquest2.com, ablpatch.everquest2.com, abepatch.everquest2.com, or rrpatch.everquest2.com at port 7010
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.13.*, 199.108.12.*, 199.108.202.*, 199.108.203.*, 195.33.135.*
Bear with me...I got it figured out during the work week and plan on posting it today sometime. The key is that most everything maps right to protocol rules, but the port range 32800-33000 should be included as a secondary connection port range to the 9100 UDP connection.
The 32800-33000 port range is what EQ2 uses to connect to the individual areas of the game and there seems to be an affinity of ports mapping to specific areas. I was creating protocol rules for each port number to connect on and finding that once a protocol/port was configured for a particular area (based on the last port connection EQ2 makes in the FW logs) you could always go there. Basically you could open up the whole game by checking the logs when you failed to go to an area and open up the port for that area which allows you to always go there...until you had a protocol definition for every port in the range 32800-33000!
I figured there had to be a better way, so I looked in the logs to see what the last port connection before the failed one was, and set the 32800-33000 range as secondary connections and I'm now going smoothly from area to area.