Well, LAN setups can sometimes be harder to configure properly than Public ones. The hard part is this part of your config:
Code:
<!-- Only specify these two if you really think you need to. -->
<address>localhost</address>
<localaddress>192.168.1.109</localaddress>
On a public server, you wouldn't even set that at all, you would leave that section commented out.
Here is what I set mine to for my test LAN server:
Code:
<!-- Only specify these two if you really think you need to. -->
<address>192.168.1.102</address>
<localaddress>127.0.0.1</localaddress>
Mine probably isn't standard though, because I run my server on VMWare in Linux and it connects to my main PC running windows where the minilogin is running. Someone more familiar with minilogin setups is probably going to need to help you with that.
And, if the repack setup has some different special launcher, then that is probably why you are having a problem. I see a ton of zone launching in your server log and you don't have hardly any configured in your launcher_zones table. You need to put each zone you are launching in your launcher zones table to match your launcher program, or the server won't know where to send you. Maybe try setting them all to dynamics and remove all of the static stuff you have set until you can get that working. Your tables and launcher program have to match perfectly, which is probably your main issue atm.
Threaded Mode
