Router changed TrueNAS IP address

[fbred24]

I have been successfully running FreeNAS 11.2 since 2019, but very much a novice.
ASRock C275004l motherboard with Intel Octa Core Processor, 16Gig Ram, with five WD 4T HDD.

Linksys WRT 1900ACS router assigned IP 192.186.1 20 to FreeNAS PC, always accessible by another network PC via browser.

IP assignment has changed:
192.186.1.20 no longer shows on Linksys Network Map, and is not pingable.
-- attempt at logging in via browser times out

192.168.1.191 was created by router for the FreeNAS PC instead, and looks like it is representing the motherboard,
named AMID0509... , rather than the FreeNAS program.
It is pingable.
-- attempts to log in as root with password fails

I am wondering if router resetting, or changing of which pcs were connected to which ethernet ports, caused IP reassignment?

If I do direct keyboard, mouse, monitor connection to FreeNAS pc, it will boot up, scroll through files, and end with the menu to choose 14) options.
If I type any of these fourteen numbers and hit Enter, nothing happens. So I can't work with IP assignment, or start PowerShell.

Windows 10 File Explorer still seems to know about FreeNAS, but it is not accessible.

Any thoughts on what caused IP change, and or how I might regain control would be appreciated.

 

[Whattteva]

Looks like from your NAS console, the IP is still 192.168.1.20.

Also, your NAS console shot shows that you hit 9 (for shell) and it successfully drops you into the shell, but then you attempted to keep hitting the number options in the shell, which will not work.

To go back to the option prompt, you have to type exit first at the shell, which will then send you back to the options prompt.

I am not sure what your first screenshot is detecting, but your NAS does not agree with it and still states that its ip is 192.168.1.20.

On the shell prompt (the number 9 option), could you type in ifconfig and post its output here?

 

[Redcoat]

I am not sure what your first screenshot is detecting,

I'd guess that's the motherboard's BMS.

And, of course, this is one of the motherboards as used in the FreeNAS Mini that had the processor/chipset problem much discussed here. I imagine that it may be on its last legs...

See https://www.truenas.com/community/threads/how-long-did-your-asrock-c2550d4i-or-c2750d4i-last.45445/

 

[fbred24]

Thanks Whatteva for the heads up about using shell correctly. I will study up. Attached is ifconfig

 

[Zedicus]

192.168.1.191 was created by router for the FreeNAS PC instead, and looks like it is representing the motherboard,
named AMID0509

that is the IPMI interface. first thing to check is the physical cable and make sure it did not accidentally get moved to the IPMI network port, on the NAS.

AFTER THAT:
if it is not working, on the NAS press 9 for console and enter the command 'ifconfig' no quotes.
that will tell us what, and if, the nas has for an IP.

 

[fbred24]

Thanks Zedicus, exactly, the cable was plugged into the IPMI port.
Placed cable in correct LAN 1 port, and everything working normally directly, and via browser at 192.168.1.20
In the ifconfig photo, what identified IPMI ?

 

[Zedicus]

In the ifconfig photo, what identified IPMI ?

actually it was this. IPMI shows up on the network as something pretty obvious based on the vendor (well, i have been in I.T. for a long time)

named AMID0509

and always remember, check the easiest things first.