We help IT Professionals succeed at work.

Cannot access my data drives

thedslguy
thedslguy asked
on
Hello Experts

I was having internet issues and had to connect directly to my COX Panoramic router, bypassing my Linksys Router.  They are on separate networks (Linksys 192.168.1.xxx ;

COX  192.168.0.xxx)

Now that I have it all back together, I can't access my Buffalo NAS Drives.  They are LS220DE housings with 2ea 1TB RAID Drives

I pulled the drives and held the reset button for 10 seconds like the quick setup said to do. I still can;t access the drives.  They show in a scan with DHCP addresses, but the connection times out.

Any ideas?

Thanks

thedslguy
Comment
Watch Question

CERTIFIED EXPERT

Commented:
Your configuration isn't at all clear.  On which subnet (192.168.0.x or 192.168.1.x) is the NAS device and on which subnet is the computer you are using to access the folders?

"They show in a scan with DHCP addresses": can you be more specific?  How are you doing the scan and what is "they"?

Can you ping the IP address of the NAS device?  What happens when you try to bring that up in a web browser?
CERTIFIED EXPERT

Commented:
"I pulled the drives and held the reset button for 10 seconds like the quick setup said to do": Be VERY careful about that!  I've scanned the manual pretty quickly and haven't seen what that reset does.  It may reset the RAID configuration.  If so, you'll want to be very sure about how you put that back together without losing data.

In any case, the first step is to be able to get to the management interface on the NAS box.  Have you installed the Navigator software?  Does it find the system?
nociSoftware Engineer
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
Does the NAS have a default GW pointing to the right address if the NAS & the PC are in different LAN's?
thedslguyComputer and Network Consultant

Author

Commented:
CompProbSolv:

The cox router is on 192.168.0.xxx.  All else is on 192.168.1.xxx.
When I scan for the drives, using the Buffalo NAS Navigator software, both drives show up on their DHCP addresses (address assigned by the router)
Both units ping.  When I try to access them in a browser, both units say Connection Refused.
I pulled the drives out before I pressed the reset button.
The Navigator software is installed and it sees both network drives.  



noci:

The PC and the drives are in the same subnet and both are set with the correct Default Gateway.



I also tried connecting from the "run" command.  I got the same error message after trying both units:

A Network Error saying "Windows cannot access \\192.168.1.168"  Then it says to verify the spelling.  I tried the built in diagnostic and it says the remote device won't accept the connection.  (I think that's the same as the"Connection refused" message when I use a browser)

-tdg
CERTIFIED EXPERT

Commented:
"The cox router is on 192.168.0.xxx.  All else is on 192.168.1.xxx.": how are you expecting devices on the 192.168.1.x network to get out to the internet (or doesn't that matter)?

"address assigned by the router": how is the router on the 192.168.0.x subnet assigning addresses on the 192.168.1.x subnet.  Most routers restrict their DHCP server to only assigning addresses on their subnet.  More importantly, why?

"both drives show up on their DHCP addresses": In my limited experience with NAS devices, the drives don't show up on an IP address, the NAS box (and its shares) show up.  Are these two individual (non-RAID) drives?
thedslguyComputer and Network Consultant

Author

Commented:
CompProbSolv

What I was saying is the COX connection is on a different subnet that network.  I have internet access just fine.  The 192.168.0.1 network doesn't factor in.   The LAN I'm using is 192.168.1.xxx. I guess I didn't need to even mention the other at all.  My apologies.

The router (192.1681.254) is assigning DHCP.  The drives are in that network.

Both NAS boxes have RAID setups with 2  1TB drives

tdg
CERTIFIED EXPERT

Commented:
OK.  I have no clue what the 192.168.0.x network relates to, but that isn't relevant to the issue of getting to the NAS boxes (I didn't realize there were 2 boxes).

I would look carefully at the configuration of the shares in the Navigator software.  I'd start with setting them up for anyone to access them without passwords.  It's sounding as if there is some sort of access rights issue.
Computer and Network Consultant
Commented:
CompProbSolv:

The rub is I can't access either of them.

And quite frankly, pretty much all you've contributed is criticism of my explanations

I believe I'll just withdraw the question and see if I can get some help from tech support

thedslguy
CERTIFIED EXPERT

Commented:
As you wish...

I've learned in many years of troubleshooting that the first (and often most important) step is to carefully describe the symptoms.  Not just the high-level observations (e.g. "I can't access my NAS drives"), but the lower-level ones (IP addresses, logging into the interface, running the management application, etc.).  If that didn't fit your needs on this question, then I'm sorry I couldn't be more helpful.  I certainly wish you success at resolving the access problems.
nociSoftware Engineer
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
We cannot access your network so to assess the "high level"  problem of "cant access my NAS" ... , and different addresses given  it FIRST has to be established how the network  is put together. Any firewalls, routers. etc. or just flat network...
After a getting that info it appears there are TWO NAS with the same problem.    So there are changes done or there was an incomplete description....

The next step is to validate all systems are actually on the same IP network. (does all routing, and low level stuff work, are all IP's as they are expected...)
If the NAS never received a DHCP address f.e then can they have a valid address?  so does DHCP work as expected.. etc.
The next step would be if the NAS actually responds to ports needed for the service (aka were the started properly).
etc. etc.
So 1) clear picture,   2) validate all expectations in the picture, from the bottom up.   ... equipment,  cabling, IP-settings, ports/firewalls/forwarding...\
In short exclude by targeted experiment all non-relevant items that can contribute to a generic problem "cannot connect to X".

Otherwise the problem stays until after 100's of attempts to do all kind of things like hard resets, restores of unrelated equipment configuration ets .  folclore driven trials  where a 20 minute test & verify might have solved it without harm to any configuration / data.