[Help] For connecting TNAS to respond to assigned subnet IP address

[petrose]

According to the screenshot information above, when the IP address of the NAS is set to 168.254.44.88, it can be accessed normally; however, when it is changed to 192.168.86.101, access becomes impossible. I suggest that you first check the network address configuration of your computer. Additionally, considering that there may be some delays in forum responses, to resolve your issue more promptly, you can visit the official website and contact the online customer service through the live chat feature. At the same time, send them this forum post so that they can quickly follow up and handle your problem.

Well, let me explain the process.
In order to connect to Control Panels, I need to cable (ETH) from my laptop to the F8 SSD device.
Opening TNAS PC then shows these two rows, one with 192.168.86.101 as status Offline, and one line of same IP with status Ready (see screenshot attached).

Then, in order to login to get to the Control Panels, i get a Prompt to change IP address to something like 168.* (local ETH subnet to my laptop).
Then, I can open the unsecure http login (using my admin account), using this 168.* something. See:

Then I can get to the Control Panels, such as Network, Disks etc. shown here:

My TNAS PC also show something:

Now, all my other network devices runs fine on my subnet 192.168.86.*, as seen here:


In order to get F8 SSD back to my wired 192.168.86.101, I need to change the IP Address back from 168.* something, to the static address.
Then re-cable, by removing Laptop cable from F8 SSD, and instead have cable from router+switch inserted to F8 SSD device. Waiting a few moments, the network light turns green again.

Nothing happens, Cannot ping device (all Firewalls unblocked) its not showing itself on the network layer.
Tried to change from the black cable that came along with device, to another I have - same result.

What is peculiar or interesting, is when I look at the network while it was cabled to my laptop, using arp -a command, I see the following:

where MAC address of the F8 SSD : 6c-bf-b5-04-95-79
shows up with two IP Addresses of which 192.168.86.101 is seems available for the ETH network, but still unpingable.
In addition, when looking at my miniswitch to which I am connecting F8 SSD and other stuff, the Eth interface acts differently !
The middle led light for the F8 SSD connector (sorry MP4 is not allowed, so see the GIF): Almost not blinking, whereas other Eth connectors blinks every second or so:


So to me the F8 SSD Plus device is 'bricked', as I cannot use it for intended purposes

[CursaYang]

You can try connecting a monitor to check the current status of the F8 SSD Plus, record a boot-up video, and send it to the support email.
If you can log in via the monitor, you can enter 'ip a' to view the current device IP address.

[petrose]

You can try connecting a monitor to check the current status of the F8 SSD Plus, record a boot-up video, and send it to the support email.
If you can log in via the monitor, you can enter 'ip a' to view the current device IP address.

I connected my LED TV as console to device, but after boot sequence (several pages), it stops with a login prompt.
As a console without keyboard, I have no way of entering my login details:-(

I do not have standalone keyboard nor screen to debug this F8 SSD.
if you have other means for me to assist your debugging, then let me know. I doubt a remote controlled session to my laptop will help, unless you will be able to fix it by looking at the Locally Attached TNAS using my TNAS PC and Browser session.

If I need to spend more time on this very looong attempt to get it working, I need a confirmation that I can return it after Amazon deadline and still get my money back.

[CursaYang]

Is your network set to DHCP or static IP? It seems like the NAS did not obtain an IP address.
To resolve your issue more quickly, we need to perform a remote diagnosis. Please go to the official website's live chat to book an engineer for remote assistance, and include the link to this post when making the reservation.

[petrose]

Is your network set to DHCP or static IP? It seems like the NAS did not obtain an IP address.
To resolve your issue more quickly, we need to perform a remote diagnosis. Please go to the official website's live chat to book an engineer for remote assistance, and include the link to this post when making the reservation.

It set to Static IP: 192.168.86.101 not using DHCP. Of course when moving to locally attached, I need to change IP address, and reverse when connecting to LAN.
How do you envision a remote engineer can assist when my device doesn't show up on LAN - not even my router can see it ?

BTW. I have ordered at HDMI to USB Camera capture, so I can use my laptop as console to the TNAS..

[TMzethar]

Is your switch network missing a DHCP server? If you insist on manually setting the IP information for the NAS network interface, don't forget to include the gateway and subnet mask. (If you are unsure how to set it up, refer to the network configurations of other devices under the switch network.)
If your switch network has a DHCP server, it is recommended that when connecting directly to a PC, you set the NAS's network interface to DHCP (although this will lose normal connectivity with the PC soon). Then connect the NAS to your switch network, allowing the DHCP server to automatically assign IP information, at which point the network port configuration is generally usable.