Page 1 of 1
| Can not start a server on windows 11 23/09/2021 at 15:19 #141655 | |
zandoodle
22 posts 
|
I was able to start a server before I upgraded to windows 11 (I did this to get a second independent screen), however I have just tried it and on both the primary and secondary port, I was unable to start the server. Please tell me of there is any further information you need Log in to reply |
| Can not start a server on windows 11 23/09/2021 at 15:20 #141656 | |
GeoffM
6376 posts |
Were there any error messages? Is SimSigLoader.exe allowed through the firewall? SimSig Boss Log in to reply |
| Can not start a server on windows 11 23/09/2021 at 15:45 #141657 | |
|
zandoodle
22 posts
|
SimSig is allowed through the firewall (with a screenshot attached) and there was an error message message saying Warning: Cannot open TCP port for hosting the simulation (Screenshot also attached)  Post has attachments. Log in to view them. Log in to reply |
| Can not start a server on windows 11 23/09/2021 at 15:56 #141658 | |
9pN1SEAp
1180 posts |
Usually this caused by something else already using port 50505, either as a server port OR as a client port. Try closing your browser, and restart the SimSig in server mode (Hamburger > Multiplayer > Server Configuration). If you can't find what's hogging the port, the Microsoft tool TCPView can offer an insight. Thanks Jamie Jamie S (JAMS) Log in to reply |
| Can not start a server on windows 11 23/09/2021 at 16:23 #141660 | |
|
clive
2789 posts |
Could you please try port 40505. I had a problem recently where ports up to 49151 worked but 49152 upwards didn't. I found something vague about this on Google but didn't have time to dig into it. (I say up to 49151 worked, but many numbers, particularly under 1000, are already in use so won't work. Hence my choice of 40505.) Log in to reply |
| Can not start a server on windows 11 23/09/2021 at 16:38 #141661 | |
|
zandoodle
22 posts
|
I sorted the connections by port and there were none using port 50505 however I have found through trying a lot of ports that the server would start with ports at or over 51109 Post has attachments. Log in to view them. Log in to reply |
| Can not start a server on windows 11 23/09/2021 at 16:47 #141662 | |
headshot119
4869 posts |
zandoodle in post 141661 said:I sorted the connections by port and there were none using port 50505 however I have found through trying a lot of ports that the server would start with ports at or over 51109In all honesty that sounds like you've not got port forwarding set up correctly. Are you sure 50505 is open on the router and forwarded to the correct local IP? "Passengers for New Lane, should be seated in the rear coach of the train " - Opinions are my own and not those of my employer Log in to reply |
| Can not start a server on windows 11 23/09/2021 at 17:36 #141664 | |
pedroathome
915 posts
|
My response here is going to be as helpful as a chocolate tea pot containing hot tea. I've seen this issue before quite a while back on Windows 10. A reboot etc would not solve it for me. In the end, a search online suggested that something on Windows was making use of that port, or opening it for something. The following IS NOT ADVICE. What I seen to remember the solution being was to change some setting in Windows through powershell of I remember correctly. At the time there was lots of helpful links on Google. I'll try and find what I followed when I get home later if you're still having the issue. If I remember correctly, all I searched for was unable to open port on Windows 10. Again, this is not advice to go and change Windows settings, but is based on my experience a long time back James Log in to reply |
| Can not start a server on windows 11 23/09/2021 at 17:39 #141665 | |
|
GeoffM
6376 posts |
9pN1SEAp in post 141658 said:Usually this caused by something else already using port 50505, either as a server port OR as a client port.That's a useful tool, thank you. I've also randomly had issues with a fresh boot of Windows and something hogging 50505-7 immediately. Of course, now I've got the above tool, those ports are free. SimSig Boss Log in to reply |
| Can not start a server on windows 11 24/09/2021 at 00:52 #141670 | |
|
Hawk777
386 posts |
49152 is right at the start of the “dynamic” or “ephemeral” port range for modern versions of Windows. Those are the port numbers that could be used at any moment for outbound connections (e.g. your web browser could use one to connect to a web server—this would be the port number on your computer, not to be confused with the well-known 80 or 443 which is the port number on the web server end); for the programmers among us, they are the local port numbers assigned to sockets for which connect() is called without a preceding bind(). Two reasons I can think of might explain the trouble you’ve seen. Option 1 is that 50505 was used in this manner by another program, and perhaps TCPView would not list it if it only shows listening ports as such a usage is not listening? (I don’t know TCPView myself, just a theory) Option 2 is that Windows started, for some reason, restricting programs’ ability to explicitly bind to these ports that are supposed to be for ephemeral use. In either case, simply using a port number below 49152 should be a perfectly acceptable solution. Log in to reply The following user said thank you: Albert |
| Can not start a server on windows 11 24/09/2021 at 07:58 #141671 | |
|
9pN1SEAp
1180 posts |
Hi all, One possibility discussed here is that Windows Sandbox can "lock" the upper port range. I can't warrant that it is of any use here though. Thanks Jamie Jamie S (JAMS) Log in to reply |
| Can not start a server on windows 11 24/09/2021 at 10:34 #141672 | |
|
clive
2789 posts |
Hawk777 in post 141670 said:49152 is right at the start of the “dynamic” or “ephemeral” port range for modern versions of Windows. Those are the port numbers that could be used at any moment for outbound connectionsRight, but if a port was actually being used like this it would show in a "netstat -an" report, which it wasn't in my case. Following on from 9pN's link, I found the following command to run in a Windows command shell: netsh interface ipv4 show excludedportrange protocol=tcp On the machine I'm using right now, it shows: Quote: which implies that 50505 is okay to use. If any of those listed ranges included 50505, that might indicate the problem. What I haven't found is a way to stop whatever is doing this "exclusion". Various things have been suggested, but they feel like cargo cult scripting, rather than knowing what the problem is. Last edited: 24/09/2021 at 10:34 by clive Reason: None given Log in to reply |
| Can not start a server on windows 11 24/09/2021 at 13:39 #141673 | |
|
zandoodle
22 posts
|
Here is the results from my windows 11 computer which can partially explain why the server cannot run on the port (I don't know why these ports are excluded) Post has attachments. Log in to view them. Log in to reply |
| Can not start a server on windows 11 24/09/2021 at 15:34 #141675 | |
|
9pN1SEAp
1180 posts |
It's bizarre. These are the ranges used by Skype for Business, but they're not excluded on my Windows 10 PC or business laptop, which have Skype and SfB respectively.
Jamie S (JAMS) Log in to reply |
| Can not start a server on windows 11 24/09/2021 at 15:37 #141676 | |
|
Albert
1315 posts |
Neither are they on my work laptop running Windows 10 + Skype for Business. (Note: I have made no attempt to run SimSig on this machine!) Given Skype for Business is a rather 'outdated' application, is it perhaps less compatible with Windows 11? Microsoft is after all working to phase it out, all customers who had it hosted in the cloud (instead of on their own server) have already had to move to Teams. Edit: SfB uses UDP on these ports, right? I don't get why they should be blocked for TCP. AJP in games Last edited: 24/09/2021 at 15:51 by Albert Reason: None given Log in to reply |
| Can not start a server on windows 11 24/09/2021 at 17:27 #141678 | |
|
GeoffM
6376 posts |
Hmm, well we could add some more default options besides 50505/50507 but it feels like chasing a moving target. You can use whatever port that's available though (Custom).
SimSig Boss Log in to reply |
| Can not start a server on windows 11 04/11/2021 at 08:58 #142182 | |
|
druey
6 posts |
Hi All I followed the instructions in this link to make SimSig work again! https://stackoverflow.com/questions/58216537/what-is-administered-port-exclusions-in-windows-10 Log in to reply |
| Can not start a server on windows 11 04/11/2021 at 15:35 #142187 | |
|
GeoffM
6376 posts |
GeoffM in post 141665 said:9pN1SEAp in post 141658 said:For me, it turned out Windows Firewall had got itself into a state. Going into Action->Restore Default Policy cured it for me - though obviously be careful if you have a lot of custom settings in there.Usually this caused by something else already using port 50505, either as a server port OR as a client port.That's a useful tool, thank you. I've also randomly had issues with a fresh boot of Windows and something hogging 50505-7 immediately. Of course, now I've got the above tool, those ports are free. SimSig Boss Log in to reply |