Can not connect or ping rune.local or IP

[Goomba79]

Hello,

I am having a bit of trouble with getting rune audio up and running on my home network.
I can see my Pi in the DHCP list on the router, however i can't browse to it using rune.local or the IP address, if I ping it all packets are lost.

I know that my install is ok as I tested it at work, and could navigate to the web UI over both a wired and wireless connection.

I have a Model B Pi and using the RuneAudio_Pi_0.2-beta build
My router is a virgin media superhub.
Are there any settings in there that need modifying?

Thanks,

Iain

[dnaman]

Iain, if it's of any relevance, I find that it takes a bit of time (maybe a minute .... guess) to actually open the webserver on the RPi when you browse to it. I presume you are waiting long enough?

It almost caught me out the first time.

[Goomba79]

Hello,
Yeah I've left it a good 5 minutes and still no joy.
Both the 01 and 02 builds work fine on my network at work.

As the 02 doesn't register on my home router at all I have gone back to the 01 build, that at least gets allocated an address (192.168.0.16) and is on the same subnet as all my other devices.

However I cannot ping it from the router.

As I can remote into it when on my domain at work it leads me the think it's something with my virgin superhub?!

It is extremely annoying

[crimius]

I'm having the same problem. Can't cannot to RuneUI webserver on RaspPi.

Any advice out there?

Thanks in advance

[crimius]

I can see it on my router and I can ping the IP. But I can't get the RuneUI web interface. Both Chrome and Firefox say the connection times out or could not connect to.