Just felt a need to agree with Clifford, you should always leave the
firewall running setting up the ports for the required database,
PostGreSQL will be the same, but different ports, as will other databases.
Other Anti Virus products also include firewalls, where the port
settings route is always best.
Just not so obvious to set up sometimes.
Based in Chester in the UK.
On 24/10/2017 19:36, Clifford Ilkay wrote:
> On Mon, Oct 23, 2017 at 7:42 PM, Lester Hurrelbrink III < > firstname.lastname@example.org> wrote:
>> The IT guy didn’t think that was the issue but when he turned them off
>> everything worked just fine. So in retrospect and probably 40 + hours of
>> troubleshooting, a Windows update came through the original server that
>> turned on some type of firewall that prevented connecting to FrontBase and
>> these same firewalls were installed in the new server when the OS was
> That “some sort of firewall” would be the Windows Firewall. You should not
> assume that just because you turned it off and it works now that it will
> continue to remain off and that Omnis will continue to be able connect to
> FrontBase. A more robust solution is to enable the Windows Firewall and
> open the port(s) you need to connect to FrontBase. That will survive
> updates that re-enable the firewall. Here is an article how to do that for
> SQL Server. Adjust as necessary for FrontBase. < > docs.microsoft.com/en-us/sql/database-engine/configure-windows/configure-a-windows-firewall-for-database-engine-access
> Clifford Ilkay
> +1 647-778-8696
> Manage your list subscriptions at lists.omnis-dev.com
Manage your list subscriptions at lists.omnis-dev.com