Port not opening
- Tannermon11
- Average Program
- Posts: 86
- Joined: Tue Sep 18, 2007 1:11 am
Port not opening
So in the past people have been able to connect to my server. Now when I turn the server on, in the command prompt it shows:
[0] Bound socket to *.*.*.*:55696.
[0] Bound socket to *.*.*.*:4534.
[0] Setting CYCLE_BRAKE_DEPLETE (Group: Annoying) deviates from its default value; clients older than 0.2.5.0 may experience problems.
[0] Connecting to Master Server 1...
[0] Killing user 0, ping 1.25.
[0] Login information sent. Waiting for reply...
[0] Got address 130.13.81.68:4534.
[0] Login Succeeded. User Nr. 1
[0] Syncing with server...
[0] Relabeling NetObjects...
[0] Syncing again...
[0] Done!
[0] Sending my server info...
[33] Killing user 33, ping 1.25.
[0] Logging out...
[0] Done!
[0] Killing user 0, ping 0.270032.
[0] Closing socket bound to *.*.*.*:4534
[0] Bound socket to *.*.*.*:4534.
[0] Connecting to Master Server 2...
[0] Killing user 0, ping 1.25.
[0] Login information sent. Waiting for reply...
[0] Login Succeeded. User Nr. 2
[0] Syncing with server...
[0] Relabeling NetObjects...
[0] Syncing again...
[0] Done!
[0] Sending my server info...
[33] Killing user 33, ping 1.25.
[0] Logging out...
[0] Done!
[0] Killing user 0, ping 0.279811.
[0] Closing socket bound to *.*.*.*:4534
[0] Bound socket to *.*.*.*:4534.
[0] Connecting to Master Server 3...
[0] Killing user 0, ping 1.25.
[0] Login information sent. Waiting for reply...
[0] Login Succeeded. User Nr. 1
[0] Syncing with server...
[0] Relabeling NetObjects...
[0] Syncing again...
[0] Done!
[0] Sending my server info...
[33] Killing user 33, ping 1.25.
[0] Logging out...
[0] Done!
[0] Killing user 0, ping 0.250927.
[0] Closing socket bound to *.*.*.*:4534
[0] sn_SetNetState: Unable to open accept socket on desired port 4534, Trying next ports...
[0] Bound socket to *.*.*.*:4535.
[0] Connecting to Master Server 4...
[0] Killing user 0, ping 1.25.
[0] Login information sent. Waiting for reply...
[0] Got address 130.13.81.68:4535.
[0] Login Succeeded. User Nr. 2
[0] Syncing with server...
[0] Relabeling NetObjects...
[0] Syncing again...
[0] Done!
[0] Sending my server info...
[0] Logging out...
[0] Done!
[0] Killing user 0, ping 0.247001.
[0] Closing socket bound to *.*.*.*:4535
[0] sn_SetNetState: Unable to open accept socket on desired port 4535, Trying next ports...
[0] Bound socket to *.*.*.*:4536.
[0] Ping charity changed from 0 to 500.
[0] Nobody there. Taking a nap...
[0] Timestamp: 2010/06/30 12:32:07
[0] Closing socket bound to *.*.*.*:4536
[0] Bound socket to *.*.*.*:4536.
I don't know why it has stopped now..
[0] Bound socket to *.*.*.*:55696.
[0] Bound socket to *.*.*.*:4534.
[0] Setting CYCLE_BRAKE_DEPLETE (Group: Annoying) deviates from its default value; clients older than 0.2.5.0 may experience problems.
[0] Connecting to Master Server 1...
[0] Killing user 0, ping 1.25.
[0] Login information sent. Waiting for reply...
[0] Got address 130.13.81.68:4534.
[0] Login Succeeded. User Nr. 1
[0] Syncing with server...
[0] Relabeling NetObjects...
[0] Syncing again...
[0] Done!
[0] Sending my server info...
[33] Killing user 33, ping 1.25.
[0] Logging out...
[0] Done!
[0] Killing user 0, ping 0.270032.
[0] Closing socket bound to *.*.*.*:4534
[0] Bound socket to *.*.*.*:4534.
[0] Connecting to Master Server 2...
[0] Killing user 0, ping 1.25.
[0] Login information sent. Waiting for reply...
[0] Login Succeeded. User Nr. 2
[0] Syncing with server...
[0] Relabeling NetObjects...
[0] Syncing again...
[0] Done!
[0] Sending my server info...
[33] Killing user 33, ping 1.25.
[0] Logging out...
[0] Done!
[0] Killing user 0, ping 0.279811.
[0] Closing socket bound to *.*.*.*:4534
[0] Bound socket to *.*.*.*:4534.
[0] Connecting to Master Server 3...
[0] Killing user 0, ping 1.25.
[0] Login information sent. Waiting for reply...
[0] Login Succeeded. User Nr. 1
[0] Syncing with server...
[0] Relabeling NetObjects...
[0] Syncing again...
[0] Done!
[0] Sending my server info...
[33] Killing user 33, ping 1.25.
[0] Logging out...
[0] Done!
[0] Killing user 0, ping 0.250927.
[0] Closing socket bound to *.*.*.*:4534
[0] sn_SetNetState: Unable to open accept socket on desired port 4534, Trying next ports...
[0] Bound socket to *.*.*.*:4535.
[0] Connecting to Master Server 4...
[0] Killing user 0, ping 1.25.
[0] Login information sent. Waiting for reply...
[0] Got address 130.13.81.68:4535.
[0] Login Succeeded. User Nr. 2
[0] Syncing with server...
[0] Relabeling NetObjects...
[0] Syncing again...
[0] Done!
[0] Sending my server info...
[0] Logging out...
[0] Done!
[0] Killing user 0, ping 0.247001.
[0] Closing socket bound to *.*.*.*:4535
[0] sn_SetNetState: Unable to open accept socket on desired port 4535, Trying next ports...
[0] Bound socket to *.*.*.*:4536.
[0] Ping charity changed from 0 to 500.
[0] Nobody there. Taking a nap...
[0] Timestamp: 2010/06/30 12:32:07
[0] Closing socket bound to *.*.*.*:4536
[0] Bound socket to *.*.*.*:4536.
I don't know why it has stopped now..
- INW
- Reverse Outside Corner Grinder
- Posts: 1950
- Joined: Tue Jul 07, 2009 4:10 pm
- Location: Charlotte, NC, USA
Re: Port not opening
Since it ends in i would say the server is connectible. Or at least on my server it says that 1 million times before stopping and it is still connectible.
Code: Select all
[0] Bound socket to *.*.*.*:4536.
Re: Port not opening
Yeah, and at least one master server has been told the correct port in that log, so all should be reasonably fine. It's an odd anomaly with your operating system, we do free the port before re-opening it, that should work in all cases. Maybe a pesky personal firewall software ruling over the ports with an iron and lazy fist?
As a workaround, if you absolutely want to have it listen on 4534, you can start the server once with TALK_TO_MASTER 1, have it quit immediately, then restart it with TALK_TO_MASTER 0.
As a workaround, if you absolutely want to have it listen on 4534, you can start the server once with TALK_TO_MASTER 1, have it quit immediately, then restart it with TALK_TO_MASTER 0.
- Tannermon11
- Average Program
- Posts: 86
- Joined: Tue Sep 18, 2007 1:11 am
Re: Port not opening
When you say start it then quit immediately, are you saying to just turn the server on then turn it off the second the command prompt pops up?
Re: Port not opening
Yeah, that, or run it with a very short DEDICATED_IDLE.
- Tannermon11
- Average Program
- Posts: 86
- Joined: Tue Sep 18, 2007 1:11 am
Re: Port not opening
When I tried opening with master 1, then closed, then opened with 0, it wasn't showing.
Re: Port not opening
You'd need to give it an extra bit of time. The masters' first connection attempt is likely to fail and you'll need to wait for the second.
- Tannermon11
- Average Program
- Posts: 86
- Joined: Tue Sep 18, 2007 1:11 am
Re: Port not opening
People were able to sucessfully get on but..I noticed for example if I go on the server then leave, the port sometimes doesn't stay open, making it so people can't connect. It doesn't do it everytime I leave, but it does it sometimes. What Might be causing that?
Re: Port not opening
The same mechanism. To work around other problems (mysterious breaking sockets), the server shuts down networking and restarts it every time everyone leaves a server. To work around THAT, put DEDICATED_ILDE 0.000001 into everytime.cfg. This will make the server restart completely after people played, then everyone leaves.
Re: Port not opening
[quote="Z-Man"]DEDICATED_ILDE 0.000001 quote]
i use 1, works fine..
i use 1, works fine..