Lacie D2 Network VK2 Help

[fvdw]

nothing wrong with your d2, something disturbs the communication between nas and PC, are you using a wireless connection between pc and router ? If yes this can be the cause of transmission abort. Use a wired connection.
Second what does the tftpd32 window shows when you try uploading the image ? and is there any data in the log viewer of the tftpd32 server ?
If auto upload goes wrong we could try to do manual loading step by step but if uploading of the kernel fails very likely you also will get problem to upload firmware files. So first we should solve the communication problem

[macgyver76]

nothing wrong with your d2, something disturbs the communication between nas and PC, are you using a wireless connection between pc and router ? If yes this can be the cause of transmission abort. Use a wired connection.
Second what does the tftpd32 window shows when you try uploading the image ? and is there any data in the log viewer of the tftpd32 server ?
If auto upload goes wrong we could try to do manual loading step by step but if uploading of the kernel fails very likely you also will get problem to upload firmware files. So first we should solve the communication problem

I confirm, only lan cable connection, wifi is disabled.
The tftpd32 window but it does not show anything both before and during the image file upload. Same thing in the log viewer....all empty.

[fvdw]

tomorrow I will post some instructions for manual loading.
One question what is the ip pool your dhcp server is using ?
The netmask must be set to 255.255.255.0 to allow all ip's in range 192.168.1.xxx to be accesible. (xxx being 1--254).
If the pool is limited and doesnot contain 192.168.1.252 the nas cannot contact your pc as is ip is outside the allowed range.

[macgyver76]

tomorrow I will post some instructions for manual loading.
One question what is the ip pool your dhcp server is using ?
The netmask must be set to 255.255.255.0 to allow all ip's in range 192.168.1.xxx to be accesible. (xxx being 1--254).
If the pool is limited and doesnot contain 192.168.1.252 the nas cannot contact your pc as is ip is outside the allowed range.

It is no longer necessary... I solved everything.
I do not know exactly what the real cause was, certainly a strange installation of Windows 10 (damn!) prevented communication even if the firewall was apparently off. In any case the important thing is to have succeeded. Now everything works.
Two last questions:
- the firmware version installed is 18.3, I remember seeing somewhere (but I do not remember where) there are patches to apply. Is it necessary to apply them?
- If I wanted to remotely shut down the NAS is there a command to send to its web page or to send the shutdown via ssh?
thanks

[Jocko]

Hi

- If I wanted to remotely shut down the NAS is there a command to send to its web page or to send the shutdown via ssh?
thanks

You can do it by using an url and youou have to open the web server port on your ISP box from WAn side. Of course it will be better if you enable https protocol because credentials can be sniffed on the request if you use http protocol. (So 443 or custom port) : https://plugout.net/viewtopic.php?f=26&t=3040#p30966From LAN, you can use local ip or nas name for nasip and from WAN use your public ip or your DDNS

And you can also also open the ssh access port (22 or custom port) and it will be better to use authentication by rsa key. After opening a ssh window, the commands are

Code: Select all

sync
standbyd-spd

(sync to synchronize the disk cache before halting the nas)