NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Unable to connect to 'source'
I've been running a ReadyNAS Duo V2 for about three years with a WinXP machine. No problems whatsoever.
I have recently retired that m/c and replaced it with a Win7 x64 machine. I've used much the same disk naming and folder structure as before.
I've gone to edit my backup jobs (changing to the new computer's network name, etc) but I'm getting this unhelpful error message when I test the connection.
The computer's network name is 'Lunga', and the 'D' partition on the hard drive is called 'LungaData' (It's Windows share name is also 'LungaData')
I've applied 'Advanced Sharing' to 'LungaData' and sharing to the folder 'documentsTim'. It's a pity that the ReadyNAS documentation is silent on the possibility of there being any errors at this stage.
The WinXP computer connected without problem on '//Islay/IslayData/documentsTim' (I've NOT used the slashes in the FrontView entry boxes, of course).
I've tried every combination I can think of, but always the same error message. I've also tried creating new jobs, instead of editing old ones, but get the same error.
I have a second (physical) drive in this m/c, which contains all the files from the old one. I can connect to that without difficulty as '//Lunga/IslayData', where of course 'IslayData' is the Windows share name of that hard drive. No login or password required here. I've applied the same share permissions to this HD as to the 'D' partition on the main drive. I think this must mean that the ReadyNAS can 'see' the computer 'Lunga', but can't see the logical drive 'LungaData'. There was no problem with it seeing the logical drive in WinXP.
I have applied all the changes suggested by HERBIEO at http://www.readynas.com/forum/viewtopic.php?f=31&t=62968&start=15#p356698, but to no effect.
I could have made a silly mistake, of course, and I continue to look for it. But I begin to wonder if it's a problem between ReadyNAS and Win 7 x64.
Can anyone offer any positive suggestions, please ?
I have recently retired that m/c and replaced it with a Win7 x64 machine. I've used much the same disk naming and folder structure as before.
I've gone to edit my backup jobs (changing to the new computer's network name, etc) but I'm getting this unhelpful error message when I test the connection.
Error connecting to //Lunga/LungaData/documentsTim
The computer's network name is 'Lunga', and the 'D' partition on the hard drive is called 'LungaData' (It's Windows share name is also 'LungaData')
I've applied 'Advanced Sharing' to 'LungaData' and sharing to the folder 'documentsTim'. It's a pity that the ReadyNAS documentation is silent on the possibility of there being any errors at this stage.
The WinXP computer connected without problem on '//Islay/IslayData/documentsTim' (I've NOT used the slashes in the FrontView entry boxes, of course).
I've tried every combination I can think of, but always the same error message. I've also tried creating new jobs, instead of editing old ones, but get the same error.
I have a second (physical) drive in this m/c, which contains all the files from the old one. I can connect to that without difficulty as '//Lunga/IslayData', where of course 'IslayData' is the Windows share name of that hard drive. No login or password required here. I've applied the same share permissions to this HD as to the 'D' partition on the main drive. I think this must mean that the ReadyNAS can 'see' the computer 'Lunga', but can't see the logical drive 'LungaData'. There was no problem with it seeing the logical drive in WinXP.
I have applied all the changes suggested by HERBIEO at http://www.readynas.com/forum/viewtopic.php?f=31&t=62968&start=15#p356698, but to no effect.
I could have made a silly mistake, of course, and I continue to look for it. But I begin to wonder if it's a problem between ReadyNAS and Win 7 x64.
Can anyone offer any positive suggestions, please ?
7 Replies
Replies have been turned off for this discussion
- If you've had the Duo for 3 years, then you have a Duo V1 (yes, the labels are misleading!). But the v2 was launched last fall, and is a completely different platform.
Are you running 4.1.8 firmware? - BTW, it looks like the NAS is able to access one hard drive, and not the other?
Are both drives formatted identically (I am wondering if one is NTFS and the other is FAT32 for instance).
Also note that in Windows the share permissions and the file/folder permissions are distinct. Windows intersects the permissions, so the result can be more restrictive than either (and is never more permissive). - Thank you for your two replies.
I AM confused about the labelling. The hardware's not much help, but the CD that came with it says it's a 'ReadyNAS Duo RND2000 Series. That does appear to have had a 'V2', so probably that's where I'm confused.
I downloaded new firmware yesterday. That's RAIDiator 4.1.9, but (in the light of version confusion) I suspect I should not have done that, as I read somewhere on the NetGear site that the V1 and V2 firmware were not compatible. However, it appears to be running without difficulty. The access problem arose before installing it, and I did that in the hope it would solve the problem. Probably I should go back and download the right firmware. (It's odd that it installed without complaint).
Yes, I can access one drive, but not the other. Both drives are NTFS.
I checked the sharing on the two drives: IslayData (the one I CAN access) has Advanced Sharing set to 'Everyone - Read'. LungaData (which I can't access) has 'Everyone - Full Control', so in that respect it's MORE permissive. Cutting it back to 'Read' didn't help any. I have also tried disregarding the folder 'documentsTim' in both cases, and tried just accessing the drives as:
HOST: Lunga; PATH: IslayData (success)
HOST: Lunga; PATH: LungaData (failure).
The only other obvious difference between the drives is size: LungaData is a 800GB (approx) partition on a 1TB drive, IslayData is a 150GB drive. The drives in the ReadyNAS are 500GB each (mirrored, can't recall the RAID number). But the data (in 'documentsTim') I'm trying to back up is nowhere near that size. In accessing the drive only (as above) could the size discrepancy make a problem ?
I will report back when I know I've got the right firmware.
Later: RAIDiator 4.1.9 seems to be OK for my product. - 4.1.x firmware is definitely V1 (sparc platforms). The problem is that Netgear also uses v1, v2, v3... as minor hardware upgrades. In this case, they used "v2" to mean two different things in the same product family.
Anyway, you keep talking about the sharing settings (which are relevant of course). But you haven't talked at all about the security tab settings, and they are just as important. The most restrictive setting in both categories is what determines the effective permissions. Maybe as a test you can add "everyone" as a user on the security tab and give them full control? - Thank you. I hadn't thought to change the settings on the Security tab - never had occasion to do it before.
There was no 'Everyone', so I created it on the LungaData drive.
It worked (to the point that 'Test Connection' connects). I was able to set the permission back to 'Read and Execute' ('Write' is unchecked). Anything less failed.
So a Great Leap Forward, thank you.
I'm unsure what the wider security issues may be. I have firewall and Internet Security. The only other (occasional) user of this computer is my wife.
Other computers on our network (my laptop, my wife's computer) seem able to access files on this computer without this new security relaxation. Isn't there some way to enable the ReadyNAS to do the same ? - Full control read permissions will allow anyone connected to your home network to read the files.
The other computers are likely using credentials (username/password) that the new PC recognizes.
You can try putting the PC username/password on the source in the backup job - that might allow you to tighten up the permissions.
You could also create a new user on the PC that has read access to the files, and use that user/password on the source. - Everything is working as I'd like it to now.
I'm no expert on Network Security, I'm just glad when I can 'see' one computer from another (which I can with current settings). I did try making my wife a User on this new m/c, but then when I tried to view this m/c in Windows Explorer from her computer I got a Login dialog which I couldn't 'satisfy'. I removed her from this computer, and all is well again (if not as secure as it might be).
Thank you for your help and patience.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
