login Server can not register more than one server?
I have multiple IP addresses, so I put them are used up, the system is proxmox, I establish a server and login server, normal operation and at the same time eqemulator my local login server registration, when I run a second EMU server, registered to the local login server, server list shows two servers, but the landing to go is the second server, the first server do not know where to go, this is why? The login server cannot support multiple local server registration? (I'm sure the IP address of the 2 server has been set up correctly.)
pls help me~ Some people can provide help, thank you very much! |
Is this correct?
You are running 1 world server which connects two 2 login servers (public LS and a local LS). The local LS is running on the same IP as the world server. |
Nah 2 worlds connecting to 1 login is what hes doing.
|
I tried that once, just piddling around with two boxes on private lan, with one login,
but router only let me forward the necessary ports to one box, so that didn't pan out. |
Quote:
Quote:
|
Quote:
|
this isn't very clear you quote the guy who says you are trying to run 1 world server for 2 login servers, but you mention your original problem being 2 worlds connecting to one login server, where the world servers reside on the same box.
2 world servers on the same box.. routing is the first problem, you sure UDP is using the right interface going out of your box? The logic for the 'resolved' IP/hostname on the login server typically fell to the 'worldaddress' field in eqemu_config.xml -- if you don't provide the worldaddress, the login server will guess based on what you connect with (hence routing). |
Quote:
No.1 EMU server and local Login Server in VM1 No.2 EMU server in VM2. VM Host VM1 VM2 Are using different Internet IP address。 VM Host IP address : XXX.XXX.253.2 VM1 IP address : XXX.XXX.253.3 eqemu_config.xml Quote:
Quote:
eqemu_config.xml Quote:
|
so again your eqemu_config.xml doesn't contain a worldaddress, it should be below localaddress in most cases
<localaddress>...</localaddress> <worldaddress>..</worldaddress> worldaddress should be the external IP that you have out to the web. See if defining those in both EMU servers helps. If not you probably have to consider getting packet captures so people can see the activity going to/from port 9000 on the client. |
Quote:
|
Quote:
|
All times are GMT -4. The time now is 02:21 PM. |
Powered by vBulletin®, Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.