Notifications Not Forwarding

[tms8707056]

I have a Mac mini that is setup as a media server. Growl is setup to display notifications from hellanzb and works fine. It is also setup to forward the notifications to my MBP. However, the forwarding does not seem to work. Any ideas why the Mac mini would see the MBP but not forward the notifications? See the attached screens for Growl network configuration...

My Mac mini network configuration.

Mac mini.png (44.57 KiB) Viewed 38742 times

My Macbook Pro network configuration.

MBP.png (43.85 KiB) Viewed 38711 times

[tms8707056]

Anybody? I am sure that my configuration is correct as far as Growl is concerned. Both computers are on the same network but I wouldn't think that the router configuration would affect it. What else can I check to troubleshoot?

[tms8707056]

Bump.

[clintobean14]

I too have had troubles setting this up. The only time I got notifications to forward were for instance in a couple menubar apps I have, that run on both of the macs, so it seems like forwarding a notifcation like from the google notifier from one machine to another was redundant. But I could never get remote app registration to work, probably because I don't know much a bout this server password in the network tab. Do I have a server password? I don't know, I've tried using my account passwords, as its both admin accounts and the same password on my macbook and emac. I can't find any documentation on the Web site about how to set this up though.

[tms8707056]

Anybody else have any ideas?

[Ephilei]

I have the same problem. I looked for a solution a while back and the consensus of a few users is that it's more than an end user problem. ie, wait for further, official releases.

[techno]

I'm having the same problem. Messages on my desktop are not forwarding to my laptop.

Forwarding from desktop to laptop is enabled and passwords set on both and match.

Firewall holes punched for appropriate TCP and UDP ports.

Getting the following messages in system log:

GrowlHelperApp[11883]: WARNING: could not register Growl server.

GrowlHelperApp[11898]: authentication failure: received signature doesn't match computed signature

[mkeen]

I am having the same problem with a similar setup. I am trying to forward growls from my Mac Mini to my MacBook Pro on my local home network. Neither Growl setups have passwords required to register a new application. I am receiving the growls on my Mini, but they are simply not being forwarded and I am getting the same error messages as techno. Any ideas from someone familiar with Growl's inner workings?

[danielB]

Has this problem with GrowlNotify Notifications not Forwarding ever been rectified? I'm getting the mismatched signature alert failures on my server as listed in the posts above. I'm attempting to use forwarded Growl notifications as feedback for Pykota print serving...and everything's working but the Growl notifications are failing with signature mismatches.

danielB

[boredzo]

All of you:

First, install the beta on both machines: http://growl.info/beta.html

If that doesn't solve the problem:

• What kind of machine are you forwarding from?
• If it's a Mac mini, what kind of processor(s) does it have?
• What kind of machine are you forwarding to?
• If it's a Mac mini, what kind of processor(s) does it have?

You can check what kind of processors your Mac has by looking in About this Mac in the  (Apple) menu.

[gracion]

I installed the beta but still no notification on the remote Mac.

forwarding from: MacBook 2Ghz (original)
forwarding to: Mac mini 1.42 Ghz PowerPC

When setting a password on both Macs, the sender logs:
5/19/09 8:59:31 AM GrowlHelperApp[552] Authentication failed while forwarding to 192.168.1.52:3162 ((null))
and the receiver logs:
authentication failure: received signature doesn't match computed signature.

So I set the password blank on both Macs and restarted Growl on both. This eliminated all error logging, but still no notification. The firewall on the receiver Mac does show something is received on port 23052 (which is allowed by the firewall).

On the receiver Mac, I've tried "Allow remote application registration" both checked and unchecked.

Also, on the sender, checking or unchecking the "Use" box in the "other computers" list logs this each time:
5/19/09 9:13:54 AM System Preferences[504] What calls resolveService:?

[gaelicWizard]

I have the same problem. Every time a notification is forwarded from my Mac Mini, Growl on my MacBook prints a signature mismatch line in Console.

I'm running Growl 1.1.5b1 (as posted on the beta page) on both machines. My source machine (the one which is posting notifications) is a Mac Mini G4. The target machine is a MacBook. I have tried running Growl in Rosetta on the MacBook (GrowlHelperApp and GrowlMenu), but the same error results.

Help?

JP

[gaelicWizard]

This problem is definitely related to the password. If I set the password to blank on both sides, then the notifications work just fine.

I'm betting this is an endian issue.

JP

[boredzo]

I'm betting this is an endian issue.

But you ran GrowlHelperApp in Rosetta on the Intel machine. That makes it effectively running in PowerPC on both ends, so if you still had the problem, that pretty much disproves that it could be endianness-related.

[gaelicWizard]

I'm betting this is an endian issue.

But you ran GrowlHelperApp in Rosetta on the Intel machine. That makes it effectively running in PowerPC on both ends, so if you still had the problem, that pretty much disproves that it could be endianness-related.

Quite right. Still smells endian-y though. I really know next-to-nothing about Growl's source so I can't agree definitively.

Wait, am I arguing with myself?

:-)

JP

[ssgelm]

I'm having this same problem when trying to send notifications from a ppc mac mini to a c2d mbp. It continues to not work even if there's no password set. Any ideas?