Growl messages not forwarding from PC to mac
Ed
from a PC to mac http://www.growlforwindows.com/gfw/help/forwarding.aspx
specifically the forward to mac section, and it is not working. I have
set all the settings exactly as they explained in the tutorial. I
enabled the debug logging on the PC and it says that the growl is
successfully being sent to the other machine. Here is an excerpt from
the beginning of the log file
Timestamp: 9/27/2011 11:59:45 PM
Notification Origin: 127.0.0.1 [LOCAL MACHINE]
Displayed using '[Default]' (TranslucentDark)
Forwarding to mbp (UDP 192.168.11.5:9887)
I am using the UDP protocol on port 9887 as required to send to the
mac. I believe the problem to be on the mac side. I made sure that the
mac firewall was off and I checked list of open internet files using
lsof -i and i get the following for the growlhelp app
GrowlHelp 443 home 5u IPv6 0xffffff80172738c0 0t0 UDP *:9887
GrowlHelp 443 home 8u IPv4 0xffffff8016cd25e8 0t0 TCP *:
23052 (LISTEN)
It looks like growlhelp is listening on the TCP port when it should be
listening on the UDP port. I couldn't find any way to change this in
the growl settings so I was wondering if there was any way to switch
the listening port to 9887. I also tried sending a message on port
23052 (which is weird because windows says the GNTP protocol uses
23053) and 23053 but it did not work either. Can anyone offer any
help? Thanks!
P.S. specs of the machines:
Sending machine:
Windows 7 Pro desktop running Growl 2.0.7.2
Receiving machine:
Macbook Pro OS X 10.6.8 running Growl 1.2.2
Chris Forsythe
--
Chris Forsythe
--
You received this message because you are subscribed to the Google Groups "Growl Discuss" group.
To post to this group, send email to growld...@googlegroups.com.
To unsubscribe from this group, send email to growldiscuss...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.
Ed
like I have tried a lot of different settings in both clients and I
have had no communication between the two.
On Sep 30, 4:07 pm, Chris Forsythe <ch...@growl.info> wrote:
> GrowlTalk, the udp protocol, has never really worked right in general. For some, it works great, for others it doesn't. We've removed GrowlTalk from 1.3 and replaced it with GNTP. Honestly it's a matter of just continually messing with Growl in order to get it to work otherwise for 1.2.2.
>
> Chris
>
> --
> Chris Forsythe
>
>
>
>
>
>
>
> On Thursday, September 29, 2011 at 7:41 PM, Ed wrote:
> > I have followed this tutorial on how to forward growl notifications
> > To unsubscribe from this group, send email to growldiscuss...@googlegroups.com (mailto:growldiscuss...@googlegroups.com).
Chris Forsythe
> To post to this group, send email to growld...@googlegroups.com.
> To unsubscribe from this group, send email to growldiscuss...@googlegroups.com.
Patrick
I have the latest version of GfW installed and the latest of Growl
(1.3.1) and I can't get notifications forwarded properly. We had a
ruby script written to forward before and it worked with 1.2.X but
since the upgrade, no dice.
Any thoughts? It should all be on GNTP now, correct? And I can forward
from Windows on a network 10.1.22.X to 10.1.11.X so it isn't a
networking issue like I had thought or a firewall issue on either
side.
Also, we have the ruby script continuing to forward to a chat client
and that still works to my Mac, but the Growl, no.
Patrick
On Oct 1, 9:12 am, Chris Forsythe <ch...@growl.info> wrote:
> Checking things and then unchecking. Disabling firewalls is another thought.
>
>
>
>
>
>
>
>
> > Could you give some specifics on "playing around with Growl?" I feel
> > like I have tried a lot of different settings in both clients and I
> > have had no communication between the two.
>
> > On Sep 30, 4:07 pm, Chris Forsythe <ch...@growl.info> wrote:
> >> GrowlTalk, the udp protocol, has never really worked right in general. For some, it works great, for others it doesn't. We've removed GrowlTalk from 1.3 and replaced it with GNTP. Honestly it's a matter of just continually messing with Growl in order to get it to work otherwise for 1.2.2.
>
> >> Chris
>
> >> --
> >> Chris Forsythe
>
> >> On Thursday, September 29, 2011 at 7:41 PM, Ed wrote:
> >>> I have followed this tutorial on how to forward growl notifications
> >>> from aPCtomachttp://www.growlforwindows.com/gfw/help/forwarding.aspx
> >>> the beginning of the log file
>
> >>> Timestamp: 9/27/2011 11:59:45 PM
> >>> Notification Origin: 127.0.0.1 [LOCAL MACHINE]
> >>> Displayed using '[Default]' (TranslucentDark)
> >>> Forwarding to mbp (UDP 192.168.11.5:9887)
>
> >>> I am using the UDP protocol on port 9887 as required to send to the
> >>>macfirewall was off and I checked list of open internet files using
Rudy Richter
stack was removed in 1.3.
one thing to be aware of is that the Mac version does not currently
support encryption so you'll want to make sure that is turned off on
the window's configuration.
the ruby script was using the UDP GrowlTalk implementation? if so
you'll probably want to replace the GrowlTalk implementation with one
of the gntp ruby implementations.
-rudy
Patrick
that is needed.
As far as PC to Mac, are you talking about encryption in the Growl for
Windows application itself? Or encryption on the Windows side? Can you
disable encryption for only GfW?
On Nov 16, 10:53 am, Rudy Richter <r...@growl.info> wrote:
> If you're using 1.3.x on themacthen yes, all GNTP. the old network
> stack was removed in 1.3.
>
> one thing to be aware of is that theMacversion does not currently
> support encryption so you'll want to make sure that is turned off on
> the window's configuration.
>
> the ruby script was using the UDP GrowlTalk implementation? if so
> you'll probably want to replace the GrowlTalk implementation with one
> of the gntp ruby implementations.
>
> -rudy
>
> On Nov 16, 9:50 am, Patrick <pdg...@gmail.com> wrote:
>
>
>
>
>
>
>
> > Hi Chris,
>
> > I have the latest version of GfW installed and the latest of Growl
> > (1.3.1) and I can't get notifications forwarded properly. We had a
> > ruby script written to forward before and it worked with 1.2.X but
> > since the upgrade, no dice.
>
> > Any thoughts? It should all be on GNTP now, correct? And I can forward
> > from Windows on a network 10.1.22.X to 10.1.11.X so it isn't a
> > networking issue like I had thought or a firewall issue on either
> > side.
>
> > Also, we have the ruby script continuing to forward to a chat client
> > and that still works to myMac, but the Growl, no.
briandunnington
Since the Growl on the Mac doesnt support encryption yet, that caused
forwarding to break (and since UDP has been removed, that is not a
fall-back option).
However, in the latest version of GfW (2.0.8, released today), there
is a work-around provided. If you use the instance of Growl that GfW
auto-discovers via Bonjour, GfW will forward the notifications without
encryption and PC-to-Mac forwarding will work again. When Growl
supports GNTP encryption, this workaround will no longer be necessary.
- brian
ps: to use the auto-discovered instance, open GfW, go to the Network
tab, and click the green + on the left side. If you are running Growl
1.3.1 on the Mac, it should be auto-detected and you can just click on
it and enter your Growl password and be all set.
On Nov 18, 9:41 am, Patrick <pdg...@gmail.com> wrote:
> Okay. I'll take a look at our script and see if that was the change
> that is needed.
>
> As far as PC to Mac, are you talking about encryption in the Growl for
> Windows application itself? Or encryption on the Windows side? Can you
> disable encryption for only GfW?
>
> On Nov 16, 10:53 am, Rudy Richter <r...@growl.info> wrote:
>
> > If you're using 1.3.x on themacthen yes, all GNTP. the old network
> > stack was removed in 1.3.
>
> > one thing to be aware of is that theMacversion does not currently
> > support encryption so you'll want to make sure that is turned off on
> > the window's configuration.
>
> > the ruby script was using the UDP GrowlTalk implementation? if so
> > you'll probably want to replace the GrowlTalk implementation with one
> > of the gntp ruby implementations.
>
> > -rudy
>
> > On Nov 16, 9:50 am, Patrick <pdg...@gmail.com> wrote:
>
> > > Hi Chris,
>
> > > I have the latest version of GfW installed and the latest of Growl
> > > (1.3.1) and I can't get notifications forwarded properly. We had a
> > > ruby script written toforwardbefore and it worked with 1.2.X but
> > > since the upgrade, no dice.
>
> > > Any thoughts? It should all be on GNTP now, correct? And I canforward
> > > from Windows on a network 10.1.22.X to 10.1.11.X so it isn't a
> > > networking issue like I had thought or a firewall issue on either
> > > side.
>
> > > Also, we have the ruby script continuing toforwardto a chat client
> > > and that still works to myMac, but the Growl, no.
>
> > > Patrick
>
> > > On Oct 1, 9:12 am, Chris Forsythe <ch...@growl.info> wrote:
>
> > > > Checking things and then unchecking. Disabling firewalls is another thought.
>
> > > > On Sep 30, 2011, at 8:19 PM, Ed <ejmc...@gmail.com> wrote:
>
> > > > > Could you give some specifics on "playing around with Growl?" I feel
> > > > > like I have tried a lot of different settings in both clients and I
> > > > > have had no communication between the two.
>
> > > > > On Sep 30, 4:07 pm, Chris Forsythe <ch...@growl.info> wrote:
> > > > >> GrowlTalk, the udp protocol, has never really worked right in general. For some, it works great, for others it doesn't. We've removed GrowlTalk from 1.3 and replaced it with GNTP. Honestly it's a matter of just continually messing with Growl in order to get it to work otherwise for 1.2.2.
>
> > > > >> Chris
>
> > > > >> --
> > > > >> Chris Forsythe
>
> > > > >> On Thursday, September 29, 2011 at 7:41 PM, Ed wrote:
> > > > >>> I have followed this tutorial on how toforwardgrowl notifications
> > > > >>> from aPCtomachttp://www.growlforwindows.com/gfw/help/forwarding.aspx
> > > > >>> specifically theforwardtomacsection, and it is not working. I have