Icybox IB-NAS901-B ethernet problem

Hi all,

I've just got myself an Icybox IB-NAS901-B and have got it working just fine via USB. However, I can't get the ethernet port to work whether I connect it directly to my Vista machine, my Ubuntu machine or directly to my router which is a Thompson Speedtouch 716 (which has DHCP enabled).

I've tried every IP configuration I can think of...

I've tried with crossover and straight cables...

The green light is on on both my ethernet port and the ethernet port on the Icybox, which blinks when I first plug it in, but then just remains solid. However, I receive no packets back from the Icybox at any point.

Any help would be greatly appreciated,

Martin

Done some further research using the DHCP server included in TFTP32 and I am receiving no DHCP requests from the box when it is connected directly to my machine...

Reckon it's defective?

The icybox has its own DHCP server - you need to ensure that is disabled. I suspect it is a configuration issue rather than a defect. Can you get to the configuration pages through the USB interface?

Hi peter - thanks for the reply.

No, I don't think so - the configuration pages are web based and seem to require the ethernet connection to be working.

I've tried with and without a DHCP server (ie. I've tried to let it be the server and the client by enabling/disabling DHCP server here) as it should technically work in either configuration mode - if there is no DHCP server it should take a static IP of 169.254.0.1 and then act as a DHCP server - if there is a server available, it should accept the IP address it is given. It definitely is not making a request for an IP address.

As I said, it works just fine in USB mode - got the disk mounted and speeds are good. The only problem is the NAS aspect, which is not working at all and, having spent all day trying every aspect of configuration I can think of, I'm on the verge of giving and sending it back to scan.

Just for the record, I am not trying to use the USB at the same time as the ethernet in case that makes a difference.

Oh, one further piece of diagnostics...

The "landisk" tool (landisk_wtools_V1.1.exe) that came with it also finds nothing.

Have you tried statically assigning your macine an address of 169.254.0.2, for example, and seeing if you can ping it's supposed static address of 169.254.0.1?

169.254.xxx.yyy is the Apipa address rtange that windows machines default to in the absence of either a static IP address or a recogniseable DHCP server. However most devices such as routers and NAS boxes use the reserved class C range 192.168.xxx.yyy or the class A range 10.xxx.yyy.zzz. The Class C address is the most common. (There is also a default Class B address range - but that is rarely used as a default in this type of scenariao)

Have you tried addressing it as 192.168.1.1 or 192.168.0.1 (with netwok mask of 255.255.255.0 in both cases). (You could try 10.0.0.1 with subnet mask of 255.0.0.0)

Hi,

Thanks for the replies.

Viper81: I've tried assigning myself several IP addresses (169.254.0.x, 192.168.0.x and 192.168.1.x) and still get 0 packets received.

peterb: I've done full port scans of all the ranges (192.168.0/1.x) you mentioned (on port 80 to try and find the web admin interface and also with a ICMP Ping) and found nothing. I've been using a subnet mask of 255.255.255.0 in every scenario mentioned.

Two points of note:

1.) Whatever I do, there are 0 packets received. This is the same in Ubuntu, Windows Vista and (my latest test) Mac OSX.
2.) I can see that there is a second LED next to the green light which at no point comes on.

I *know* that only 1% of hardware is faulty, but I have severe reservations about this piece of kit that purports to be a matter of just plugging it in and then pointing a web browser at 169.254.0.1. It just doesn't seem to work no matter what I try on three different machines and a router.

Thanks again,

Martin

Well someone has to get that 1%... it sounds as if you have covered all the obvious things - perhaps RMA is the way to go - sorry it didn't work out.

It does, unfortunately, sound like it's fairly fubar'ed. Once last thing I'd check (although it's fairly rare) is that the pins in the network port on the NAS box aren't damaged (or just pushed up so that they don't make full contact with the cable) as you only need one of the pairs working to get a link light.

Hi guys, and again, thanks for your time. (how do I thank you so that your "thanks" counters go up? :))

Viper81: I had a look at the box and I can't see anything obviously wrong with it - it looks just like any other ethernet port I've looked at. I'm also a little reluctant to start moving pins about in case *I* snap something and then invalidate my warranty.

So, in conclusion, I think I'm going to have to go down the RMA route. Pity, it was all going so well - Citylink even redelivered!

Thanks again,

Martin

Your welcome.

(after - I think 25 - posts you get a thanks button appear at the bottom of the post you want to thank. Not quite sure why that limit is there - most new posters come here looking for assistance!

Hope the RMA goes smoothly and you have more success with the replacement. Where did you buy it?

Ah ok, I'll have to get doing some serious posting.

I bought it from scan and I did dispatch an email to their tech support on Friday (and they are open Sat) but have not had any response.

Think I'll give them a call for the personal touch on Monday.

Thanks again,

Martin

you could stick a thread in the scan section of the forum (SCAN care@HEXUS HERE). as some of the SCAN guys spend some time around here during there weekends too....

but seeing asthough it's nearly mondee, you might as well call them...

also, on the SCAN not responding to your email query point, i'm not sure if they reply to querys over the weekend... so it could be that you will get a reply tomorrow.

Hope you get things sorted matey :thumbsup:

On the rare occasion I have had to use it, Scan's RMA process is pretty good - but on something like that, it would be worth talking to their tech guys.

As suggested have made a thread over in the scan section...

I await their reply! :)

Thanks again guys.

Martin

Its good to talk! Give them a call 01204 474747 (rather than the expensive 0870 number)

Heya,

I did end up phoning - and they were very helpful and pretty much agreed that it sounds like a tech fault. The RMA is being processed :)

Thanks so much for all your help - was glad to hear it wasn't just me being exceptionally stupid!

Martin

Phew - it really wasn't my fault hehe!

Current status of your RMA: Awaiting Replacement / Credit

We can confirm your returned goods have now been tested by our technicians.

Thank god for that! :>