Can´t launch with firewall

Aztecaphoto

• 2011年05月03日 22:25

Hi:
Due yo security reasons, my iMac is connected to a firewall.
While activated under "admin" account, it worked for several weeks. It crashes now every time I launch it.
I know maybe it is because the SW can´t get in touch over the web with PO servers (but, who knows?)
So, how can I keep working CO6?
Skipping the firewall is out if question...

Regards

0

• 

  Paul Steunebrink

  • 2011年05月04日 06:29

  It is not the firewall. Why? Because I can't see of any reason from either your post or from the fact that CO6 runs without connection to the Phase One activation server.
  Next, in general, firewalls are configured to allow outgoing connections, preventing ingoing. In addition CO6 uses TCP port 80, and I don't think you blocked that port (it is the http protocol that uses TCP/80, hence you would not be able to post here from behind that system).
  
  You have to look for another reason. I am happy to discuss any other option with you.

  0
• 

  Aztecaphoto

  • 2011年05月04日 21:59

  Thanks Paul:
  The thing is that if I want to work with CO Pro properly, I have to unplug the server cord. Done several times.
  I have CO6.1 installed and I can´t deactivate the license to install CO6.2, neither send a crash report. It quits wihout any explanation or window in both cases.
  I believe is not a CO SW issue, but I have no clue what´s happening.
  
  Perhaps I´ll have to take the Imac to an "open" server connection. I have admin permit on this machine, but not over the web server at work.
  
  Saludos

  0
• 

  Paul Steunebrink

  • 2011年05月05日 10:11

  Hi Juan,
  
  I am not sure I entirely understand your post, despite re-reading it several times. Such can happen. No problem. Some tips anyway.
  
  When updating CO, from 6.1 to 6.2 for example, does not require deactivating before update.
  
  You mention the server cord. I could not figure it out but assume for now it is the Ethernet network cable. For a test, you could start CO with the cable disconnected, and next, connect it again. See if CO want to run.
  
  In case of crashes of CO, I suggest to do some general maintenance on OS X (repair permissions, rebuild drive), an CO (refresh default session file, refresh preference files, clear batch history, clear and rebuild output recipes). Hope this helps.

  0

投稿コメントは受け付けていません。