plugout.net

I'm far from home and after several weeks of usage of the Lacie cloudbox from remote, either by webdav\ftb, admin console access etc all went smooth till the today attempt of connection timed out.

I called a friend and he managed to tell me the ip of the router (which I then checked against the dynamic DNS IP I was seeing on my end and they matched), I asked then to reboot the device and I've been told that when it is starting there is 1 red led blink and then nothing. Disks are spinning and the ethernet light on the back of the device blinks too so it's communicating with the router I guess.

Port forwarding and relative router configurations are unchanged.

What may have happened? :thinking
Can I somehow remotely troubleshoot the issue? It's already a miracle I managed to get the ip of the router, asking him to locally access the NAS admin panel I think it's already too hard for my friend ^^

Hi Maxride,

I am sorry but it not fully clean for me :

Maxiride wrote:t's already a miracle I managed to get the ip of the router, asking him to locally access the NAS admin panel I think it's already too hard for my friend

Do you mean your friend can open locally fvdw-sl web-interface ?

if Yes, I see at least one explanation, the NAS has a new IP on your LAN (for example if it gets its IP from the DHCP server of your ISP box) and then the port forwarding rules are broken.

Did he try to reboot the ISP box? some box may be hanged after a long running time.

Regarding the unclear quoted part:

Initially I though that there was something wrong with the dynamic dns update, so I went to http://www.dyns.cx/ (the dynamic dns service I'm using) and checked what IP was registered. My friend already had access to the router's wifi so I simply asked him to connect to the home wifi and just type "what's my ip" on google, this way I ensured that the dynamic dns I was seeing is synced to the actual router ip.

Jocko wrote:Do you mean your friend can open locally fvdw-sl web-interface ?

Since I manually set the static IP I asked him to type it in the browser and he said that the browser responded with "address unreachable"

Jocko wrote:if Yes, I see at least one explanation, the NAS has a new IP on your LAN (for example if it gets its IP from the DHCP server of your ISP box) and then the port forwarding rules are broken.

The fvdw firmware was setup to use a static IP address and there is nothing else connected to the router at the moment, except for my friend smartphone when he did the test.

If I'm lucky enough I can manage him to turn on my desktop pc at home and install teamviewer so I can do some changes like if I was there for the network.

So if you can not connect locally to fvdw-sl web-interface that means the issue is the NAS (maybe the boot-loader failed to detect the disk)

And only a local access will allow you to investigate the issue.

Jocko wrote:So if you do not have an access locally that means the issue is the NAS (maybe the boot-loader failed to detect the disk)

And only a local access will allow you to investigate the issue.

Once I manage to get a remote "local access" for instance using team viewer to connect to my local desktop computer at home what should I try to do?

My friend while connected to the local network didn't managed to load the login screen by typing the static (local 192.168.1.x) IP address of the nas.. :scratch

Is the blue led not on when the nas has powered on?
The red flash could come from bootloader if it can not load the firmware. If the blue led stays off after boot is completed most likely you have a disk problem

fvdw wrote:Is the blue led not on when the nas has powered on?
The red flash could come from bootloader if it can not load the firmware. If the blue led stays off after boot is completed most likely you have a disk problem

Thanks for the hint, I'll try to check that!