05-03-2010 11:34 AM
Just bought the 110 with 1TB.
Installed BlackArmour Discovery (several times now) and when I start the S/W I get "No server found on your network".
I have read as much as I can to no avail and need some help.
When I first started Discovery I had to unblock it in my Windows Firewall.
As part of trying to fix this issue I have not turned off Windows Firewall and am relying on the Router Firewall.
I am running a desktop PC with Vista Home Premium (up-to-date).
The NAS name is BA-2296C0 (I think it is a zero at the end).
In Windows Explorer, under Network, I can see the NAS. However, when I try to expand, I get 'Windows cannot access \\BA-2296C0'. If use Diagnose button I get "BA-2296C0 is not a valid host name'.
I have tried cmd (as administrator) by entering ipconfig /all. I recognise my PC but I have a couple of Media disconnected messages.
Also, at some point I saw the message "Windows cannot access \\BA-2296C0, Error code 0x80070035, The net work path was not found'. The diagnose button said 'BA-2296C0 is not a valid host name'
I have DHCP enabled on my router. The modem/router is a local brand. It supports my desktop PC and a netbook (XP) and I have never had any problems. I have tried different ports on the router and another network cable.
Any suggestions on what to try next?
Solved! Go to Solution.
05-03-2010 02:49 PM
I don't know whether the NAS box could always be seen on the Vista Network Map.
Anyway it is.
It has an IP and a MAC address.
I have tried to ping the IP address but it is not reachable.
05-04-2010 02:52 AM
If I plug the NAS directly into the network controller, then I can logon and continue the setup process. As soon as I revert back, then I am back to the start.
This is how one guy fixed it (copied from a thread in this forum)...
inally got it sorted. After monitoring network traffic it was discovered that although the NAS220 was sending requests to the DHCP server the NAS220 was using 169.254.96.35 so I set up a router and route to this IP address, logged on to the NAS220 then set the NAS220 to static IP address and BINGO!!!
i need some further explanation because I have tried adding entry to the Routing Table List (obviously not very successfully).
Perhaps the steps to go through. There cannot be many now.
05-04-2010 09:49 AM
This part of your thread may be a concern, 'is not a valid host name'.
It has been observed that if you receive “hostname is no longer valid” when trying to access the NAS110 and then you try to re-flash its firmware and the flash reports, “The firmware image is not valid. Please use a valid firmware image”, the 110 has failed and needs to be replaced. (note: Replacement applies only to the NAS110 with this issue because it is a single drive unit which cannot be removed without voiding the warranty.
Follow along with me here. We need to attempt to flash the firmware on the NAS.
Connect the NAS directly to the PC.
Get the NAS's Manager page up and log in.
Go to System and Firmware Update and click Manual Update on the left.
Leave the browser open but minimize it for now.
Click Here to download firmware revision 1000.0391 for the 110 NAS
(Note: It does not matter if the NAS is running 1000.0391 or not)
After the download has completed maximize the Manager page and Browse to firmware and attempt to flash the BlackArmor.
Does the firmware update complete or does it report “The firmware image is not valid. Please use a valid firmware image”.
If the firmware upgrade reports, “The firmware image is not valid. Please use a valid firmware image”. the BlackArmor NAS 110 needs to be replaced.
Return it to the place of purchase or call Seagate Warranty for replacement.
05-04-2010 01:16 PM
Followed your instructions and everything went OK.
I logged off the NAS and shutdown the PC, NAS, Router and switched off the power.
Restarted and this is what I happens:
a) Discovery will not see the NAS.
b) In Windows Explorer, the NAS does not show in Network
c) In Network and Sharing, I have a Private Network and Network Discovery is ON (only Password Protected Sharing is OFF). If I click on View full Map I see in a line:
My PC, then NAS, then Gateway (my router:192.168.1.2) and then Internet.
d) NAS IP Address is IPv4:169.254.121.163 and it has a MAC Address. NAS is BA-2296C0.
If I right click on the NAS I see 'Management URL'. If I select this I get a new browser window but it cannot display the web page.
e) If I start a new Windows Explorer, then the NAS does not show up under Network. All I see is my PC (yesterday, I could see the NAS under Network).
Hope to hear from you RAsg for some more help.
05-05-2010 10:47 AM
This is the NAS's ip 169.254.121.163 when connected to the router? This is a 0 config ip address and it is not on the same network as the router which is, router:192.168.1.2.
With the 110 connected to the router use these instructions to reset the Network settings in the NAS.
The server reboots itself. Once the server has restarted and the LAN and disk drive LEDs are lit up, the reset is complete.
DHCP should be enabled in your router and after this reset the NAS should automatically pull an ip.
If you still have trouble getting the 110 to be found in the Discovery software etc. you should call Seagate Support and see if they can help to get you going.
If the NAS is new you will have 90 days of free phone support from the point of registering the NAS.
05-05-2010 12:36 PM
Thank you RAsg for your instructions.
I tried this but it did not work.
However, I borrowed a Thomson Speedtouch non wireless modem/router and Discovery sees the NAS.
So, my conclusion is that I need a new wireless modem/router.
Would you agree?
05-05-2010 12:46 PM
Every thing looks good as what you done, but I suggest check to see your modem/router firmware is current. You can check on that OEM site for firmware for it before buy more hardware.
05-05-2010 02:26 PM
Checked the firmware and I had the latest version.
Decided to ring up the Retailer's Support Centre and they were most helpful (Dick Smiths in NZ for all you Kiwis)
Fortunately, I had a spare modem/router, because I was able to set the NAS to Static in the LAN and assign a new IP Address which was in my 192.168.1 range.
After a shutdown and swapping the cables over, after the re-boot everything was OK.