Can't get applications to registered on Mac

[Adam]

I have Growl for Windows set up to forward notifications to Growl on
my Mac. I know it's configured correctly because on the Mac, when I
run the "tail -f ~/Library/Logs/Growl.log" command in the Terminal, I
can see the notifications as they occur. The problem is they're never
being *displayed* by the Mac, only *logged*.

As I understand it, in order for Growl on the Mac to be able to
*display* a notification, the originating application must be in the
Mac's "Applications" list in the Growl preferences.

On the Mac, I have "Allow remote application registration" checked and
a server password set. I've actually tried it with and without a
password. Despite this, the only programs listed in the "Applications"
tab in the Mac's Growl preferences are the Mac's programs. There are
no programs from Growl for Windows. I've tried removing them from
Growl for Windows' list and re-registering them, but that doesn't
help.

Any tips? Thanks!

[Brian Dunnington]

when you set up the forwarding from your PC to the Mac, did you
manually provide the ip address of the Mac or did you use the Bonjour
auto-discovered listing?

the reason is that the Mac version of Growl does not yet support
encryption. by default, all notifications that are forwarded from GfW
are encrypted, so Growl cant understand them. as a workaround, GfW
will forward notifications that are not encrypted, but only to
instances of Growl on Macs. in order to know if the recipient is Growl
on a Mac, you have to use the forwarding item that GfW detects.

assuming your Mac is powered on and Growl is running, and the two
machines are on the same network, you can click the green + button on
the Network tab to add a forward destination. GfW should auto-detect
the Growl on Mac instance and list it as an option - if you use that
one, the notifications will be forwarded without encryption and then
the apps should be able to register. I have the same setup here and
that is how i have it working.

let me know if that works or if you still have any trouble.

> --
> 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.
>

[Adam]

I installed Bonjour Print Services for Windows v2.0.2 but I still only
saw these four items in GfW's "Forward Notifications" dialogue box:

Click here to manually add a computer that is not in this list
Click here to forward notifications to an email account
Click here to forward notifications to an iPhone via Prowl
Forward to your Windows Phone with Toasty

The Windows IP is 192.168.100.134 and the Mac IP is 192.168.100.105.

But the fact that I was able to see notifications in the "~/Library/
Logs/Growl.log" file indicates that the Mac was able to receive the
notifications just fine and that the encryption was not a problem. Any
other ideas?

[Brian Dunnington]

Which applications are you forwarding notifications from? In order to
be registered on the Mac (and thus be able to display notifications),
the REGISTER request from the PC has to be forwarded as well. Most
apps sent the REGISTER request when they first start up, but some send
it at other times. Maybe if we can identify the apps (or one specific
one for now), we can walk through the process end to end and check
each moving part to see where things fall down at.

[Adam]

Thanks for your willingness to help! I'm using Outlook 2003 and have
the "Outlook" application registered in GfW.

On Feb 21, 10:17 am, Brian Dunnington <briandunning...@gmail.com>
wrote:

[Brian Dunnington]

Ok. Lets walk through it and check at each step to see where the issue is.

1. if Outlook is running, close it.
2. if Growl for Windows is not running, launch it
3. make sure Growl is running on the Mac as well
4. set a password in Growl on the Mac, and then configure the same
password in the forwarding configuration in GfW
5. open the Console on the Mac
6. launch Outlook

At that point, you should get a line that says 'Growl: Outlook
registered' in the Console.

However, if you are not using the Bonjour-discovered instance, then
Growl on the Mac will not be able to parse the REGISTER request and
instead, you will get something more like this in the Console:

Growl: Error occurred ...... Application-Name is a required header.......

If that is the case, then Outlook will *not* be registered on the Mac
and subsequent notifications will not be shown, even if they are
parsed properly. (Growl v1.3.2 may have fixed the parsing issue, so it
may no longer be an issue).

