@Mijzelf and @fvdw
Thanks for the fast response and I have to apologize because I wasn't clear in some points. First, I have to say that my previous Network Space and my Network Space 2 have and served me well over the years. I have to point out that %98 of the time when a problem appears it is usually a Windows problem. In the past when I have encountered a problem seldom is it necessary to reboot the NAS. I have attempted the "Proper Care and Feeding" of the NAS using a UPS and power surge protection. I avoid cold (hard) starting the NAS, and cringe when this is the last resort when I can't communicate with the NAS and bring it down gracefully. The Network Space 2 just works.
I don't think a factory reset killed your nas.
I meant the factory reset may have exposed one of the root causes of the problem. What concerns me is that now the NAS “continuously beeps” after the NAS boot has completed as indicated by the LED. I feel it is not a beep “indicating over temperature state” because several times during my troubleshooting I have shutdown the NAS overnight.
what you describe it is not fully clear what exactly happened with your device
When this happened I was using my desktop to do normal day to day tasks. I did not add any MS hot fixes (DT is fully patched), install or remove any programs or drivers, or add or remove hardware. I came back the next day and noticed I could not see my NAS share from Windows Explorer.
It seems to have worked in the manual ip setup you described
I did the private network scheme because I’m in a insecure network location. It might give me a false sense of network security for my NAS, but it was cheap with only the expense of a network switch and CAT5 cables. I went through my old notes and one of several references I used was http://www.wikihow.com/Set-up-a-Private-Network
After the reset I went into the NIC properties and changed TCP/IPv 4 to “Obtain IP address automatically” and “Default gateway” to mirror my WIFI router’s ip address on the NAT side. I also verified using ipconfig settings on the NIC adapter and used my Netgear WiFi adaptor network settings as a reference where applicable. When I was satisfied the NIC and NAS had recovered, I used the freeware Advanced IP Scanner from http://www.advanced-ip-scanner.com
to scan the entire subnet. I used Advanced IP Scanner options “scan resources” with “shared folders”, “http”, “https”, “ftp”, and “active user name”.
Also, please do not become offended, but I did “RTFM” about LED states in the Network Spaces User Manual.
After some prayer and meditation and a promise of complete obedience and unquestioned love to the disk drive Gods, I ‘am leaning on attempting to remove the NAS drive myself and attempting to recover my data. I received a LaCie support reply back which states:
As a part of repair and testing process the drive will be formatted and/or the mechanism may be replaced so any data on the drive will be lost.
They recommend d2recovery but the price is out of my range. As I see it I have nothing to lose. Once this saga is over, I probably will purchase another LaCie product for intermediate data network storage, and a NAS RAID solution for recovery purposes.