connection error

[vales]

<?xml version="1.0">
<server>
        <world>
                <shortname>minilogin</shortname>
                <longname>My Minilogin</longname>
                
                <!-- Only specify these two if you really think you need to. -->
		<address>127.0.0.1</address>
		<localaddress>127.0.0.1</localaddress>
		
		<!-- Loginserver information.  -->
        <loginserver>
		<host>192.168.1.4</host>
		<port>5999</port>
		<account></account>
		<password></password>
        </loginserver>

                <!-- Sets the shared key used by zone/launcher to connect to world -->
                <key>some long random string</key>

                <!-- Enable and set the port for the HTTP service. -->
                <http port="9080" enabled="true" mimefile="mime.types" />
        </world>

                <!-- Database configuration, replaces db.ini. -->
        <database>
                <host>127.0.0.1</host>
                <port>3306</port>
                <username>eq</username>
                <password>eq</password>
                <db>eq</db>
        </database>
</server>

###Your current configuration is as follows:

loginserver.ini:
[LoginServer]
loginserver=192.168.1.4
loginport=5999
worldname=My Minilogin
worldaddress=192.168.1.4
locked=false
account=
password=

[WorldServer]
Defaultstatus=
Unavailzone=
[ChatChannelServer]

worldshortname=
chataddress=
chatport=

[LoginConfig]
ServerMode=Minilogin
ServerPort=5999

Try that I guess. If not, then I'm all out of ideas. I'm thinking it could be just your setup. I'm sure somewhere along the way, you messed something up. There shouldn't be any reason why you can't connect if you say you've done all you posted and still can't connect.

1.) Revert everything, and I mean everything. HOSTS file, router ports, uninstall MySQL, Perl, etc. - just get rid of it all and delete all the folders it leaves behind. Then re-install it step by step again.

OR

2.) Try making a public server and see if you can log in with that. Make yourself a login account from here and test it. If you can run the server on a different PC and still connect to it via Public Login, then that narrows down the issue if it being a faulty install. Then all you have to do is fix the port numbers instead of doing all of this no-ip crap.

I think by you trying "everything" really screws up more than fixing it. Just keep it simple and try to approach it slow.