The TFTP access is explained in the recovery guide …
You configure a special fixed IP on a computer and start the TFTP server. Apparently, the NAS has a mode, initiated by the one-touch USB button at the front, where it tries to get a FW version from that IP address. That worked, but it didn’t help.
So your NAS has network connectivity. That’s the important thing. You were able to connect to the NAS via the network to do the TFTP work.
Now, we need to figure out why it’s not seen on the network.
What kind of switch do you have? Is it a dumb switch, smart switch or managed switch? Or do you just have a router and no switch?
What happens if you plug the NAS into a different port on your switch/router. Sometimes ports go bad and they can give problems. Or if you have a managed or smart switch with VLANs, if a port gets set mistakenly to a different VLAN, then you won’t see the device either.
The answer is there, we just have to work through things to find it.
Yes, some kind of connectivity is there, but the NAS doesn’t show up on the network. I don’t have any fancy network setup, by the way. No VLANs or managed switches. Just a router and a switch.
For this investigation, though, I used an unused router and connected the NAS directly to it. The NAS does not show up but a computer connected to the router immediately shows in the GUI of the router.
So it’s not the cable or any switch or router configuration. The NAS seems to not ask for an IP address, but after the FW update, it should be in default mode, shouldn’t it?
Perhaps it’s not but the reset to factory settings didn’t work/happen?
Like I wrote above, it doesn’t behave as described in the manual, when you press the reset button 3 seconds or 15 seconds. 15 seconds should reset to factory defaults, but the reset button seems to not do anything. (perhaps I should check, whether it’s properly connected )
No, if it has a static IP address it will not “ask” for an IP. A firmware update doe not change this. A reset would put it back into DHCP mode.
What router do you have? The network map in many Asus routers does not always show devices correctly. Also, in your router, are you actually looking at the DHCP server assignments?
Complicating things by adding another router probably makes troubleshooting worse as you may introduce a second DHCP server and unknown firewall rules. I would try a direct connection, i.e. a single cable, between the NAS and a PC.
It could be extremely important. Any and all information could lead to the answer. Knowing what router brand and model, O/S version, device, all have specific quirks that could be important.
Who says that the NAS had a static IP address? It never did and should still be asking for an IP address - especially when connected to an unknown router.
I have a Fritzbox 7490 and it usually lists all devices connected to them.
You clearly misunderstood … I am using a default router and am connecting the NAS to that router. I am not connecting ANOTHER router to the existing network … jeez
At this point I am trying to get the NAS get recognized in the network, regardless of what OS any clients are running.
Is that reset button the only way to reset the NAS? My guess is that somehow the resets don’t work.
It wasn’t clear one way or another. Just trying to give options and fill in some of the missing information. The more details the better, whether or not you think it is relevant.
Windows 11 doesn’t necessarily show devices on the network that don’t live up to it’s security expectations. It usually applies to older devices that show up OK in Windows 10. There is a workaround but better to check with Windows 10 or mobile app first.
So, let’s say you have a long lease time on your router for DHCP. Let’s say you have a 120 day lease time. Under the DHCP spec, the client device asks for a renewal lease when half the lease is past. So at 60 days, the router would ask for renewal of the address and then it would not as for another 120 days. So if during that 120 day period between lease requests, you cleared all the DHCP information from your router, then the NAS would not necessarily show up anywhere as a “client” of the router. You may be able to see it in traffic logs, etc. but it would not show up as an item that has a lease under DHCP.
Additionally, if the NAS has somehow gone into a self-assigned IP address mode (ie: 169.254.0.0 network), then it would never show up in the router either.
So, yes, there are multiple “worlds” this is possible.
I would take the edge off your posts my friend using verbiage like you are. Also saying things like, “In what world…” All we are trying to do here is help you and you pushing back with language like this effectively accusing us of something. We have no idea and if you want our help, I would suggest you be a little nicer.
Now, I’m not sure why you don’t have a static IP for a NAS. It’s best practice that any server type devices do have static IPs. But that’s your choice if that’s how you want to do it. You did get a self assigned address for your TFTP connection and if that put the NIC on the QNAP into self-assigned mode, you will never get an IP address for it. So it would effectively be static. So yeah, it could have a “static” IP absolutely.
And again, we are trying to help you but we have to ask questions for clarity to help narrow things down. Please stop with the “You should know this” attitude as something in your network/system has changed and it’s no longer working. So it may be the QNAP but it may also be something you did.
Yes, the resets do work. I’ve done it many a time.
Yes, you are soo right and I apologize … I should have re-read what I wrote … I really appreciate you trying to help …
Huh … it would be weird for QNAP to keep that self-assigned IP address, wouldn’t it? I think I read that it would go back to DHCP, but perhaps I will try to reconfigure a router with that specific subnet and see if it’s visible.
Good to know .. but how do you know that the reset worked while performing it? Is the NAS beeping, flashing an LED or something like that?
Mine does nothing .. no beep, no flash, no change in colors … and I have pressed that reset button for at least 30 seconds.
)