ping to an outside host can fail for a multitude of reasons, only a few of which actually say anything useful about the state of your own network.
As a first step, open a terminal window and type
ip route ls
You should see an output along the lines of
shadur@equinox:~$ ip route ls
192.168.15.0/24 dev eth0 proto kernel scope link src 192.168.15.102
default via 192.168.15.1 dev eth0
This indicates that your local network is an ethernet connection (
eth0) with the address
192.168.15.0, and that its default gateway through which it accesses the rest of the internet can be found at
Next, you can try to
ping that address:
shadur@equinox:~$ ping 192.168.15.1
PING 192.168.15.1 (192.168.15.1) 56(84) bytes of data.
64 bytes from 192.168.15.1: icmp_req=1 ttl=255 time=0.352 ms
64 bytes from 192.168.15.1: icmp_req=2 ttl=255 time=0.269 ms
--- 192.168.15.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1000ms
rtt min/avg/max/mdev = 0.269/0.310/0.352/0.045 ms
If you see something similiar to the above, your own local network is, at least, fine. At this point you can start looking with more advanced tools like
traceroute to see where your connection to the destination might be failing.
However, after a quick google check of what
growl is actually supposed to be I get the feeling that there's something else going wrong. Can you expand your question to give us a few more details on what you're trying to do, how you're attempting it, and the full error output? The line you're currently giving us gets cut off abruptly...