NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Ridcully
Apr 12, 2010Aspirant
Error connecting to. Win 7 starter issues ?
Is there a bug in the front view software?
There are so many threads with people being unable to get the test connection to work and just being left wih error connecting to. Its obviously not just me.
Can we have some guidance please.
I've selected
remote windows/ nas tiemstamp
host = name of the computer with no slashes or anything like that
path = d as I want to back upthe entire d: drive
login and password as per login to the machine.
Browse option never light up
There are so many threads with people being unable to get the test connection to work and just being left wih error connecting to. Its obviously not just me.
Can we have some guidance please.
I've selected
remote windows/ nas tiemstamp
host = name of the computer with no slashes or anything like that
path = d as I want to back upthe entire d: drive
login and password as per login to the machine.
Browse option never light up
27 Replies
Replies have been turned off for this discussion
- I'm guessing the OP eventually got this sorted as he never responded to the last post.
I'm having the same issues as above. "Error connecting" etc, etc.
This is the main error message I get from the log after it tries to run.
Reason for failure:
Unable to access remote path //PC1-PC/I:
I've tried with with ip address (static) and host name. Logins are correct and I can login via the laptop and view/edit intended backup path.
Ideas please?
I used to use secondary software for this, but decided I've give this a go via Frontview, as I assume this is one of it's intended purposes. I can go back to Second Copy if needs be, but now I'd like to get this working.
Thanks. - ewokNETGEAR ExpertIf you're trying to backup the I: drive, I believe the correct path should be I$.
- RidcullyAspirantI'd left i so long to get round to trying again that I came across a different problem and so started a new thread
Based on the replies to that thread, the problem was I was trying back up the entire drive, which causes issues. Apparently you need to back up folders
http://www.readynas.com/forum/viewtopic.php?f=31&t=47984 refers
Still having problems about the correct syntax for folders though - Thanks for the replies Ewok and Ridcully.
I have tried the command suggested by Ewok, but it still doesn't work.
I've also tried individual folders, like this: i:\My Folder. But I still get the same unable to connect message.
I've tried with ip addy 192.168.1.102, and host name.
I'll keep an eye on your other post Ridcully, thank you. - ewokNETGEAR Expert
InTheShires wrote:
I've also tried individual folders, like this: i:\My Folder. But I still get the same unable to connect message.
You would need to put a share name in the path, not a filesystem path like i:\My Folder. Try sharing the folder and seeing if that works. ewok wrote: InTheShires wrote:
I've also tried individual folders, like this: i:\My Folder. But I still get the same unable to connect message.
You would need to put a share name in the path, not a filesystem path like i:\My Folder. Try sharing the folder and seeing if that works.
Not 100% certain I understand, sorry.
But, the whole drive is shared under Windows, if that's what you mean? :oops:
So, should it be like this? \\my-pc\i hdd3\my folder
???- ewokNETGEAR ExpertWell, if you can't connect to the shared drive (\\my-pc\i$), it's unlikely you'll be able to get to a subfolder of that drive unless the folder is shared separately. Have you tried connecting to the I drive share using another PC?
ewok wrote: Well, if you can't connect to the shared drive (\\my-pc\i$), it's unlikely you'll be able to get to a subfolder of that drive unless the folder is shared separately. Have you tried connecting to the I drive share using another PC?
Yes, I can connect to all Windows shares via all PC's in the house. That has never been issue. (Second Copy has been performing these tasks for me ages now, with no problems. I just thought, given that it's supposed to be able to do it, I'd let Frontview run the tasks, instead of using a third party app.)
This is a screengrab of the error. I've tried linking to three separate W7 PC's in the house, but get the same error no matter which PC, or whether I use Host name, ip and whatever share is available on that particular PC.
- ewokNETGEAR ExpertIt looks like your slashes are going the wrong way. What exactly do you have in the host and path fields for the backup?
FULL Backup started. Mon Dec 13 23:21:12 GMT 2010
Job: 001
Protocol: cifs
Source: //192.168.1.XXX/d$
Destination: [Desktop]/
Backup failed. Mon Dec 13 23:21:14 GMT 2010.
Reason for failure:
Unable to access remote path //192.168.1.XXX/d$.
The backward slashes were just desperate attempts from me trying different things to get this working.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!