Norton 360 blocking PostgreSQL - Solved

PandaB5PandaB5 Posts: 251

Hi

In the past week Norton 360 has started blocking PostgreSql - so every time I start Daz Studio I get an error message: A valid PostgreSQL CMS connection could not be established. It must be a recent update of Norton that caused this issue.

If I disable Norton Smart Firewall and Norton Auto-Protect - both for 15 minutes and then open Daz - everything works 100% - and even when they kick in again there is no problem - Daz works 100% until I close it.  But it's a pain having to disable my anti-virus every time I want to start Daz.

I can find Daz Studio in my list of applications to "allow" but I cannot find what / or how to whitelist the PostgreSql commands it runs. Can anyone point me in the right direction?

Thanks

 

Post edited by PandaB5 on

Comments

  • FishtalesFishtales Posts: 6,162

    The CMS, postgres.exe, needs access to an internal port. The port number can be found under Preferences/CMS. Open the Firewall and find where it allows port access and tell it to allow access to that port number.

  • PandaB5PandaB5 Posts: 251
    edited October 2017

    Thanks Fishtales. Adding postgres.exe to my list of allowed programs solved it for me.

    If anyone else has the problem the step-by-step solution is as follows:

    1. Open Norton 360
    2. Click on the settings on the light grey bar at the top
    3. Click on Firewall (2nd from the top)
    4. Go to the tab: Program Control
    5. Click on ADD
    6. It will open your list of programs and scroll to : DAZ3D and under DAZ3D there's a folder named: POSTGRESQL CMS - click on that
    7. Click on the folder named: Bin
    8. Click on postgres.exe (scroll down the bin folder until you find it.)
    9. It then brings up a block that is green to show the .exe is considered safe - there is a block that will show "automatic" - change that to "always allow". 
    10. Then click OK
    11. Then click apply.

     

     

    Post edited by PandaB5 on
  • FishtalesFishtales Posts: 6,162

    @PandaB5

    You are welcome. I'm glad you got it fixed.

Sign In or Register to comment.