Server will not support more than one client at a time

[Jolrak]

still having problems with this, my server name is questionable methods...if someone would please try and join this it would be much appreciated. i think it must be something simple, my server is running win 2000 pro with no firewall.

[EvoZak]

I have a similar problem with my setup. If I'm connected to my server (which is on my lan), external people couldn't connect... they got a "unknown error". However if I log off, external people connect just fine and then I can connect as well.

I'm not running any minilogin stuff, just the latest build with the bots enabled and PEQ db. No errors of any kind were in the logs.

[Congdar]

I don't know if this is the same issue as you have, but I found that if I only have one dynamic zone running then I can only have one connection and I can't zone to another zone and I can't log in any other accounts.
Make sure you have 5 or 6 dynamic zones running.

[Jolrak]

i have 5 dynamic zones running.

[Jolrak]

still havent figured it out. tried running a client on same machine as server and same result. server will only support 1 client at a time.

[Cripp]

you may have to use a dns name for the server address and on each machine locally ur using to login u add a line in the hosts file (C:\windows\system32\drivers\etc\hosts) that looks like

192.168.0.2 host.whatever.com

where 192.168.0.2 is the server local IP. you can setup a dns name at www.no-ip.com
in your eqemu_config.xml you need to add the <address> and <localaddress> lines right below the short/long names.. in the <world> section.
<address> would have the dns name and <localaddress> would have the internal IP... after you set all of this hopefuly it will work

PS: the dns name should be setuip to use your external IP not internal.

[quadroplex]

you should also check the wiki for the router/NAT fix for windows servers also you will need to set it up to use your EXTERNAL ip address, or a dns name. you are using your INTERNAL ip address (192,168.x.x) your external IP Can be gotten at whatismyip.com

Also make sure that your firewall and router has the port forwarding for the server ports 9000 - 9080 and 7000-7100 open in the firewal and forwarded to the correct machine on your lan or noone can connect to it outside your lan.

Also check your variables table, the logintype variable, to make sure that it is set to public and not minilogin.

[trevius]

If what crip recommends doesn't work, maybe you can help identify the problem by explaining in more detail how your network is setup.

I suspect it is either your network, or just windows 2000. I know servers run fine on XP, Linux and Windows Server 2003, but I am not sure if they are ok on 2000 or not.

So, if I understand you correctly;

Your server is connected to a plain modem that connects directly to the internet. This modem does NOT have a built in router or anything other than just being a modem?

THEN, you also have a separate NIC card on your server PC too allow it to have LAN connectivity and maybe even share the internet through your server?

Finally, you have a completely separate internet connection in your house that has a router connected to it and your brother uses that to connect to your server without going over any sort of LAN connection?

If my understanding is half-right, no wonder you have connection problems lol. Sounds like a Frankenstein of a network there!