4.267 - Looking for Sessions on Port 2400

[Gibsonm]

I was working with @BadgerDog and we discovered a quirk.

 

The Host settings were to host of Port 2300 (the default).

 

I as a Client had a screen saying "looking for sessions on Port 2400":

 

 

Should anyone intending to Host change it to "2400" going for forward??

 

As it was changing the Host to use Port 2400 made no difference, in terms of the Client being able to find the session.

 

The Client doesn't not have an option to specify the port to search on.

 

This happens using both the "8 user cap" executable and the "server" executable.

 

@Nike-Ajax @Major duck This may have implications for your Kanium session, although it wasn't an issue for TGIF.

 

Edited October 16, 2021 by Gibsonm

[Gibsonm]

UPDATE:

 

With @BadgerDog still Hosting in 4.267 I started a 4.265 Client in the hope that I could at least join but with the usual "flashing name" at his end to indicate I had an incompatible version.

 

My machine just "looked for sessions" (albeit without the "on Port 2400" message).

 

Edited October 16, 2021 by Gibsonm

[Ssnake]

I think port 2400 is for discovering sessions and initiating the host-client handshake, where they will negotiate which port actually to use for the game session (typically that would be 2300, but it could be another one depending on the local conditions).

[Gibsonm]

UPDATE: Its working now (i.e. I could join a session hosted by him).

 

What's changed?

 

It appears that in the last seven days Windows (God bless em) rolled out some sort of update to the their firewall package forcing rules to be applied.

 

@BadgerDog was not previously running the Windows Firewall and last week he could Host, this week he couldn't.

 

Going in and editing the Windows Firewall to allow both inbound and outbound traffic for SB Pro PE now means he can host again.

 

Edited October 17, 2021 by Gibsonm

[Volcano]

FWIW, nothing has changed regarding ports per se, its just that the text is displayed there to (hopefully) help people figure out what port it has been looking at when connecting (not that the port # has changed in this update, I mean).

[Sean]

Depending on how you do the firewall exception, the windows firewall will have to be checked and exceptions reapplied every time there is a new exe.

[Gibsonm]

4 minutes ago, Sean said:

Depending on how you do the firewall exception, the windows firewall will have to be checked and exceptions reapplied every time there is a new exe.

 

Yes, I'm comfortable with that process.

 

The gotcha for the wider audience, I think, is that it appears that post the Windows update this week, the Windows firewall maybe activated without the user knowing.

 

Certainly pre this week (both pre 4.267 and pre the Windows update) @BadgerDog did not need to add the new .exe to the exceptions list because he wasn't running the Windows Firewall.

 

Now in order to get it running, he did need to add it (even though he did not consciously choose to activate the Windows Firewall).

 

[Nike-Ajax]

Thanks for the heads-up @Gibsonm - and thanks for thinking of us.

 

We will cross fingers and toes and see tonight.

[Major duck]

Year Thanks @Gibsonm

MD