News:

Buffalo provides Data Recovery services. Read about it here.

Main Menu

No Warning on Lost Network Connection

Started by TerryR, July 19, 2010, 08:21:12 AM

Previous topic - Next topic

TerryR

I have a TeraStation Duo  TS-WXL/R1 being used only for file backup. I just discovered it's been off the network for some time. Rebooting the unit fixed the problem.

 

The issue is I never got any warning that the connection had been lost.  I have NASNavigator running all the time (on Windows 7 64-bit) and had expected it to report a loss of connection, but it didn't.

 

Is there any way, other than manually checking from time to time, to get a warning when the connection is lost? I've not found this issue discussed in a search of this board.


AngelsAbys

The Nas Navi should have reported this in its own way, which is the unit does not display in the window.  If it still does display but you cannot connect try to refresh the navi.  There is no real way to make sure it stays connect outside of keeping the unit dust free, in a well ventilated and temp controlled area, as well as making sure the switch is in the "on" position and not the auto


TerryR

Thanks, AngelsAbyss. The NASNavigator did fail to display the unit, which of course is no warning at all because you have to open the Navi to see that. Sounds like a huge hole in the system to me.

 

The Terastation actually reported that it was connected to the network on its display, and gave an address on the LAN. But the router showed no connection - obviously it didn't recognize the address, and as a result the unit was not accessible. It had apparently been off for a while, so there is no telling at this late date what caused the disconnect.

 

Rebooting the unit obviously caused it to request a new address which was provided by the router and the connection was restored. Perhaps assigning a permanent address would help?

 

The issue at this point isn't so much the loss of connection, but the fact that no report of that is generated. It seems the real solution is for Navi to be fixed so it recognizes and reports loss of connection, so it wouldn't matter what the cause of the lost connection was.

 

Terry

 

 


AngelsAbys

A static address would certainly help with holding the connection.  The higher ups also read through the forums, I will make sure at least 1 of them sees this post to work on an implamentation for a DC issue


TerryR

Thanks on both counts, AngelsAbyss.

 

Terry


Browser ID: smf (is_webkit)
Templates: 4: index (default), Display (default), GenericControls (default), GenericControls (default).
Sub templates: 6: init, html_above, body_above, main, body_below, html_below.
Language files: 5: index+Modifications.english (default), Post.english (default), Editor.english (default), Drafts.english (default), StopForumSpam.english (default).
Style sheets: 4: index.css, attachments.css, jquery.sceditor.css, responsive.css.
Hooks called: 182 (show)
Files included: 35 - 1354KB. (show)
Memory used: 1001KB.
Tokens: post-login.
Queries used: 16.

[Show Queries]