Can't zone into BoT. Any ideas?

[Aeniec]

As title states, I can't zone into BoT. I was able to zone in 1 time on my 'box' client but since then I can't zone back in. When I was in BoT on my alt - I could walk around and see guildies killing stuff / etc. ISP crashed for a few hours and upon coming back, I can't zone in.

Here is what I've tried so far to fix the problem - along with the number of times I've tried it:

Copying Bot files from 'box' to 'main' x5 (last 3 included reboots)
Copying all files and folders from 'box' to 'main' x1
Redownloading UF missing files from hateborne.com and reinstalling x2

I really don't know what to do? Any ideas? The fact that I could actually zone in 1 time on my 'box' client but never on my 'main' has thrown me for a complete loop.

-Xalle

[Noren]

The last time I heard about something like this, my guildy and I narrowed it down to the port being used for the zone conflicting with his ISP. As far as I understand it, each zone receives a randomized port #. For static zones (BoT) a new port # is issued upon every reboot. (I may be confusing the terminology of static/dynamic zones, because I recall there is a distinct difference between dynamic and instanced but it escapes me right now).

How does this pertain to you?
1) It could be your router or firewall (although I doubt it). If this were the case, you can disable your firewall and bypass your router by connecting directly to the cable/dsl/fibre modem.

2) It could be totally out of your hands. Your ISP may block traffic along certain ports for whatever reason they may have... and if that were the case, then you're SoL. Nothing you can do about that but wait until the next server reboot when Bastion of Thunder is assigned a new port. If you want to confirm that this is the case, then try another internet connection. Hotspot through your phone or, if you're portable, head somewhere with a different ISP and see if you have better results.

You've done everything that can be done with your local game files, afaik, so it all comes down to connecting with the server. Everquest/logs/dbg.txt should hold some enlightening details about your failed connection to Bastion of Thunder. If you're unfamiliar with the log file and confused by the mass of text in there, simply delete it and then try to zone into BoT. It will create a fresh new log, in which BoT errors should be at the very top.

Hope that helps.