Bad server name. Unknown reason.

[creiss]

Yes I can understand that.

But I doubt i can use the LoginServer (public) for my setup, can I?

-Chris.

Sure can, when the server is locked only people with GM access can get in.

So bring it up locked and only you can get in.

[creiss]

Just to be clear:

My server has NO external IP. It would report to your login server as 10.0.0.13 - all skill cool?

If yes, all my problems just vannished

-Chris.

[John Adams]

You have no internet access?

If that's the case, then no. You cannot use eqemulator.net:5998 as a login server, and must use minilogin.exe.

Sorry, I gave all the info I know on how to make it work. As stated, my setup is spread over 3 machines, all of differing OS's, and mine works flawlessly. No public IP, no external access - all internal (192.168.x.x network).

I wish you luck.

[creiss]

Poor choice of words. Loss of precision.

I meant: There is no way for anyone from the internet to connect to my server, there is NO WAY to it. The server, however, CAN, dial out. As can any other PC on this lan.

I also thank you for your configuration, and even a 1:1 (except modified ips) will result in the bad server name error message. Whoever has the code of miniLogin please have a look at the source and debug it, tell us what actually throws this message, and how I can avoid it - thanks

Debugging a blackbox (closed source) without proper (or any) documentation on error(!) messages is always hard. :P

-Chris.

[LostZaphod]

Some use wine to run minilogin.exe on the unix box, though i think you have to have a graphic desktop installed.
I bet your real issue is related to tcp/ip port blocking, as John's config works. Check your unix and Microsoft box's
and make sure the ports are open (Firewall's turned off etc..).

These are the port's i know of...
5999 (minilogin)
3306 (mysql)
7000-8000 (zone's)
9000 (world)
9080 (world)(html admin pages)

[Angelox]

I run wine minilogin all the time - runs just as good under Linux - graphical or not.
But the catch is, you can't use wine for anything else , because when it's kill time, you have to really "murder" wine, else the wineserver won't let loose minilogin port. when you restart, there'll be no minilogin.
Here's my "hackish" approach, and it works fine;
startup;

#!/bin/sh
wine MiniLogin.exe > logs/MiniLogin.log &
P=`pwd` 
export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:$P"
#make sure we have a place to log
mkdir -p logs 2>&1 > /dev/null 

#boot up world
if [ ! -e .lock-world ] ; then 
	    touch .lock-world 
	    ./world & 
	    # wait for shared memory to load
	    sleep 20 
fi 
#start up the official launcher
if [ ! -e .lock-launcher ]; then
	    touch .lock-launcher
	    ./eqlaunch zones &
	    sleep 80
fi

stop;

#!/bin/sh 

killall wine MiniLogin.exe world eqlaunch zone wineserver wine-preloader
sleep 3

if ps ax|grep -e 'w[o]rld' -e 'z[o]ne' -e 'eq[l]aunch' >/dev/null; then
	            killall -9 world eqlaunch zone
	            sleep 2
fi

./cleanipc 
rm -f .lock-zones .lock-world .lock-login .lock-launcher 

sleep 3
killall wine-preloader
sleep 3
killall wine-preloader
sleep 3
killall wine-preloader #wine-preloader never makes it to the third one :)