IB server port requirements

[bobD 6]

Suddenly today my home network IB 2020 server is getting blocked by the Windows Defender Firewall. 

If I turn off the firewall for the local area network everything works, so I know it's definitely a firewall configuration issue

The server has been solid for some time and I haven't changed anything other than applying Windows updates as they come out. I'm suspicious that a Windows Defender update might have wiped some of my settings.

Context: home local area network; all connections should be coming from 192.168.4.*

IB server is on an up-to date Win10 Pro box

Anyone have a current firewall requirements link or cheatsheet for an IB 2020 server on a Win10 Pro machine?

TIA, bobD

[Virgo 18]

What is current network profile? Sometimes router restart or some other change causes Windows to think, that it has switched from private to public. Or domain to public. And All those have different firewall rules.

[tgbs 16]

You need to add exception to firewall. Port or program is your choice

https://supportcenter.lexisnexis.com/app/answers/answer_view/a_id/1081611/~/adding-exceptions-to-the-windows-firewall

[Frickler 16]

3 hours ago, tgbs said:

Port or program is your choice

Recently I had that problem too. Not with Interbase, but with svnserve. An exception for svnserve.exe was suddenly no longer an option, only the port (3690) worked.

[Hans J. Ellingsgaard 22]

Port 3050 (if it is installed with default options) has to be open on the server

[bobD 6]

On 4/1/2025 at 12:59 AM, tgbs said:

You need to add exception to firewall. Port or program is your choice

https://supportcenter.lexisnexis.com/app/answers/answer_view/a_id/1081611/~/adding-exceptions-to-the-windows-firewall

I ended up adding both: an allow inbound program rule for ibserver.exe, an the same rule for port 3050 tcp.

I have no idea how the previous Interbase exceptions got dropped, though the firewall control panel looks nothing like it once did, so I have to assume it's bee evolving with Windows updates.

Anyway, all the db clients now connect again with the Win Defender Firewall monitoring local area connection calls

What I don't know is whether that's overkill: If I disable the ibserver program rule and just leave the port open everything still works, including connecting to the server with IBConsole from my Delphi development machine, but ISTM that I remember something Interbase needing a UDP connection. Am I misremembering?

I don't know if Embarcadero removed that dependency, or I just didn't test enough to catch what's missing...

bobD

 

 

 

[bobD 6]

On 4/1/2025 at 12:42 AM, Virgo said:

What is current network profile? [...]

The machine identifies its connection as 'public'. It's a hardwire (not WiFi) connection to my router. Additional details in response to tgbs.

It could be that that changed with a router reboot--I'm not sure of the basis on which the db server or router decides how to characterize the connection  as public or private.

The firewall rules do segregate the local connections (I assume by seeing the calling IP address as 192.168.*).  I'd like the Interbase3050 rule to only accept calls from this side of the router, but it wasn't at all obvious to me how to configure that.

Edited 6 hours ago by bobD