Do you have any other PCs in your 192.168.2.x network that you could try connecting to your test server from? That will verify that it at least works for connecting as it will bypass any port or routing issues from the external network as it connects locally.
I have never tried a dual NIC and dual ISP setup for EQEmu, so I am not completely sure what other problems that might cause that could be different than the standard ones.
With your 2 LANs being in separate IP space now, that should reduce some potential routing issues. I am just not sure how the server decides which NIC to use offhand. I assume it would just be listening on port 9000 for any connection to come in and when one does, it would just reply through the same NIC it came from. It sounds like it could be getting confused on which NIC to use. Did you try disabling your other NIC yet to see what happens?
Having a DMZ set on your test server's network could definitely cause some issues. That is basically like having all ports forwarded to 1 IP, so if the IP for the DMZ was pointing to somewhere other than your test server, it would probably override your port range forwarding settings and cause connections to fail.
Since you have a special network setup, you may be one of those special cases that does require those IP fields to be set in your config. Everything looks correct as far as I can tell.
What I don't get is that you said some users can connect and others cannot. If even 1 person can connect, all should be able to. If they aren't, maybe it is something on their end or something else with the setup on your server. Maybe I can try connecting when you have it set the way you did and see what the sniffer shows if I fail to connect.
|
Hybrid Mode
