Print

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

[fallex]

First of all apologies to users who tried to help me here :- http://forums.dlink.com/index.php?topic=54705.0. (reading it may help in explaining more to this problem.)
Unfortunately I had a heart attack and ended in hospital, so with reference again to that topic, whilst in hospital I decided to basically start from scratch ordered the newer DNS 320 (the one with the sloping lid) B1 version. Still with original firmware. (The original 320 I have is the A1 version with the 2.03 update)
So arriving home I put the 2 x 2tb drives in and reformatted both, but then the problems from the original post reared up again.
By now having got to the stage of a drowning man clutching at straws I installed Linux on a spare drive (never used it before - know nothing about it) - just wanted to find out if it had the same sort of problems as windows. Booted up and sure enough I get the same problems but obviously the error message in Linux is worded differently, it just says "Connection timed out" but the effect is the same as in Win 7. I can see the DNS 320 and the two 2 drives in each operating systems, but I cannot access them to do any file work. I,m at a loss as what to do, I,ve probably screwed up the settings but for the life of me I can't see how, anybody got any suggestions? thanks for reading.

[ivan]

From what you are saying it appears that you can access the unit via the web interface otherwise you wouldn't be able to format the drives.

How did you set up the drives - JBOD, STANDARD, RAID 0, or RAID 1?
What services did you enable - CIFS, FTP etc.?
Have you changed your router at the time the the first problems arose - ports may be closed on a new router so preventing access.
Did you give the unit a fixed IP or is it getting the IP via DHCP?

Answers to those questions should be a reasonable starting point to try and solve your problem.

I tend towards thinking there has been a change in your network that is causing the problem and not the NAS units but without information about your network setup and router make/model I can't take that further at the moment.

