Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[CptnBlues63]

This just started a week or so back.  I've been fighting with it for that long trying to get it to work with no joy so here I am.

I can ping the NAS.  I can also connect to the management interface via http.

I cannot map a drive to the NAS from Windows or from my FreeBSD (v10.1) box (I've built a zfs NAS device and copy everything to it from the NAS as another backup)  and I've tried pretty much everything I can think of.  I've rebooted the device.  Powered it off, let it sit for a good 30 seconds, powered it up.  I've checked every possible setting in the management interface as well.

I can't map using the IP address either.

Any ideas?

[FurryNutz]

Link>Welcome!

• What Hardware version is your DNS? Look at the sticker behind or under the device.
• Link>What Firmware version is currently loaded? Found on the DNSs web page under status.
• What region are you located?

What Mfr and model is the main host router?
Is the DNS getting a Dynamic IP address from the main host router? I recommend using a Static IP address ON the DNS set to 192.168.#.32 or .23.
Swap out LAN cables. Link> Cat6 is recommended.

PC 3rd Party Security Software Configurations

• Turn off all anti virus and firewall programs on PC while testing. 3rd party firewalls are not generally needed when using routers as they are effective on blocking malicious inbound traffic.

[CptnBlues63]

HW Version: B1
FW Version: 1.10

The router connected to the internet is an older Linksys WRT54GL with the latest version of Tomato.  But all it's providing for my network is NAT, DHCP and some basic firewalling.  And that only because it was in place before I built a pf based firewall on a FreeBSD box.

I'm located in western Canada (not that that should matter or make any difference).

I always run static IP's on devices like the NAS and my printer.

I don't use firewalls internally on the windows based PC's, I have a FreeBSD pf firewall between my SOHO Router and my LAN and can't be bothered with MS's built in PITA POS firewall.

Just FYI, I do IT for a living and have for 20 years.  While I'm presently specializing in enterprise level networking and have been the last decade, I have around 10 year prior experience doing everything from hardware (PC's, laptops and servers) to MS AD domain administration.  So I'm not a newb.

I've covered all the basics on this.  It was all working fine and then it just wasn't.   I had no problem with mapping drives and accessing the device as recently as the last week in October when I reimaged my windows 7 PC to it as a backup.  I was gone on my annual hunting trip the first two weeks in November and upon returning discovered I could no longer map to it from any PC in my house and am unable to access the data on it.  My wife, who's very tech/computer savvy would not have touched the NAS physically while I was away and at most, might have copied some files to it.

Link>Welcome!

• What Hardware version is your DNS? Look at the sticker behind or under the device.
• Link>What Firmware version is currently loaded? Found on the DNSs web page under status.
• What region are you located?

What Mfr and model is the main host router?
Is the DNS getting a Dynamic IP address from the main host router? I recommend using a Static IP address ON the DNS set to 192.168.#.32 or .23.
Swap out LAN cables. Link> Cat6 is recommended.

PC 3rd Party Security Software Configurations

• Turn off all anti virus and firewall programs on PC while testing. 3rd party firewalls are not generally needed when using routers as they are effective on blocking malicious inbound traffic.

[FurryNutz]

Try a different router?

[CptnBlues63]

In hopes of achieving what?

All my devices plug into a switch.  The switch in turn plugs into my pf firewall (BSD box) which in turn plugs into the SOHO router.

Traffic going from any one PC to the NAS (or to the printer or another PC) goes via the switch and never touches the pf firewall or the SOHO router as it's all on the same subnet.

Try a different router?

[ivan]

Can I assume you are still using win7 on your computers and was it only one of them that you reimaged?

I also assume that you have checked for such things as the NAS and computers are in the same workgroup (we have found that win7 defaults to homegroup when there is no domain server)

