I was wondering if you could set a permanent IP for a home server on the master server(s). Well, that's the only actual solution I've seen you come up with on the forums for this issue.
sn_SetNetState: Unable to open accept socket on desired port 4538, Trying next ports...
Have you come up with a better solution for this yet? I never had this issue when I ran Linux servers, just on Windows .. I've tried disabling the firewall, the ports are forwarded, etc. etc..
You can connect the first time, but when everyone leaves, it will go through the master server process and fail, try to connect to next port and keep doing this.
If you could add the IP as permanent, can you use a no-ip address? I have a dynamic address, like most people, so it will change eventually. Atleast I think it's dynamic, I haven't really noticed it change, but I just moved and got new ISP so .. yeah.
Master Server Permanent IP
- kyle
- Reverse Outside Corner Grinder
- Posts: 1965
- Joined: Thu Jun 08, 2006 3:33 pm
- Location: Indiana, USA, Earth, Milky Way Galaxy, Universe, Multiverse
- Contact:
Re: Master Server Permanent IP
This is on your end. somehow armagetron is not getting closed properly so the previous one is still running taking that port. most likely it is getting a sighup, which makes it restart, instead of something like a sigterm, which will kill it.Light wrote:sn_SetNetState: Unable to open accept socket on desired port 4538, Trying next ports...

Re: Master Server Permanent IP
I know it's on my end, but it's far from unique to me and as far as I can see, zman hasn't come up with a solution for it. I saw him tell someone that they can turn talk to master off and he can put the IP in the master server, which would completely go around the issue. I figured it couldn't hurt to ask.
Re: Master Server Permanent IP
We have the SERVER_DNS option where you can tell the master server a DNS name (or, in fact, IP) where your server is supposed to be reachable all of the time, if your IP is dynamic, you're supposed to get a dyndns or similar account and link SERVER_DNS to that. Won't solve the problem, though. The network socket gets reinitialised every time everyone leaves, and the strange error where a just released port is not available immediately again strikes whether TALK_TO_MASTER is on or off. DEDICATED_IDLE .01 will make the server restart completely when everyone leaves, maybe setting that in addition helps (plus an automatic server restart mechanism). The server restart gives the system more time to properly free the socket.
- Tank Program
- Forum & Project Admin, PhD
- Posts: 6712
- Joined: Thu Dec 18, 2003 7:03 pm
Re: Master Server Permanent IP
I suppose that actually what you really mean here is port, not IP. So that if the server finds port 4534 in use, and it's set to use port 4534, it will someone free that port up and then take it.
