Reply

192.168.168.168 stuck

nickelodean
Luminary

192.168.168.168 stuck

Sigh... alas, I am stuck on 192.168.168.168 and can't access ReadyNAS Ultra 6 (RNDU6000). I tried setting up "teaming" and downloaded/installed the add-on from this link - Teaming ReadyNAS Ultra NICs - Blah, Cloud.

Upon doing so, it now goes to subject IP and can't be recognized, or ability to access the admin page to remove the add-on. Any suggestions?

 

Model: RNDU6000 (ReadyNAS Ultra 6)|READYNAS ULTRA 6 (DISKLESS)|EOL
Message 1 of 8
nickelodean
Luminary

Re: 192.168.168.168 stuck

Note that Raidar 6.5, 4.3 could not find it.

I've tried rebooting/restarting, only using 1 NIC, plugging into other ethernet ports to no avail

Model: RNDU6000 (ReadyNAS Ultra 6)|READYNAS ULTRA 6 (DISKLESS)|EOL
Message 2 of 8
nickelodean
Luminary

Re: 192.168.168.168 stuck

Sigh... OS reinstall did not work. same ip

Message 3 of 8
mdgm
Virtuoso

Re: 192.168.168.168 stuck

Do you have a backup of your data?
Message 4 of 8
nickelodean
Luminary

Re: 192.168.168.168 stuck

Ugh... no

Message 5 of 8
mdgm
Virtuoso

Re: 192.168.168.168 stuck

I assume your switch is configured correctly for the teaming mode you chose?

Have you tried connecting just the one NIC?

If all else fails you’d need to use the tech support mode boot menu option and fix it manually using shell commands.
Message 6 of 8
Sandshark
Sensei

Re: 192.168.168.168 stuck

192.168.168.168 is the default if it's set for DHCP and no DHCP server gives it an address.  While I think RAIDar should still find it, I suppose it's worth setting up a computer with a 192.168.168.xxx address and doing a direct connection to see if you can get in.

 

FWIW, the best solution to teaming on an Ultra is, IMHO, conversion to OS6.  But you'll first need access to your data to make a backup.

Message 7 of 8
nickelodean
Luminary

Re: 192.168.168.168 stuck

UPDATE: So I was able to get a fix... sort of (fixed itself??)... at least for my situation.

I turned off the nas for 14 hrs or so... came back to it, and before turning it back on, I turned off a few other devices in the same room that were also on the same network (note that there are multitude of other devices connected throughout the house) and was able to get a new ip address 192.168.86.231. So, the nas is now detectable/viewable. From there I was able to get to the admin page. Thanks also to mdgmnas for his knowledge for going forward from here.

Message 8 of 8
Top Contributors
Discussion stats
  • 7 replies
  • 822 views
  • 2 kudos
  • 3 in conversation
Announcements