08-02-2012 06:13 PM
I initially had problems when I first setup my Black Armour NAS 220 only being accessable sometimes on the network. I solved this by changing it to a static IP and mapping it on all computers on the network. Has been working fine for a couple of months and then all of a sudden connection problems are occuring. The mapped drives will only connect sometimes, and the Black Armour discovery software doesnt even display the drive on occasions, but if you close the discovery software and launch again the drive will usually appear. It seems to stay connected for random lengths of time and then we have the same problem again. This is REALLY frustrating. Even when it will not display in the discover software I can ping the NAS and it shows it is on the network. Any ideas anyone?
11-14-2012 04:15 AM
Just an acknowledgement from another user having experienced similar problems.
This is my experiences in brief:
* Configuration - Run a BlackArmour NAS220 connected to a NetGear GS608 switch. Router Netgear RP614. Main PC Windows Vista 64-bits equipped with Nvidia disk controller SW. Have recently upgraded NAS220 firmware to latest available version.
* When initially installing the NAS220 it could not be found on the Network (in my understanding due to erroneous default IP address 169....). Solved by connecting locally to PC and assign new IP 192... Then the NAS 220 was discovered on the network.
* Sometimes the connection to the NAS220 drops. My solution has been to manually reset and reconnect directly via IP-address (192...). This happens quite rarely though. Seems to be more frequent with password protected shares, which might not reconnect after PC re-boot.
* The bundled Discovery software seemed to only occasionally find the NAS220 on my network. Lately I noticed, however, that there might be quite a lag from when one starts Discovery until the the NAS is found. Some testing indicated search times between 5-10 minutes on my network. Since one gets no indication that the search is ongoing, one could easily conclude that the NAS is simply not found. I don't know whether the Dicovery program always finds the NAS (after a delay) - as I haven't had the time or interest to do further testing...
Interested to hear more about others' experiences with similar issues and solutions.