NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Backup not working
I haven't run my regular backup jobs for a month. In that time I have:
Replaced disk #1 after failure & resynced
Replaced disk #2 after failure & resynced
Upgraded to version 4 of FrontView
None of my previously existing Remote: Windows (NAS/Timestamp) backup jobs work. I get an "unable to access remote share" error.
I have tried:
1) Resetting up the backup job - still get "unable to acess" error
2) Swapping forward slashes for back slashes - still get error
3) Verified the backup locations are reachable from other locations on my Windows network.
Attached is a snippet from one of my backup jobs. Any help would be appreciated:
--------------------------------------------------------------------------------
INCREMENTAL Backup started. Tue Jan 1 08:07:23 EST 2008
Job: 013
Protocol: cifs
Source: [media]/
Destination: //NETWORKHDD/share/media
Backup failed. Tue Jan 1 08:07:26 EST 2008.
Reason for failure:
Unable to access remote path //NETWORKHDD/share/media.
--------------------------------------------------------------------------------
INCREMENTAL Backup started. Tue Jan 1 07:05:07 EST 2008
Job: 013
Protocol: cifs
Source: [media]/
Destination: //NETWORKHDD/share/media
Backup failed. Tue Jan 1 07:05:09 EST 2008.
Reason for failure:
Unable to access remote path //NETWORKHDD/share/media.
--------------------------------------------------------------------------------
INCREMENTAL Backup started. Thu Nov 29 07:05:07 EST 2007
Job: 013
Protocol: cifs
Source: [media]/
Destination: //NETWORKHDD/share/media
`./Videos/Amazon/Thumbs.db' -> `/job_013//media/Videos/Amazon/Thumbs.db'
`./Videos/DVD/720 Width WMV/Babel.wmv' -> `/job_013//media/Videos/DVD/720 Width WMV/Babel.wmv'
`./Videos/DVD/720 Width WMV/Thumbs.db' -> `/job_013//media/Videos/DVD/720 Width WMV/Thumbs.db'
`./Videos/DVD/720 Width WMV/Lucky Number Slevin.wmv' -> `/job_013//media/Videos/DVD/720 Width WMV/Lucky Number Slevin.wmv'
`./Videos/DVD/320 Width DIVX 6/Thumbs.db' -> `/job_013//media/Videos/DVD/320 Width DIVX 6/Thumbs.db'
`./Videos/DVD/320 Width DIVX 6/LUCKY_NUMBER_SLEVIN.avi' -> `/job_013//media/Videos/DVD/320 Width DIVX 6/LUCKY_NUMBER_SLEVIN.avi'
`./Videos/DVD/320 Width DIVX 6/Casino Royale.avi' -> `/job_013//media/Videos/DVD/320 Width DIVX 6/Casino Royale.avi'
Replaced disk #1 after failure & resynced
Replaced disk #2 after failure & resynced
Upgraded to version 4 of FrontView
None of my previously existing Remote: Windows (NAS/Timestamp) backup jobs work. I get an "unable to access remote share" error.
I have tried:
1) Resetting up the backup job - still get "unable to acess" error
2) Swapping forward slashes for back slashes - still get error
3) Verified the backup locations are reachable from other locations on my Windows network.
Attached is a snippet from one of my backup jobs. Any help would be appreciated:
--------------------------------------------------------------------------------
INCREMENTAL Backup started. Tue Jan 1 08:07:23 EST 2008
Job: 013
Protocol: cifs
Source: [media]/
Destination: //NETWORKHDD/share/media
Backup failed. Tue Jan 1 08:07:26 EST 2008.
Reason for failure:
Unable to access remote path //NETWORKHDD/share/media.
--------------------------------------------------------------------------------
INCREMENTAL Backup started. Tue Jan 1 07:05:07 EST 2008
Job: 013
Protocol: cifs
Source: [media]/
Destination: //NETWORKHDD/share/media
Backup failed. Tue Jan 1 07:05:09 EST 2008.
Reason for failure:
Unable to access remote path //NETWORKHDD/share/media.
--------------------------------------------------------------------------------
INCREMENTAL Backup started. Thu Nov 29 07:05:07 EST 2007
Job: 013
Protocol: cifs
Source: [media]/
Destination: //NETWORKHDD/share/media
`./Videos/Amazon/Thumbs.db' -> `/job_013//media/Videos/Amazon/Thumbs.db'
`./Videos/DVD/720 Width WMV/Babel.wmv' -> `/job_013//media/Videos/DVD/720 Width WMV/Babel.wmv'
`./Videos/DVD/720 Width WMV/Thumbs.db' -> `/job_013//media/Videos/DVD/720 Width WMV/Thumbs.db'
`./Videos/DVD/720 Width WMV/Lucky Number Slevin.wmv' -> `/job_013//media/Videos/DVD/720 Width WMV/Lucky Number Slevin.wmv'
`./Videos/DVD/320 Width DIVX 6/Thumbs.db' -> `/job_013//media/Videos/DVD/320 Width DIVX 6/Thumbs.db'
`./Videos/DVD/320 Width DIVX 6/LUCKY_NUMBER_SLEVIN.avi' -> `/job_013//media/Videos/DVD/320 Width DIVX 6/LUCKY_NUMBER_SLEVIN.avi'
`./Videos/DVD/320 Width DIVX 6/Casino Royale.avi' -> `/job_013//media/Videos/DVD/320 Width DIVX 6/Casino Royale.avi'
133 Replies
Replies have been turned off for this discussion
- I have the same problem. I powered down my ReadyNas box when I went on vacation. When I returned and brought everything back up, none of my backups could access my WinNT-SP2 shares. Everything worked before....????
StuBarrett wrote: I have the same problem. I powered down my ReadyNas box when I went on vacation. When I returned and brought everything back up, none of my backups could access my WinNT-SP2 shares. Everything worked before....????
OK, got it to work. Good tips in this thread. The problem was that the IP address of my WinXp box changed and I got it to work by using the hard coded IP address for the host name. //nnn.nnn.nnn.nnn/share
Question; what do I have to do to use the host name of the machine (//host/share)? I could get another WinXp box to access the share using the host name so there is some kind of DNS capability working. Why can't the ReadyNax box do the same?
Probably a feature turned off...???
Thanks, StuStuBarrett wrote:
Question; what do I have to do to use the host name of the machine (//host/share)? I could get another WinXp box to access the share using the host name so there is some kind of DNS capability working. Why can't the ReadyNax box do the same?
You may want to try turning on the WINS feature on the NAS and setting up your PCs accordingly. I've seen at least one customer whose DNS behavior changed unexpectedly, probably at the ISP.- I think there's a fundamental question that is still not being addressed here. In most of these cases, the issue describes very similar to mine -- a situation where the NAS and PC needed to be turned off, then when they were turned back on, and the PC likely grabbed a new IP address through DNS, the NAS would not recognize the host name. The NAS appears to be holding on to old IP addresses rather than recognizing PC's strictly by host name. I think this is something that needs to be fixed by Infrant rather than worked around by us.
- StuBarrett, since you are on RoadRunner, can you try loading this page, and setting the option to disable it: http://ww23.rr.com/prefs.php
RoadRunner recently enabled a feature where failed DNS queries would redirect you to their "service" instead of responding with an expected NX (non-existant) host response. This will definately break some home lans where PCs try to query a local PC name, its not online, and they get RoadRunners IP instead, messing stuff up.
did you see it show the old IP in some logs? the more likely thing is it couldn't resolve the hostname at all. if the systems were off then just recently turned back on, the master browser elections probably weren't complete, so no one PC/Server in the LAN took control for answering what local host was which machine. WINS would resolve this issue.fourthturn wrote: The NAS appears to be holding on to old IP addresses rather than recognizing PC's strictly by host name. The browser service maintains a list of the domain name or workgroup name the computer is in, and the protocol being used for each computer on the network segment being served by the computer running the browser service. On each network segment, a master browser is elected from the group of computers located on the segment that are running the browser service.
The master browser is responsible for collecting host or server announcements, which are sent as datagrams every 12 minutes by each server on the network segment of the master browser.ewok wrote: You may want to try turning on the WINS feature on the NAS and setting up your PCs accordingly. I've seen at least one customer whose DNS behavior changed unexpectedly, probably at the ISP.
OK, what are the steps for setting up PCs to use WINS?derek wrote: StuBarrett, since you are on RoadRunner, can you try loading this page, and setting the option to disable it: http://ww23.rr.com/prefs.php
RoadRunner recently enabled a feature where failed DNS queries would redirect you to their "service" instead of responding with an expected NX (non-existant) host response. This will definately break some home lans where PCs try to query a local PC name, its not online, and they get RoadRunners IP instead, messing stuff up.
Whoa, I'm impressed!! That worked.
Weird, how mu other PCs could resolve the host name... I've never needed to use WINS since DNS always worked.
Stu- We need to keep this thread alive since I continue to have problems setting up backup jobs for my ReadyNAS NV+. I configured the ReadyNAS as a WINS server and configured each XP computer for WINS operation. When I test the backup connections I still get the error message from before, no matter how I try to specify the path. Since I haven't used WINS before I may have made mistakes in the setup, but so far it's still broken.
flexkeeth wrote: We need to keep this thread alive since I continue to have problems setting up backup jobs for my ReadyNAS NV+. I configured the ReadyNAS as a WINS server and configured each XP computer for WINS operation. When I test the backup connections I still get the error message from before, no matter how I try to specify the path. Since I haven't used WINS before I may have made mistakes in the setup, but so far it's still broken.
Does test connection work with the IP address of the source machine?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
