Trouble backing up to/from Win7 machines

What version of RAIDiator is on the Pro Business?

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).

mdgm wrote:
What version of RAIDiator is on the Pro Business? 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

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.

Looks like the OP has gone to bed, but I have exactly the same problem.

My NAS is an ULTRA6 Radiator:-

Hostname: ULTRA6

Model: ReadyNAS Ultra 6 [X-RAID2]
Serial: 2EE20ARV00361
Firmware: RAIDiator 4.2.15
Memory: 1024 MB [DDR2]

IPv4 address: 1: 192.168.1.2
IPv4 address: 2: 192.168.1.3


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?

Any ideas?

ewok wrote:
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.

Mark

My Windows 7 is 64 bit as well, so it appears Frontview Backup is not compatible with W7 64 bit.

Maybe one of the developers will pick up on this and provide a response.

Clayton

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.

mark