Since you are using windows download a copy of NETSCAN (find it with google, it's free and comes with both 32 and 64 bit versions in the zip).  Unzip it and double click on either the 32 or 64 bit executable (depends on which version of win you have) - fill in the IP range you are using and click run.  This will show if the NAS is appearing on the network or not - let us know if it is and, if you gave it a fixed IP does it appear at that IP.

[fallex]

Again my apologies, I did not know what other, if any information I should have put in my post, so I,ll try and answer your questions the best I can.
1/ The drives are set up as 2 standard drives
2/ Both volumes share setting are CIFS and FTP
3/ Router is a Cisco EPC3925 supplied by my ISP and has been in situ since we moved into the house, and therefore has not been changed
4/ As regards the IP addressing the DNS 320 has been addressed, both fixed at 192,168,0,32 and assigned byDHCP at 192.168.0.22, the problem persists either way. At the moment IP address is assigned by DHCP. I,ve no idea if this is the preferred method or not, but I have a large amount of units on my network (4 andriod tv boxes, 1 Mede8er media player, 1 laptop, 1 other windows Pc-rarely used, plus 2 tablets accessing network wirelessly via a wireless extender)so I prefer to let DHCP assign IP address as and when required. I have also tried disconnecting all those units and just basically having the main PC , DNS 320  and router in the network but whether fixed or assigned addresses the problem persists.
I,ve gone into the settings on the router to see if anything there needs to be changed but to be honest with my very, very limited knowledge I really would't know where to begin. (No reason why? but I,m beginning to suspect a router problem)
Downloaded netscan (presume its the one from download.com)  but does not seem to work, on running it comes up with a error message in italian.
So that is as far as I have got any further info you require just let me know. Thanks

[ivan]

Sorry I should have looked up where to get Netscan. http://www.softperfect.com/products/networkscanner/ scroll down the page past the screen shots to download the zip file (this is the latest version that works with win2000 to win

I will get my service manager to get a copy of your router manual tomorrow (nearly midnight here) and we will see if anything jumps out at us that you might have missed.

We always setup NAS boxes with fixed IP - it makes it so much easier to access things like the FTP server and web interface, for example using ES File explorer on android all our NAS boxes FTP servers appear under the lan tab without having to go through a long connect procedure (do it once and it is the same every time).

The fact your router is supplied by your ISP does make me wonder about some settings.  I remember a friends BT HomeHub that wouldn't allow some ports to be changed which was frustrating to say the least.

I will let you know what we find after I read the router manual.

[fallex]

Well the mystery deepens, earlier on today low and behold I was and still can gain access to the volume_2 drive and I have been able to transfer and work with files all day long.
Volume_2 has my tv video files on it
Volume_1 has my movie video files on it
But you've guessed it Volume_1 is still a no no. windows simply tries to discover the contents of the drive with the green travel bar taking forever to discover the contents of the drive.
Both drives are 2TB and are exactly the same Samsung model and both have been checked by smart disk etc. In fact I removed both drives from the 320 and inserted them into a twin drive DAS connected via esata to my PC and using Disk Internals Linux Reader free program I was able to work from Windows 7 with the two drives with no problems whatsoever again verifying that the drives do not seem to be at fault
So logically my earlier suspicion that my router might be at fault now seems incorrect, if one of the drives actually is now working as it should within the NAS.
I then tried to think again about possible reasons for not being able to access one drive whilst being able to access the other drive, I looked the differences between the two drives, other than the actual folders and file names then there was no difference, the only file types on the two drives are .jpg .avi  .mp4 and .mkv. Then a thought occurred to me the vast majority of the video files on Volume_1 (TV Series) are smaller in size than the movie files already on the Volume_1 drive (put on drive earlier)
so, I've come to another conclusion, that windows itself is at fault and struggles to discover correctly video files above a certain size (especially in bulk).
I don,t know how feasible this sounds but having googled this it seems it can be a problem on some windows 7 systems over networks that evidently from what I understand, originally came to light with windows vista, and it does not like to work with large collections of large video files
As an example I tried to to copy a single folder with a 1.4GB video file and two .jpg files inside over to my Volume_1 drive (in the 320) it would take up to 15 minutes just attempting to copy these 3 files, on a few of occasions on opening the folder I got an entry for the video file but the size was never correct sometimes 0kb the most it ever showed was about 300mb I think, the interesting thing was that it never failed to transfer the jpg files.
So I wonder if anyone else has come across this or has thoughts on it or indeed knows of a fix for this.

[ivan]

Sorry I can't help with the windows problem - we have only one instance of win XP here running in a VM that has one purpose, fine tuning epub files.

Just a thought since you are half way there.  Do you know anyone with a laptop with win XP on it that would allow you to use it to see if it can access Volume_1 in the way it should?  If it can then you have pin pointed the problem, though how to fix it maybe a bigger problem.  If it can't then we have to determine why?

[fallex]

Hi again, apologies yet again for late reply, been ill yet again also major problems with ISP doing area wide maintenance.
Anyway took the advice and found a friend who had a copy of win xp for me to test out the problem after installation on a small drive.
Interesting results really, suspect drive worked fine in Xp, then out of interest I did a HD check with Xp and lo and behold it found some errors on the drive (why the drive should still work in Xp is anybody's guess) which was never found using software in win 7, so I,ve decided to buy a new drive now as I seem to be chasing a ghost here, and it does look as though this drive might be suspect and I would not want to risk carrying on using it.
So thanks for your help much appreciated.
Last questions, what is the maximum size of harddrive will the newer version of the DNS 320 take (hardware Version B1 Firmware Version 1.00) (would I need to update firmware), would ultimately like to install 2X4tb drives if possible. Thanks again.

[ivan]

Sorry to hear about your illness, unfortunately s**t happens.

Before you consign the drive to the scrap heap you should download a copy of the seagate disk tools and run that against the drive mounted in either a USB/SATA caddy or, maybe, your DAS unit.  Doing that will confirm the state of the drive and if it can be trusted or not. 

If it doesn't pass anf the drive is still under warranty you should be able to get a replacement.

As for the maximum size of drive for the B1 version I can't say, we don't have one neither does any of our clients.  The changelog of the firmware should give that information if there has been any change from the basic setup.   

[fallex]

Ok, will try and follow your recommendations over the weekend. Will post back with any useful info.
But more importantly would really like to thank you Ivan for your help and patience.

[fallex]

Ok ran Seagate tools and would you credit it, drive actually died during the tests, so it seems the drive had problems all along. So again thanks