Also, for anybody who is doing any forwarding to/from a Mac, be aware
that the old UDP protocol has been completely removed from Growl/Mac.
If you are forwarding from a PC to a Mac using UDP on port 9887, it
isnt going to work anymore. You can edit your forwarding settings to
now use GNTP over port 23053 instead and you should be all set again
(and get some nice new features as well like icon forwarding, etc).
If anybody tries it out, let me know your experience.
Try that and let me know how it goes.
> --
> You received this message because you are subscribed to the Google Groups "growl for windows" group.
> To post to this group, send email to growl-fo...@googlegroups.com.
> To unsubscribe from this group, send email to growl-for-wind...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/growl-for-windows?hl=en.
>
>
if the 'NONE' is where the password hash should go. if that is not
present (as in this case), then GfW will reject any notification from
the network. (If it were correctly passing the password hash, it
should look something like: GNTP/1.0 NOTIFY AES:blahblahblah.blahblah
SHA256:blahblahbah.blahblah)
You can try asking on the Growl/Mac discussion group here:
http://groups.google.com/group/growldiscuss/ to see if they have any
ideas.
Subscriptions are a separate thing from forwarding and you dont need
to (and shouldnt) configure any subscriptions to get forwarding to
work (which is also why the documentation on forwarding doesnt mention
it).
I have a Mac here, but it is still running Snow Leopard, so I will
have to upgrade it to Lion before I can install Growl 1.3. Once I do
that, I can try to reproduce your issue, but from seeing what the log
shows, it definitely sounds like the password is not being handled
correct on the sending (Mac) side.
What works:
- forwarding from Mac to PC *if* you have the same password set up
correctly on both ends. On the PC, you have to have the password set
up on the 'Security' tab, and on the Mac, you have to set the password
for each machine that you are forwarding to (click to the right of the
name (Growl on MACHINE) in the password column to enter the password -
it is NOT the same as the master password for incoming notifications).
What doesnt work:
- some images dont come through when going from Mac to PC. web-based
images (urls) seem to work fine, but local images are not forwarded
correctly
- forwarding from PC to Mac doesnt seem to work at all. With a
password set, the Mac cannot properly parse the incoming message, and
with no password set, it complains that the keyHash is missing.
Both of those appear to be bugs in the Mac implementation and the Mac
guys know about them now, so hopefully they can get them fixed. That
said, your case (forwarding from Mac to PC) does work for me when
configured properly, so hopefully we can get yours to work for you as
well.