[Solved] What ports to open [Not sure how or why]
I've read every post I could find, going back to 2004 or so using search engines, about which ports to open. My server runs and connects with no firewall running; however, when I enable the firewall, it gives me a 1017 error.
My system: Code:
VPS Code:
To Action From |
5998
5999 7000-7500 7778 (chatserver on this ?) 9000-9001 Thats all you need. I just set all of them to both tcp/udp You only need 3306 open if you're going to access your database remotely. |
Wow, okay, I enabled and disabled the firewall several times, like I had done yesterday, and deleted and readded the ports and now it's connecting. Huh... odd.
I'm not complaining one bit! |
Quote:
|
if you are talking about the eqemulator.org login it has a flaw in how it sends packets to the clients. The only way to circumvent is by using a tunnel for your UDP traffic or potentially using a VPN.
The login server eqemulator.org uses is ancient and Rogean needs to update to the new public LS that has been available for years. |
Quote:
|
oh lol..
in that case we need to see the login logs and world logs... it should give you more information there, if the world isn't connected to the login it won't be listed. |
Latest world log:
Code:
[05-18-2018 :: 20:49:53] [World Server] Checking Database Conversions.. Code:
[05-18-2018 :: 20:49:55] [Zone Server] CURRENT_VERSION: 1.1.3 http://www.eqemulator.org/forums/showthread.php?t=41899 |
not seeing any login server attempts at the world server, so unless you cut off your world log that is a problem. Also asked for the login server log not the zone log.
|
Quote:
EDIT: No login server log file exists. |
I rebuilt the server twice and it finally worked; the "new_server" option, however, never worked, and I had to manually create the admin user, add all the info to the files, etc.
My friend is STILL having that problem: Error - a timeout occurred. She can ping the server, but every single time she tries to connect, it gives her that. I can connect from my computer and play. Her eqhost.txt Code:
[LoginServer] So frustrating, now. Not sure why it would allow me to play and not her. Both of us have fresh Titanium installs, no changes except the eqhost.txt file. Image of her error: https://i.imgur.com/Eo8vPwG.jpg |
Are you and your friend both in the same home, trying to connect ? On a Lan ?
Or is she trying to connect from another location ? Aslo check the log file in the client logs folder and see what it says. |
Quote:
Is there anything I should look for in her router that would stop the traffic? I'll have to ask what kind she has, I suppose, to see if it has a default firewall that's blocking traffic. Where are the client logs located, so I can walk her through it? |
Try this, just to for troubleshooting purposes :
Temporarily - put your server into the public Emu login server. If your friend can get on through there, then you have no port or firewall problems. |
Just to clarify, (for private loginserver, outside connections).
If your friend can connect to any server on that Emu public server list that supports your client version (like Titanium), then there is no issues on your friend's end. If your friend can't connect to any server, problem is on their end. (usually a firewall, which can also come from an antivirus program). If your server is patched into the Emu public login server and your friend can connect to it through there, then neither of you have any port or firewall problems. Ultimately, if absolutely nobody can connect to your server privately, or from the Emu public login server, the problem is on your end. Ruling all that out, then if the connecting problem is soley with your own private login server, then the problem is more than likely within your server configuration. It would still let YOU in, because you're connecting from within your own lan or network, regardless. Then it's a matter of looking at the two common culprits, the login.ini file and/or the eqemu_config.json file. |
All times are GMT -4. The time now is 10:32 PM. |
Powered by vBulletin®, Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.