7100 - 7500 forwarded in your router ?
configs (including login.ini) set right for IP's ? |
Grumpy, thanks for continuing to assist. to answer your questions
Yes eqemu_config.json with removed user/pass Code:
"server" : { Code:
[database] port forwarding looks like 5999 5998 9000 7778 7000-7500 QoS is disabled on the router UPnP is disabled on the router IPv6 is disabled on the router this is a netgear R6230 with the latest firmware. I can login from LAN machines without issue using RoF2 client. anyone trying to come in from the WAN gets timeouts on the zone ports (7000, 7001, etc.) zone.exe is starting all of the zones on 127.0.0.1:<random high port> like 61130 if I use a site like yougetsignal.com for port 7000 its showing as closed. yet 5999 is open netstat /an does not show those ports as listening on the win 10 box. tho 7778 is. |
Not quite sure what you're doing here ? <address>.no-ip.biz
You are using 9001, is that in port forward ? |
<address> was just me masking my DNS address.
9001 wasn't in port forwarding. |
Quote:
The dyndns account pointed to that IP and clients put that address in their eqhost. But not sure how you are setting yours up. |
after adding 9001.
I can see that 9000, 9001, 5998, 5999 are all open ports to the outside world. 7000 , 7001, etc are not. |
using my actual IP and removing all DNS entries. I end up with port 7000 still being an issue.
I'm also seeing [Error] Handle_NewLSInfo error, remote address was null, defaulting to stream address <my ISP IP address> |
In your config, can you try this out ?
"high" : "7100", "low" : "7500" Instead of this ? "high" : "7400", "low" : "7000" |
i'm assuming you meant
low 7100 high 7500 i'm seeing open UDP ports in that range now (and the 7000 range if i switch back). i'm guessing that the DNS trick you asked previously was the fix. will need to test from the WAN to confirm |
Quote:
|
still an issue
this is from the client outside of the network Code:
[Sat May 05 15:37:49 2018]00466:Initializing character select UI. |
this is a working LAN login.
something is happening that port 7100 isn't being used locally. and it isn't giving an actually address on port 7100 for outside traffic. Code:
[Sat May 05 15:45:37 2018]00233:Zone Connect -- 0 -- Received MSG_ZONE_ADDRESS |
Is it something as simple as needing to add ?
!--<address>Serving Machines IP</address>--> <!--<localaddress>127.0.0.1</localaddress>--> To the json file in some way? I noticed that this newest build doesn't use the xml file anymore. |
The FULL .json config is a little different, but this is what I am
using right now on the public server I have up. It doesn't apply to a private outside login, since I am using the Emu public login. Code:
{ |
the client isn't receiving an address for zones outside of the network. I can't explain why that is happening
inside the network [Sat May 05 15:45:37 2018]00233:Zone Connect -- 0 -- Received MSG_ZONE_ADDRESS [Sat May 05 15:45:37 2018]00234:Zone addr [192.168.99.76:48155] received... outside of the network [Sat May 05 15:37:53 2018]00468:Zone Connect -- 0 -- Received MSG_ZONE_ADDRESS [Sat May 05 15:37:53 2018]00469:Zone addr [:48155] received... the server is running on a laotop. the client inside of the network is on a completely different machine. yet I get connected fine. |
All times are GMT -4. The time now is 03:36 AM. |
Powered by vBulletin®, Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.