meteohub.de

Hi,
I finally got my WMR100-NSLU2-Meteohub-WD working but then decided to move the equipment.
I clicked on the Shutdown button in the Maintenance section of the Meteohub web interface,
disconnected everything, moved it, hooked everything back up same as before, powered up
the NSLU2 and now I am unable to browse to the Meteohub. I was also seeing it in my network
before the move but can't now. I can ping it. Actually I can ping it with two addresses, the one
dished out by my router and the emergency one (192.168.1.77) mentioned in the manual.
I can see it using the Linksys EasyLink software that came with my router but just can't
browse to it. Any help would be greatly appreciated. What a let down after finally getting everything
working.

Thanks

May be you already have it, but check this:

The PC from where you want to browse needs to be in same IP rang than meteohub IP. Do you have it ok?

Chill,

Thanks for the quick reply. It is mysteriously working now. Last night after the move I tried rebooting it a couple times with no results. I powered down last night and left it powered down. This morning I powered it back up and still could not connect. I just rebooted it again a few minutes ago and it is now working. Weird!
Have any ideas why?? No changes to my network setup.
I do not understand. I almost hate to ever power it down again.

Well here we go again. I accidently unplugged the NSLU2 and now I'm unable to get to the web interface. I've always used the 192.168.1.101 address to access it but now I can't even ping it. I can ping 192.168.1.77 and that address also shows in the Linksys Easylink Advisor for it but I can't access it using that address either. I have noticed though that when it boots up it doesn't give me the beeps for the ip address. This is the same as before before it finally booted up normally.
Any ideas?
Thanks in advance

As of yesterday evening it is working again. I can't tell you how many times I rebooted the thing but the last time I unplugged the USB connection to my WNR100 before powering it up. No idea if that was the fix or not but I'll definitly try that first next time.