Try all of that and see what you see. Based on what the Console shows,
we can try the next steps.

[Brian Dunnington]

I just double checked and, as of Growl 1.3.3, the password bug is
still not fixed, so you will still have to use the Bonjour-discovered
instance.

[Adam]

Still no luck. Here are some things that might be helpful to know:

Mac:

OS X 10.6.8
Growl 1.2.2

Windows:

XP SP3
Growl 2.0.8 (build: 2.0.8.1)

I have yet to see a Bonjour-discovered item appear in GfW's list of
computers to forward notifications to.

Another application I've been testing with is Windows Media Player
(WMP-GNTP). Here's the Mac's log (the first line is apparently from
when I restarted the Mac's Growl):

Feb 21, 2012 2:06:43 PM Growl registered
Feb 21, 2012 2:08:45 PM ---
Feb 21, 2012 2:08:45 PM WMP-GNTP: "Highway Blues"
Marc Seales, composer. New Stories. Ernie Watts, saxophone.
Speakin' Out () - Priority 0

But, of course, I didn't see this notification displayed by the Mac;
it only got logged by the Mac.

Thanks!

On Feb 21, 1:11 pm, Brian Dunnington <briandunning...@gmail.com>
wrote:

[Brian Dunnington]

Ah - I didnt realize you were still using Growl 1.2.* - that changes things.

Growl versions prior to 1.3 dont advertise themselves over Bonjour for
the GNTP protocol because they dont even support the GNTP protocol;
they only support the older UDP-based protocol. That explains why you
never see the Bonjour-discovered instance.

When you set up the forwarding from the PC, I assume you are telling
to forward using UDP and port 9887 (if not, change it to use those
values). Since you are seeing Growl log stuff on the Mac, you must
have those values set properly.

I am not an expert on Growl on the Mac, but I believe there is a
setting that causes it to log only (not display) notifications. It may
be called 'Hide all notifications' in that version, but I cant
remember (see this image:
http://www.google.com/imgres?q=growl&um=1&hl=en&sa=N&biw=1351&bih=841&tbm=isch&tbnid=CmA7Drfrudg-XM:&imgrefurl=http://www.matwolf.com/apple/how-to-remove-growl-notifications/&docid=aO4JqYMd0XEyKM&imgurl=https://lh4.googleusercontent.com/_QzdUvyDN87g/TXJdKd2Yv4I/AAAAAAAAC-U/aObLeVElYjU/growl3.jpg&w=600&h=430&ei=gkhET4H9EK_YiQKmzenWDg&zoom=1&iact=rc&dur=205&sig=108382169562228352453&page=2&tbnh=139&tbnw=194&start=26&ndsp=30&ved=0CN0BEK0DMCI&tx=77&ty=65)

Do notifications from the local Mac show up fine? You might have
better luck at this point posting to the Growl/Mac support group
instead: http://groups.google.com/group/growldiscuss

[Adam]

I have been using UDP, yes. Also, my Mac programs display Growl
notifications just fine. What I've read is that Growl on the Mac will
display notifications ONLY if the application that generated the
notification is registered with Growl on the Mac. So, although the
Windows notifications are making it to the Mac, because the Windows
applications aren't registered with the Mac, it refuses to display
them. So I thought it made the most sense to post here to see if there
was something I'm doing wrong with registering Windows applications on
the Mac. I could try posting on the Mac side, though. Thanks very
much!

On Feb 21, 5:47 pm, Brian Dunnington <briandunning...@gmail.com>
wrote:

> Ah - I didnt realize you were still using Growl 1.2.* - that changes things.
>
> Growl versions prior to 1.3 dont advertise themselves over Bonjour for
> the GNTP protocol because they dont even support the GNTP protocol;
> they only support the older UDP-based protocol. That explains why you
> never see the Bonjour-discovered instance.
>
> When you set up the forwarding from the PC, I assume you are telling
> to forward using UDP and port 9887 (if not, change it to use those
> values). Since you are seeing Growl log stuff on the Mac, you must
> have those values set properly.
>
> I am not an expert on Growl on the Mac, but I believe there is a
> setting that causes it to log only (not display) notifications. It may
> be called 'Hide all notifications' in that version, but I cant

> remember (see this image:http://www.google.com/imgres?q=growl&um=1&hl=en&sa=N&biw=1351&bih=841...)

[Brian Dunnington]

On the Mac, on the Network tab, make sure you have checked 'Allow
remote registrations' - even if the registration is making it to the
Mac, it may be intentionally ignoring it.

Other than that, each time you launch Outlook (and Growl is running on
the PC), it should forward a REGISTER request to the Mac. Assuming it
is set up to allow remote registrations, then it should register there
as well, which should let you receive future notifications.

[Terrance Hinds, Sr.]

I guess I did something wrong, because I don't have a Mac. I am using
Windows 7 Ultimate 64-bit. Sorry.

[Brian Dunnington]

Terrance -

That message was not in response to you. It was in response to another
person who posted about a different issue. Now that you are registered
with this group, you are probably getting emails for all responses. I
did reply to your question as well, so you should get an email about
that as well.

[Terrance Hinds, Sr.]

Okay and thank you for clarifying that for me. :-)

Thank you,
Terrance Hinds, Sr.

[Adam]

Yeah, I've got that checkbox checked on the Mac. So it's like GfW
isn't forwarding the registration to the Mac or the Mac isn't
accepting it for some reason.

On Feb 22, 7:40 am, Brian Dunnington <briandunning...@gmail.com>
wrote:

> >> >> >>> > To unsubscribe from this group, send email to...
>
> read more »

[Brian Dunnington]

Here is a way to enable some logging in GfW to see if it is forwarding
the message: http://groups.google.com/group/growl-for-windows/browse_thread/thread/1c17687b801efff0/038d1645921177c3?hl=en&lnk=gst&q=logging#038d1645921177c3

After you follow those instructions, close Outlook and relaunch it.
That will cause it to re-register with GfW and also forward the
registration. Then check the logs and maybe that will shed some light
on things?

[Adam]

After setting up GfW logging, I closed Outlook and made sure the "Log"
folder was totally empty. Then in GfW, I clicked the "Applications"
button, right-clicked "Outlook", and clicked "Remove Application".
Then I opened Outlook. Outlook then reappeared in GfW's list of
application and the "Log" folder then had one file in it. This is the
contents of that file:

---------------------------------------------------------------------------
Timestamp: 2/22/2012 10:45:25 AM
Notification Origin: 127.0.0.1 [LOCAL MACHINE]
Displayed using 'Standard'
Forwarding to Mac (UDP 192.168.100.105:9887)


-----------------------------------------------------

GNTP/1.0 REGISTER NONE
Application-Name: Outlook
Application-Icon: C:\Documents and Settings\Adam\Local Settings
\Application Data\Growl Extras\Growl Outlook Add-In\outlook.png
Origin-Machine-Name: ADAM-XP-IE6
Origin-Software-Name: GrowlConnector
Origin-Software-Version: 2.0.0.0
Origin-Platform-Name: Microsoft Windows NT 5.1.2600 Service Pack 3
Origin-Platform-Version: 5.1.2600.196608
Notifications-Count: 2

Notification-Name: Outlook Reminder
Notification-Enabled: True
Notification-Display-Name: Outlook Reminder

Notification-Name: New Mail
Notification-Enabled: True
Notification-Display-Name: New Mail



-----------------------------------------------------

GNTP/1.0 -OK NONE
Response-Action: REGISTER
Origin-Machine-Name: ADAM-XP-IE6
Origin-Software-Name: Growl/Win
Origin-Software-Version: 2.0.8.1
Origin-Platform-Name: Microsoft Windows NT 5.1.2600 Service Pack 3
Origin-Platform-Version: 5.1.2600.196608
X-Message-Daemon: Growl/Win
X-Timestamp: 2/22/2012 10:45:25 AM


---------------------------------------------------------------------------

At the same time, I was watching the Mac's "~/Library/Logs/Growl.log"
file to see if anything got logged, but nothing got logged.

On Feb 22, 8:49 am, Brian Dunnington <briandunning...@gmail.com>
wrote:

> Here is a way to enable some logging in GfW to see if it is forwarding

> the message:http://groups.google.com/group/growl-for-windows/browse_thread/thread...

> >> >> >> >>> >> > a server password set. I've...
>
> read more »

[Brian Dunnington]

Thanks for doing that. So it looks like Outlook properly
re-registered, and the log file says that GfW at least thinks it is
forwarding via UDP to the Mac.

Seeing as how you reported that you were able to see notifications
show up in Growl's log (even though they were not displayed), we can
assume the following:

1. the IP address and port are correct
2. you dont seem to have any firewall/etc issues that are preventing
the network traffic

At this point, there are probably two things you could try:

1. If you have something like Little Snitch on your Mac, you could try
running it to see if the network connection is actually making it to
the make. Alternatively, you could probably try something like
Wireshark on the PC, but it is not exactly user-friendly

2. You could try changing the IP address of your forwarding
configuration to point back to your local PC. That will cause and
endless loop of notifications, but it should verify that the UDP
packet is being forwarded (GfW will receive the UDP packet and handle
it just like Growl on the Mac would have).

[Adam]

I installed Wireshark on the Mac and started watching the Ethernet
port's activity (I'm not using Wi-Fi at all). I used the following
filter:

(ip.src == 192.168.100.134 and ip.dst == 192.168.100.105)

The filter looks for any traffic coming from Windows and going to the
Mac. I left Outlook registered in GfW and then when I opened Outlook,
Wireshark on the Mac saw the UDP traffic, which was apparently an
attempt to register with Growl on the Mac, though nothing got logged
to the Mac's "~/Library/Logs/Growl.log" file.

On Feb 22, 11:09 am, Brian Dunnington <briandunning...@gmail.com>
wrote:

> >> >> >> >> >>> it at other times. Maybe if...
>
> read more »

[darrylo]

On Feb 22, 12:26 pm, Adam <ataylo...@gmail.com> wrote:

> The filter looks for any traffic coming from Windows and going to the
> Mac. I left Outlook registered in GfW and then when I opened Outlook,
> Wireshark on the Mac saw the UDP traffic, which was apparently an
> attempt to register with Growl on the Mac, though nothing got logged
> to the Mac's "~/Library/Logs/Growl.log" file.

Perhaps I'm hallucinating, but I thought the latest Growl on the Mac
dropped UDP support?

[Brian Dunnington]

It did, but Adam said he is using Growl 1.2.2, which is pre-Mac App
Store and pre-GNTP, so it still has UDP support.

[Darryl Okahata]

On Wed, Feb 22, 2012 at 4:09 PM, Brian Dunnington <briandu...@gmail.com> wrote:

It did, but Adam said he is using Growl 1.2.2, which is pre-Mac App
Store and pre-GNTP, so it still has UDP support.

 

Well, in that case, what about the OSX firewall?  (I think you only mentioned that the windows firewall wasn't an issue.)

-- Darryl

[Adam]

The fact that the Mac is logging notifications to "~/Library/Logs/
Growl.log" indicates that it is not having problems *receiving*
notifications. The thing is, it's not *displaying* the notifications.
I believe the cause is that the originating Windows applications are
not registered with Growl on the Mac. I don't know how to get them
registered, though.

On Feb 23, 1:07 am, Darryl Okahata <darr...@gmail.com> wrote:
> On Wed, Feb 22, 2012 at 4:09 PM, Brian Dunnington <briandunning...@gmail.com