i have a readynas PRO that has been working fine for quite some time.
the environment was mostly winxp machines and one win2000 box, and i could read and write to each from the readynas.
i have since changed two of the machines to win7 64bit, and the trouble began.
when i do a frontview backup job to or from any of the win7 machines i get a error. Using the test connection is says 'error connecting to path'.
if i try connecting from each machine to each other machine, i can ping them all, and can connect to each share from each other machine, regardless of whether it is winxp or win7. this happens with firewall on or off on each machine, each using windows firewall. and i CAN connect with the readynas if i use the same settings (other than host) on the winxp machines or the win2000 machine.
settings are as follows: backup source is irrelevant backup target is Remote windows timestamp, host is the computer name, path is the path (i even tried a new share in the root of the c: drive just to test that) normal login/password, and then try test connection.
any ideas? this is a real pain for me since everything was working fine before. likely i have something misconfigured in win7, but i cant figure out what.
but the identical host/path/login/password connects from outside the readynas, so....
Have you tried specifying the IP address of the Windows 7 machine as the host, rather than the computer name?
Path should be in a format looking something like this "windowssharename/folder/folder" (no quotes).
version is 4.2.17 the latest i think
ip address; no, but hold on ill check.........same thing happens when i use the ip address as host
format is what i was using. i use the exact same format on the non win7 machines and it works fine, so there is something with the win7; either the way the nas views it, or the way i have the win7 shares set up. but they all talk to each other, so....
thanks for the suggestions. not sure what to do next
Volume C: Online, X-RAID2, 6 disks, 13% of 9250 GB used
The Windows 7 PC I am trying to connect to is identified on the network as HPA5320UK with an IP 192.168.1.14. The windows Firewall is turned off (both Home and Public).
Whether I use Timestamp or Archive, put either HPA5320UK or 192.168.1.14 in Host, put any public folder in path (using sharename or full path as per OP, the browse button remains greyed out and with any number of different admin passwords I always get the same error:-
e.g "Error connecting to //192.168.1.14/Users" or "Error connecting to //HPA5320UK/Users".
Whatever the combination of Host and Path, it is always "Error connecting to" and the Browse button remains greyed out. Basically exactly as per the OP.
As this seems specific to Windows 7 (I have Ultimate), do you think it could be connected to Homegroup?
Just tried leaving the Homegroup and leaving Firewall (both) turned off and still no joy.
Anyone else having this problem, or perhaps found the solution. Since the Browse button remains greyed out I presume there is no connection to the Host?
What error message are you getting? Try switching the protocol to archive bit, run the backup job, and see what kind of error message you get.
first, there is no archive bit protocol in the list for the destination; just the source, so i cant switch most of them.
second, right now it isnt working. however, when i checked the logs, it DID work the other day. ?????? but right now i still get the error message "error connecting to computername/users"
Just so you know, im trying to copy BOTH from the computer to the nas for backup of documents, AND from the nas to the computer (spare drive) to backup some critical files from the nas. neither works right now. and the computers they dont work on are windows 7 64 bit. everything else (winxp and win2000) work fine.
I took the plunge and installed Windows 7 Ultimate (32 bit) to test out how to connect from a ReadyNAS to Windows 7
I have a brand new setup, all defaults selected during the setup. I've left HomeGroup enabled and haven't even looked at things like the firewall settings - just logged in using the admin account created during installation once the install completed
When installation completed, Windows 7 immediately found my NAS (Ultra 4 / Firmware 4.2.17) and was able to write to a CIFS enabled share as shown below:
I then created a new user (sphardy), logged in as that user & shared the home directory of that user via the "Share with HomeGroup (Read)" menu option, resulting in the following:
I then setup a Frontview backup job as follows
Note: I selected the 'Contacts' subfolder purely as a test, and used the IP address as a precaution
After successfully testing the connection I ran the backup job as follows:
As the image shows, the job ran successfully and I can confirm data was properly copied across.
I then changed the backup job to use the hostname of the Windows installation, rather than IP address:
Again the backup completed without issue.
In summary - there doesn't appear to be a fundamental incompatibility between a ReadyNAS running 4.2.17 and Windows 7, in fact this testing couldn't have gone any easier. Maybe there's something here in these results that will help those not able to use Frontview backup to access Win 7 machines.
lets get back on track here. any new/different issues deserve their own threads.
if i try 'test connection' right this second on the jobs that connect to a win 7 machine, it fails. however, last night the backup went fine, even though the other day it didnt. NOTHING changed as far as configuration. So there is something else going on. Not saying it is the readynas, but it has to be either the nas or the win7 permission system. i get the exact same result with the nv+ and the pro when i do 'test connection' - in other words i get error when trying to connect to win7 machines, but they connect ok to winxp machines. the setup/permissions dont change from day to day, so im focused on the nas.
also, i discovered that periodically the home shares go off line on the pro box. this is when all the other shares continue on line. when that happens i only have access to a few files/directories, presumably the ones that are cached locally. No telling what is causing this. Note I have two readynas boxes, one sparc one pro x86, that have been running more or less flawlessly for several years (3 years for the x86, about 4 yrs for the sparc, without a single hardware failure). most all issues i have had with them were traced to flawed add-ons, as everything else has worked well. there are NO addons currently installed other than the Netgear default ones. i wonder if there is some remnant from one of these old addons still causing issues (i have never defaulted/reloaded the nas's as that would be a big pain, but may be my only option if i cant figure this out).
so if anyone can explain to me how the configuration/setup could cause this intermittant problem, im all ears.
in the meantime, lets get this thread back on track; ewok/mdgm, is there anything, logs etc. that might help in figuring out this issue? im willing to try anything to figure out what is going on. especially now that it seems intermittant.
When the backup did work the other day, did the logs look as expected, no errors, warnings, etc.?
I don't know what would cause an intermittent failure like that. The software on the NAS isn't changing between backup runs, and if the state of the Win7 box isn't changing, then I'm not sure what would cause the problem.
Go ahead and send me the logs and I'll see if there's anything interesting there.
When the backup did work the other day, did the logs look as expected, no errors, warnings, etc.?
I don't know what would cause an intermittent failure like that. The software on the NAS isn't changing between backup runs, and if the state of the Win7 box isn't changing, then I'm not sure what would cause the problem.
Go ahead and send me the logs and I'll see if there's anything interesting there.
yeah, kinda weird. something is definately going on, just dont know what.
tried to send logs, they are 38mb; any suggestions like direct upload or ?
I am having the same issue. I followed sphardy's instructions above. The only difference is the OS and the firmware version. My Ultra 2 came with .15 and I have not upgraded to .17. I am running Windows 7 Premium 64 bit on the laptop. I am able to backup an XP machine I have, but cannot backup the Win7 machine. I can easily copy files between the two machines so sharing is working fine.
When I set everything up I get the common test connection error, but I run the backup anyway and it says it completes successfully however no files get copied (there are two test files in the Contacts directory on the Win7 PC). Here is the log file:
====================================== FULL Backup started. Sat Jul 2 21:06:27 EDT 2011
Backup finished. Sat Jul 2 21:06:27 EDT 2011 =====================================
I used to have McAfee on the PC but removed it completely thinking that it might be a firewall issue, however, all of the other PCs in the house can see the Win7 laptop and copy files to and from it, only the NAS is having an issue with backups. I can even manually copy and paste the files between the Win7 laptop and the NAS. It appears the issue is with the FrontView Backup system.
This is frustrating as I otherwise really like the device, however it appears that there are a lot of issues with FrontView (judging by the volume of people that have unresolved problems on the forum). Anyone have any suggestions?
Ok, here is something interesting that I discovered. I can keep everything the same (host, path, etc.) except change the logid and pwd to anything I like (fictitious or real) and it will still complete successfully (but not copy files), but if I blank out the logid and pwd then it fails and I get this message in the log:
-------------------------------------------------------------------------------- FULL Backup started. Sat Jul 2 21:24:50 EDT 2011
Anonymous login successful tree connect failed: NT_STATUS_ACCESS_DENIED Files copied: 0
Backup failed. Sat Jul 2 21:24:51 EDT 2011.
Reason for failure: Error encountered copying data from remote source path //Gandalf/Users/NAS/Contacts ==> /Test/ due to permission denial on one or more files -------------------------------------------------------------------------
So it looks like the anonymous login works, but the job fails due to permission denial on the files. If you use any random logid/pwd then the job completes but the files do not copy probably because the session setup failed. I have no idea what to make of it.
This article will do it. It appears that backups are not compatible with Windows7 64 bit. Three registry tweaks and then logging in anonymously fixed the problem.
its running 4.2.19, same as my pro business is now.
and i get exactly the same result as before. but....
if i enter the info properly, it backs up. on both the pro biz and the pro 6
but, if i try to 'test connect' it fails. on both units.
i had thought the pro biz had been corrupted with some rogue software add ons, since it did have problems and was 'repaired' but now the new virgin pro 6 does exactly the same thing.
summary; 'test connect' fails on both, but backups work on both with the login info that fails test connect.
i received my pro 6, and have exactly the same issue, with the same error that saintstephen is getting. it shows as sucessful; ie a green icon next to the backup job, but it doesnt copy any files
and it says 'error' when i test the connection. so why does it say success?
Hi I too have been having the same problem as those above. I have been trying to back up my photos from my computer to the NAS. The test connection button always fails, but if I saved the options anyway I could run the backup process but no files would transfer. I tried all sorts of configuration in the path names and adjusted many settings within my Win 7 share options but nothing was working. However..... I just uninstalled Windows Live Sign In Assistant (using the windows remove programs feature from control panel), restarted the computer and tried again (without changing any settings within the Frontview). The backup is now running and I can see files in the backup share folder on the NAS!
Hurrah!! 😄 I hope this helps some of you out there too, it was driving me mad trying to work out what I was doing wrong. Good luck
Cheers Mark
I have an Ultra 2, Radiator 4.2.20 and Win 7 64 Bit Home Premium
I think there is definitely something broken with FrontView backup.
Just noticed this same behavior on my ReadyNAS Pro 6 running 4.2.20.
I have 2 backup jobs for a couple of Win7 64-bit machines - both jobs indicate they completed successfully, but with 0 files copied. Test connections fail for both and the browse button greyed out. These jobs used to work just fine and I'm not sure how long they've been broken. Played around with user IP vs. hostname, new shares, no security, FW turned off... nothing.
