What's new
  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

I Who Know Nothing Seek Network Help Please.

Saltrams

New Around Here
Greetings. This is about a NAS but I think it is more of a LAN specific problem. Trouble is, unless something just works or I have detailed instructions, I haven’t the first clue…
I have an Asustor 7004T NAS. It was all working fine. Then I moved house, got a new ISP (Starlink, with Gen3 modem, in case that’s relevant) and plugged my NAS into the modem. It took unusually long to boot but once it did, I was able to see all the content using Windows Explorer on the same laptop that I used in the old house.
However, I can’t access the AMD (OS) & admin of the NAS. I can’t get into it via Web GUI, the proprietary Asustor App reports it can see the NAS but can’t access it (the IP address is shown as the old one as in my old house) and it reports the NAS has a “different subnet”.
Also, the Starlink App shows the NAS in its device list with a different IP address to the one it had before but it isn’t accessible no matter what various IPs I try.
Back in the old house, I did change the default access ports but I know those numbers & it doesn’t help.
Starlink reports the IP is 192.xxx.x.254. Starlink’s subnet is shown in the App as 192.xxx.x.1/24 (which to my amateur eye is outside of the range of the NAS’s IP ending 254) and it says “[This is an] advanced feature that changes the IP addresses assigned to your devices. Most users [that’s me!] should use the default.” Hence, I’m not just altering the subnet rashly to see what happens!
Could the IP address for the NAS in the old house be “static”? which I somehow set myself (or it just did it itself) but then why would Starlink give it another, different one and one outside of its own subnet range? That makes no sense.
So, I hope I’ve described everything properly; does anyone know what’s amiss & how to fix it please?
 
Starlink reports the IP is 192.xxx.x.254. Starlink’s subnet is shown in the App as 192.xxx.x.1/24
If these are 192.168.x.x, there is no need to hide them here in the post. /24 is OK as long as the first 3 parts of the IPs match.
 
Oh, OK thanks. I thought it best to put x as I didn’t know if it was important.
I’d be pleased to know why /24 is OK when .254 is outside that number, just for the learning value. However, it means that the subnet isn’t the problem so now I have no clue as to what could be wrong 😞
 
192.168.1.1/24 belongs to the subnet with the range 192.168.1.0 - 192.168.1.255. Look up “CIDR calculator” online and it might do a better job explaining it than me.
 

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Back
Top