Remote computer restart results in forgotten forwarding
Posted: Mon Aug 29, 2005 8:35 pm
I've been using Growl 0.7 on an iMac G5 and PowerBook G4 without any issues. Both are running Tiger 10.4.2 with all current updates.
Today I upgraded to 0.7.2 and decided to give the notification forwarding feature a try. After creating a new firewall service to allow TCP port 23052 and UDP port 9887 through everything works fine. That is until the sending computer detects the receiving computer is no longer available, at which time the receiving computer is removed from the list of computers to forward notifications. Furthermore when the receiving computer is re-detected, both the "use" checkbox and "password" fields have been cleared, rendering the feature useless.
Is there a way to make the configuration "stick?"
Thanks in advance!
Today I upgraded to 0.7.2 and decided to give the notification forwarding feature a try. After creating a new firewall service to allow TCP port 23052 and UDP port 9887 through everything works fine. That is until the sending computer detects the receiving computer is no longer available, at which time the receiving computer is removed from the list of computers to forward notifications. Furthermore when the receiving computer is re-detected, both the "use" checkbox and "password" fields have been cleared, rendering the feature useless.
Is there a way to make the configuration "stick?"
Thanks in advance!