News:

Buffalo provides Data Recovery services. Read about it here.

Main Menu

Buffalo Can't be access over the network.

Started by tparker_Mops, October 29, 2008, 02:56:46 PM

Previous topic - Next topic

tparker_Mops

   

I have a Buffalo Terastation that was purchased by the agency I now work at previously. Up till now the only issue I have had with it was it getting close on being full. I had an incident last weekend where it did fill up and my back up jobs all naturally failed. I cleaned up some space and thought everything was good. I came in the other day and found it powered down. I turned it on and watched it go through its routine to check everything throughout the day and it got to 80-85% by the end of my day and I let it roll through the night.

 

This morning, it was off again, so I powered it up, and went to our remote office where I was working from today. The terastation wouldn't respond through the web browser when I attempted to check on things. So when I got back to the main office this afternoon I checked on it again. The date now says 1/1/2005 and the time is all wrong.

 

I can ping it through the network, but the web server is not responding and the Application that is installed on my workstation doesn't apparently see it correctly as I can't see any of the shares?

 

What can I do now? I am very new to this product? Please help.

 

TIA.

 

Tim

 


macgyver35

   

Hi Mops,

 

I too have had a number of issues with the Buffalo NAS drives and their connection to our network.  They seem to be somewhat particular and require a number of settings to be adjusted that are outside of the "network" settings tab within the web-based user interface.  Given that the date has reset, it sounds like your station may have reverted to factory default settings.  You can still ping it since it is set up by default as a DHCP client, but outside of that you'll get nowhere, and Buffalo's downloadable documention is very lacking.  Here is a great article on getting things set back up.  You'll need basic network and active directory knowledge, but even with that, the article points out a number of "gotchas" that are easy to miss.  I've also found that even when these things are set up correctly that you will often still have problems with the station losing it's network connection or that AD permissions are not carried through correctly.  In general, the Active directory capability is VERY poorly documented and I still have questions about establishment of permissions, etc.  At this point, my love of Buffalo products is fading fast.

 

 http://buffalo.nas-central.org/index.php/Joining_Active_Directory


tparker_Mops

   

Thanks for the info. I will take a look at that link and see what it offers me. I ended up going out last night and getting a 1TB Ext. USB Seagate drive to put on the server. We were running out of room any way on the Terastation. I now have it sitting on my desk and am cableing it up so I can toy with it from here.

 

I don't think we are doing much with AD (if anything) it was pretty much just the NAS device that apparently I found out last night was supposed to store all the agency files, they found out quickly that it wasn't what they wanted/needed so they moved it to just storing Backup Exec backups.

 

Now it will be a door stop for me till I get it working!!

 


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: 147 (show)
Files included: 35 - 1354KB. (show)
Memory used: 997KB.
Tokens: post-login.
Queries used: 15.

[Show Queries]