Failed to connect to zoneserver
I've recently set up and configured a server, and it appears that one of the clients I'm using isnt getting over to the zoneserver after character select. I've been able to view the server, character create, and receive error on the client machine :
sony\everquest\logs\dbg.txt Code:
2014-09-20 23:56:56 Initializing character select UI. I am able to zone just fine when connecting as a client from the server, but nothing from a different workstation. I have also verified that it is not account related from the server machine. Firewalls are turned off and Ive forwarded ports as necessary. Hell, I've even wired both server and client to make sure it wasnt a wifi latency issue lol. I did see somewhere that the zone connection time can be increased. Any thoughts would be greatly appreciated :-) |
These are on the same network segment? Or is there a router? I still like the idea of port forwarding being the issue. What do the zone logfiles say?
Is the server running linux? Can you run a zone server from the command-line (in case it is crashing) |
Post your config files, if you would. We can take a look to see if there's something askew.
(Obfuscate your uid/pw, please) It may be something as simple as configuring for localhost when you need to have it setup on your LAN card's IP. |
Sorry i should have been more clear. This is a home lan on the same router. To try and eliminate the issue altogether I have forwarded 1-65535.
I'm using win7 pro to host at the moment. The workstation is also win 7 pro. I was trying this from server 2012, but I was getting tons of errors. Server 2012 is kinda a learning project now lol eqemu_zone_2612.txt Code:
[09.20. - 22:50:19] ---- Zone server halas, listening on port:7004 ---- Code:
[Network] [09.20.14 - 22:48:33] New Titanium client connection from 192.168.1.101:61801 |
Thanks, this is making me cross-eyed lol
Code:
<?xml version="1.0"?> Code:
[database] |
In login.ini:
Code:
[options] Code:
local_network = 192.168.1. That was telling your login server to listen for specific traffic at '1.112' instead of the '1.x' subnet. Post back if you're still having issues. EDIT: You probably want to enable and set this to the same address as your local as well: Code:
<!-- <address>some.server.com</address> --> |
I updated both settings and it worked. Thanks for your help!
|
All times are GMT -4. The time now is 01:44 PM. |
Powered by vBulletin®, Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.