As a test to see if there are any problems with the drives in the NAS, enable the FTP server (if you haven't already) and then use something like FileZilla to log on to that server.  You should then be able to see the files and folders for the defined user/group.  If you can't see any files/folders then there is usually a problem with the user/group settings.  That problem will have to be solved first.

I will say it is generally the simple things that cause the most problems usually because we are 'sure' that they haven't changed so we don't look at them.  I learnt that the hard way when I started in computing with punched cards and in many ways what applied then applies more today. (example: we had one client that had such things as NAS boxes and network printers setup on fixed IP addresses although the computers were on DHCP.  For some reason they changed the router that had the DHCP server and everything with fixed IP couldn't be found - not so strange because the new router gave out IP addresses on a different subnet.  Their IT guy couldn't find it because he 'knew' the DHCP server worked therefore it had to be something else.  It wasn't until one of my guys got there without any preconceived and followed our check list that the problem was found and rectified).  There are times when I think that us professionals are our own worst enemies because we just 'know'.
 

[CptnBlues63]

Actually, I didn't explain that quite as clearly as I could have.  I backed up up my main gaming rig which is indeed running Windows 7.  I made an image of the PC and stored it on the NAS.  In fact, it went direct from PC to NAS.  Upon rereading my post, I realized it sounded like I reimaged the PC which was not the case.

As to the rest of your query, I did all the basic troubleshooting.  I got nowhere.  So, I waited a couple days and did it again, just to make sure I didn't miss anything.  After another few days, I went through it again and posted here.  As I said, I've been working in IT for 20 years and I know how easy it is to miss the simple things so that's why I went through the troubleshooting a couple times before posting here.

I did as you suggested and enabled the ftp server but was unable to access via ftp.  I ran the disk checking utility on the NAS mgmt software (again) and it found no errors.

I just now rebooted the NAS via the mgmt software (for like the 10th time) while writing this response and lo and behold, this time it decided to work.  What "fixed" it, I do not know but while I have it online, I'm going to copy everything over to my FreeBSD NAS and I'll start looking for a new enclosure to replace this one, I no longer trust it.  I do wish I could put a 10 Gig interface on the D-Link because I do have one on the FreeBSD box and a few sfp+ multimode cables on hand.  While I only have about half a TB of data on the device, it would certainly copy a whole lot quicker at 10 Gig than at 1.  Oh well, you can't have everything...

Thanks to everybody who tried to help me on this.  I appreciate it.

Can I assume you are still using win7 on your computers and was it only one of them that you reimaged?

I also assume that you have checked for such things as the NAS and computers are in the same workgroup (we have found that win7 defaults to homegroup when there is no domain server)

As a test to see if there are any problems with the drives in the NAS, enable the FTP server (if you haven't already) and then use something like FileZilla to log on to that server.  You should then be able to see the files and folders for the defined user/group.  If you can't see any files/folders then there is usually a problem with the user/group settings.  That problem will have to be solved first.

I will say it is generally the simple things that cause the most problems usually because we are 'sure' that they haven't changed so we don't look at them.  I learnt that the hard way when I started in computing with punched cards and in many ways what applied then applies more today. (example: we had one client that had such things as NAS boxes and network printers setup on fixed IP addresses although the computers were on DHCP.  For some reason they changed the router that had the DHCP server and everything with fixed IP couldn't be found - not so strange because the new router gave out IP addresses on a different subnet.  Their IT guy couldn't find it because he 'knew' the DHCP server worked therefore it had to be something else.  It wasn't until one of my guys got there without any preconceived and followed our check list that the problem was found and rectified).  There are times when I think that us professionals are our own worst enemies because we just 'know'.
 

[CptnBlues63]

Correction, drives are accessible via windows file manager but I can't open any files.

They appear to be copying to my FreeBSD NAS device ok so once I'm done that, it's time to replace the enclosure.

[ivan]

One last thing, check that you can read the transferred files.  I have seen files that were transferred to another unit apparently OK but were damaged because there was an intermittent hardware fault on the unit they came from.