Ubuntu iOmega NAS directly connected

Liam Proven lproven at gmail.com
Wed Oct 17 20:14:56 UTC 2012


On 17 October 2012 19:10, Harry de Snoo <hdesnoo at gmail.com> wrote:
> When connected to the router, it was sometimes to be seen, but I could not
> stay connected to it. (On whatever computer I tried), culd not copy files.
>
> Indeed I could use a web based tool on IP 192.168.0.109 before

OK, that is a standard private IP address - anything starting
192.168.x.y is private and will not travel over the public Internet.

(The others are 172.31.x.y for a private network of up to 65,535
machines and 10.x.y.z for a private network of up to 16 million
machines. Many people use 10.x.y.z for small networks as it is easy to
remember.)

> Edited the connection and added that IP to 169.254.6.145.

This one is an automatic address. That means it is in the special
range for when no server was available to assign an IP address to the
device. (E.g. when you connected your NAS box directly to your PC with
no router in the middle.)

If you have a router or other DHCP server available, the 168.x.y.z
address should disappear.

> When I ping, I get response from both..

So the device is still working at some level. That's good.

> But in Firefox I cannot get a respons from both IP's
>
> Suggestions?

It sounds like a problem with the NAS to me. Do you have any other
computers you could use, to verify that although it responds to Ping,
it does not respond to any web browser?

If it is a problem with the NAS, then your options are:

* find out if there is some proprietary setup/config tool that you can
use to talk to the NAS.

Snag: this probably means using Windows. :¬(

* Google to see if this is a known problem.

I would do this for you, but you have not specified a model number or
anything for the Iomega device.

* see if there is a reset button or some other kind of factory-reset
command or control.

Snag: this potentially might wipe all your data.

* If you can get control of the device, perhaps via an Iomega Windows
tool, then you could try upgrading its onboard firmware. This often
resolves many problems with network-attached devices.

P.S. Please bottom-post on mailing lists like this one. Your reply
should go /under/ the text you are answering.

-- 
Liam Proven • Profile: http://lproven.livejournal.com/profile
Email: lproven at cix.co.uk • GMail/G+/Twitter/Flickr/Facebook: lproven
MSN: lproven at hotmail.com • Skype/AIM/Yahoo/LinkedIn: liamproven
Tel: +44 20-8685-0498 • Cell: +44 7939-087884




More information about the ubuntu-users mailing list