Can connect to other DR4 servers, but not mine
 

I've compiled the 5/29/04 DR4 release from biosprite. World and boot5zones start fine, with no item errors, etc. I can see my server at the server selection screen. When I try to connect to it, the screen goes black (like it normally does), then I hear HD activity (like it normally does), but after about 3 seconds, I end up back at login. I don't get a 1017 error (if I do, I don't see it). I can log in to other people's DR4 servers. I don't know if anyone else can log into my server. I've searched for this error, but the closest thing I've seen to my situation is when people crash out to desktop, or get stuck at character creation, and I'm not having either of those problems (right now at least).

Post the outputs you get form world.exe and all the zone servers so we can see what the problem might be.

Sorry to waste time again, as I found the error shortly after posting.

I didn't have the correct external IP (forgot to update it to match ISP's new assignment).

I am in my world now (for better or worse =)

Come join me in a bit once I tweak the db.

whats your servers name?

"sianyde", but I've fixed the problem, thanks. You're most welcome to come on in if you want, but I just put it up, and targetting still isn't working right.

so how did you fix it.. I am unable to log into my server but I can log into other dr4 servers..

Well, my problem was that I was working behind a router. I used the EqEmu server guide to fix it. I signed up for a domain at no-ip.com. In my loginserver.ini, I used the domain name I chose for the variable "worldserver" and "chatchannelserver". I especially needed to assign "chatchannelserver" a value to get this work.

In boot5zones.bat, I also used the domain name. The lines in my boot5zones.bat look like this:

start zone . mydomain.org 7995 192.168.2.103

where 192.168.2.103 is the interal (assigned by router) address of my machine that is running world.exe and zone.exe.

Just remember to update your external IP (the one your ISP assigns) with the domain name provider, or d/l a utility that does it automatically.

Again, I had to do this b/c my machines are behind a rotuer, and I couldn't accomplish the goal by DMZ'ing a machine (either my router or myself can't figure it out, probably the latter).