Intel NUC12WSHi3 ROCK installed….. network address “ lost “

Intel NUC12WSHi3
.m2 256gb SSD ( Rock OS )
16gb SoDimm Mem.
2Tb SSD HD ( Internal )

Rock successfully installed on Intel NUC12 256gb SSD.
USB stick removed as prompted and NUC restarted. Network address as shown on screen ( 192,168.1.43 ) entered into iPad ( same network )

Information screen displayed on iPad including ? Mark for Codecs, network address and option to format internal SSD HD.
2Tb internal SSD HD formatted OK confirmation.

NUC restarted and Network address now showing. 192.168.8.143 ; unable to log in.

FAQ checked and resetnetwork command used. Network reset message displayed. Network cable removed and reattached but still showing 192.168.8.143.

USB stick inserted and ROCK new install repeated. Same network address 192.168.8.143.

Any suggestions on how to get back to 192,168.1.xx network address please.

Have you got multiple subnets in your home network?

Is that an IP assigned when the device fails to see the DHCP server? I’d try a different cable or plug it direct into your router and see if that works. If it does you’ll need to troubleshoot your network.

Normally a DHCP failure results in an 169.254.x.x address, I believe…

3 Likes

No subnets.( I don’t think ) Just a router and 1x 4 port hub plus 2x 8 port hubs all in different rooms: each hub wired directly to the router.

Clarification… hubs or switches? Can you post the model numbers? Thanks.

1 x 5 port & 2 x 8 port Switches ……sorry.
Netgear GS308 x2 ( 8 port )
BUFFALO LSW6 x1 ( 5 port )

Hmm.

I’m not a networking dude, just some guy who has troubleshot similar issues.

  1. what device is your rock plugged into?
  2. Do you know what device is handling out IP addresses (acting as a “dhcp server”)? Is it possible that two different devices are trying to do this?
  3. Can you check your router to see what devices are registered and the IP ranges (the a/b/c in a.b.c.d)? If that’s gibberish… Do you have Unifi WiFiMan or some other device detector you can run on your phone to see whether there are other devices with similar addresses?

Thanks.

Will try a different cable or direct router connection tomorrow.

I can not find good details on the Buffalo device but it says something about a “switching hub”, so I suspect it is the issue. Unless of course, there is another device that has not been mentioned that is also serving up IPs.

As far as I can tell the two Netgears are unmanaged switches and shoul dbe fine to connect the NUC to and not have any IP issues.

My suggestion is to remove the Baffalo from the branch the NUC is on and see if that “fixes” it.

Will reply tomorrow as it’s almost midnight here in Japan, sorry.

1 Like

2 ideas.
Any rogue device that acts as an (unwanted) additional DHCP server on your network?
And - have you power-cycled all network components?

1 Like

Good morning @Derek_W
I cannot know for sure since you didn’t share anything about the make and model of your router and how internet gets into your home:
Is there an ISP modem that your wifi router is connected to via lan cable?
If so, both devices may have assigned an IP address from a different address range.
However, this is pure speculation and if you stick to the known facts, according to them this should work:

Your iPad connected via WiFi and the NUC via LAN do not have an address from the same IP adress range.
So connect the NUC via LAN port to the same device that the iPad is connected to (via Wifi => your Wifi router).

If both devices still can’t see each other, it is either due to the DHCP server not being configured right in the router or to a faulty network interface controller in the NUC.

I have this same NUC model installed with ROCK. I can’t solve your problem but I can tell you what happens when a defective Ethernet cable is attached.

Last week I moved the NUC from my hifi cabinet to my computer closet using a cat 5 cable from my box-o-cables into my main switch. I could not detect it on boot and noticed the Ethernet jack on the back was not blinking at all.

I attached a monitor and on boot I don’t remember exactly what it said, but it made it obvious that it could not acquire an IP address via DHCP. Replaced the cable and rebooted and everything worked, lights blinking as they should be and the console output showed clearly that it was able to acquire an IP address.

This address is being handed out via a DHCP server somewhere on your network. Most routers have DHCP servers. You need to identify every “router” in your network. I would go so far as to unplug everything, take a pc, plug it directly into your internet connected router and verify what address it hands out. Then plug in the next thing, plug into that, re-verify (reboot the pc).

This might take time but if you expect your network is 192.168.1.x then you need to figure out where this 8 network is coming from.

1 Like

Our setup in Japan is as follows:

Japan NTT provided Optical Fibre into our house connected to a Router which is a NTT PR-500Ki with its own plugin Wi-Fi dongle ( NTT SC-4ONE (2) ) The router has a dedicated slot for this wireless dongle.

The router has 4 lan ports of which 3 are used for the 3 switches mentioned ( Buffalo LSW6-GT-5EPL & 2x Netgear GS-308 )

Router is 192.168.1.1 and has been since installation 2 yrs ago. Addressees for all wired and wireless equipment are 192.168.1.xx

NUC Lan cable was attached to the Buffalo switch located in our lounge. Changed cable but NUC still no change of address 192.168.8.xxx.

NUC moved to Netgear switch and address reverted back to 192.168.1.43 so problem solved. So I will replace the Buffalo switch with a Netgear.

Thank all for your hints and help.

2 Likes

I didn’t lookup what the buffalo device was but “switching hub” was one of the various terms of a set of nightmare devices introduced around the time switches were becoming a thing. They worked as follows…

They had a 10 megabit hub and a 100 megabit hub connected to all ports and any port could be set to attach to either hub. The two hubs were “bridged” onto an internal 2 port switch.

This allowed for a lot of 10/100 megabit ports while utilizing a very cheap 2-port switching architecture. They “worked” but were slow, had high frame loss, high latency, only supported half-duplex, and generally were poor performers. But, back in the day, a switch was high hundreds to thousands of dollars and router ports cost more. If you just needed a way to bridge your 10 megabit network to your 100 megabit network this was the cheap way.

2 Likes

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.