>> Thought this was a well know problem with the 1.2 release. No? > > We won't know until we know what “this” is, which means first establishing > which version you're using on each machine and how each machine is configured.
True. Well for me "this" is... I've upgraded both machines to 1.2.1b2. The pref panes on both machines show "running". Version shows the beta2. The 10.5.8/Intel machine has "forward" "use machine" and "password" properly set. The should-be-receiving end is a 10.6.2/Intel machine with "listen for incoming notifications" and "allow remote registration" set. netstat -nl | grep 9887 netstat -nl | grep 23052 Shows growl listening on udp port 9887 on the 10.6 machine, not on port tcp port 23052 though. > Depends on what you mean by “remote notifications”. Sending original > notifications over UDP (e.g., with growlnotify) works fine. Forwarding's > busted, and fixed in 1.2.1b1. Doing a "growlnotify" on the forwarding machine I do get a local notification message. I also do get a "could not find local GrowlApplicationBridgePathway, falling back to NSDNC" in the console though. Running "growlnotify" on the 10.6.2 machine brings up the notification ... even without the "GrowlApplicationBridgePathway" log message. I see GrowlHelperApp[960] authentication failure: received signature doesn't match computed signature Sounds like it's just the password that is wrong. But I made sure they use the same and restarted Growl - twice. cheers -- Torsten -- You received this message because you are subscribed to the Google Groups "Growl Discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.
