Windows XP Pro (laptop & desktop), Verizon FiOS router, HS-DH1000GL drive.
I have had this drive for a couple of years and it has been solid (although it will inadvertently freeze and begin beeping so I have to restart. Also seems to be constantly writing - it is a bit noisy).
Over the weekend I had to reboot but after restarting I could not locate it on my network. So I read the thread below and followed the instructions. I was able to get the firmware upgraded and could see the files on the drive but I have not been able to reconnect to the network. The FiOS router is the DHCP server. My guess is that the drive is not getting the proper IP address but I cannot get into it to reassign.
I Downloaded all of the most current software from the Support section of the web site.
Probably a simple fix but I can't seem to figure it out.
Thank you in advance for your help.
(PREVIOUS THREAD)
I would try plugging the unit directly into your pc and logging into the interface and give the unit a static ip address from the routers dhcp pool and see if will connect then.
I did connect the drive directly to my laptop, installed the NASNavigator2, then changed the IP address to one that matches my network. I then reconected the drive to the network but was not able to connect to it, either through a browser or with a mapped drive.
What did I leave out?
Thanks.
Did the nas navigator see it when you plugged it back into the pc? And im guessing since you were able to set a static on it you were able to access the interface when plugged right into your pc right? Did you update to any kind of new antivirus of firewall?
I just reconnected to my laptop and haven't been able to get back to it through NASNavigator; I can't even ping it with the IP I gave it. I was not able to access it from the 'interface' - I'm not sure I know what that is. Yesterday I was able to open a window that mimicked a browser that I was able to manage the settings. Is that the interface? Is that accessed by typing the IP address in a browser?
Do I need to reboot the drive?
Is there something I haven't installed? I have the original Navigator as well as version 2.
Also, on the original CD there is a tool to "connect to this computer" or "connect to the network". I'm just not sure if I've go some conflict going on somehow.
Sorry for the trouble. I think I know just enough to potentially make me dangerous...?
Thanks.
Correction:
I re-opened the Navigator and it had obtained a new IP again. I was able to go into 'Properties' on the File menu and request a new IP. It took me to a browser that allowed me to log into the interface.
What now?
Well if it has a static ip address now plug it back into your network and see if you can access it over the network. You have to make sure you gave it an ip address that your router can use. Like if your router is running on 192.168.11.1 make sure the ip address that you gave the linkstation is at least 192.168.11.x
Hmmm.
My network range is 192.168.1.x.
When I assign the drive 192.168.1.9 (not used on my network) it will not connect once I click on 'confirm'.
Does it require DNS settings?
It doesnt require DNS settings. Try plugging it back into your network and holding the reset button for 10 seconds. Give it about 2 minutes then try and see if the navigator can access it.
Maybe a dumb question but will it wipe the drive?
Not a dumb question at all. No it wont wipe the drive.
I held the reset button as directed and the drive began beeping (hoping that meant it was acknowledging the reset). I pressed the power button to clear the beeping and the drive continues to run.
However, I am still not able to access it over the network. Nor can I locate in in the Navigator when I click the Refresh button.
If I reconnect to my laptop directly and change the IP address to one that matches my network, it should remain as an assigned address, correct?
It doesn't make sense that it will now not show up on the network, unless there is something else I need to do.
As soon as you set the ip it should be able to be accessible. When you were changing the ip, were you using using the web admin tool (opening a browser and typing in the current ip and logging in) or the nas navi?
I initially tried it with the Navigator but found that when I plugged it back into the network the IP address changed back, so I changed it in the interface.
When I reponed the Navi it shows the IP in the lower right corner but the drive doesn't show up above.
Currently I have it reconnected to my laptop and I am buring a backup of the data (most of it is already backed up but I wanted to get the last couple of days done).
It seems to be running fine; I'm just perplexed an getting it back on the network.
When you put the unit back on the network it should get an ip address. Try putting it back on the network with an ip of 192.168.1.150 and then after its all rebooted and on the network go to your computer and select run and type in \\192.168.1.150 . see if it brings up the folders that way.
Reset IP to 192.168.1.150 then reconncted to network. Couldn't locate through Navi, Windows Explorer, or browser window.
When you say 'after it's all rebooted' do you want me to connect to te network, power off and restart?
After setting the IP on the drive to one that matches my network (192.168.1.150 - as suggested), I reconnected the drive to the network but was unable to locate it through Navi, Windows explorer, or a browser (Firefox) using the IP address. Clicking on the Start button and usin the 'Run' command failed as well.
I went ahead and pressed the reset button on the back of the drive to reconnect it to the network. It rebooted but returned to an IP tat is not on my network (169.254.222.226). I don't know where that IP address is coming from.
When I have it connected directly to my laptop I am able to access the drive and copy files to and from.
Where is it getting the IP from when all of the other devices are getting it from the FiOS router? I have 2 computers, a PS3, and a Kodak wireless frame on the network.
I'm truly baffled on this.
a 169 ip address is an auto generated ip address. I would try attatching it back to your pc and updating the firmware. Something is really strange about that whole situation. Do you have any router you could possibly try as well?
I updated the firmware already but will try it again. I don't have another router to try; The FiOS router/modem connects right to their interface in my house so I don't know how to work around it.
All of my other devices connect OK to the router (both wired and wireless - iPad, iPhones, wireless photo frame, desktop CAT-5, & laptop CAT-5 and wireless.
The only things I can think of that set this in motion would be improper shutoff or that I converted a video file from Sony AVCHD to MPEG4.
Those are the only things that transpired prior to the drive disconnecting.
I got to the end of the line with Jotin but I was able to resolve the problem after hours of tinkering.
With the drive powered down, I attached it directly to my laptop then powered up. It generated it's own 'default' IP address (169.XXX.....) and I was able to locate it through the Navigator. I then clicked through to the 'Open with Browser' button and was able to get to the interface.
I worked through all of the links there and finally got to one of the tabs/buttons that allowed me to power the drive down through the interface.
Once it was powered down I disconnected the drive from my laptop, reconnected to the network, and powered up. The drive obtained a correct IP address on the network and had to be re-mapped to each computer accessing it.
A rather inconvenient situation to work through as I'm not sure why the drive would not obtain an IP address from the router since it is the DHCP server. All of my other devices reconnect with no problem.
I can assure you that I am now in search of a better solution. This drive is slow, seems to run constantly and make a terrible amount of writing noise, and the interface is not real easy to use.
I am looking for a media server/drive that is easy to navigate and stream video/pictures QUICKLY to my computers and TV's. After all, my wife and children want to access the media as well and if they have to deal with these issues, they would not be able to work through it. Technology shouldn't be this hard.
Oh, wait. That's why I'm converting to APPLE. Everything we have with that name on it WORKS. It's that simple. PC-related devices should be thown in the trash - too many geek types have their weird ideas on how to do things and forget that 98% of the world wants something easy to use and work when you press the button. What a concept.
bwritt wrote:
Oh, wait. That's why I'm converting to APPLE. Everything we have with that name on it WORKS. It's that simple.
Is that ment to be a joke? Either way i'm laughing! loooooooooooooooooool