Cannot connect to source

[bhenshaw]

I am frequently (but not always) getting a "Cannot connect to source" error when trying to sync from my wife's laptop to my desktop. I have a group which contains four profiles that sync different folders on her computer to mine. The first profile often fails with that error, but the other three work fine. When they are done if I restart the first profile, it will work fine.

Sometimes the entire group works just fine without this error occurring.

Her computer and mine are not in sleep mode or hibernation when this happens. Hers is running Windows 11 and mine is running Windows 10. Syncback SE is running on my computer. I am accessing here computer through our wi-fi network using:

\\<computername>\Users\<username>\<path for folder to copy>\

Anyone know why this might happen? is there something I can do to keep the first profile in the group from failing?

I tried searching in the forums, but didn't find anything.

Thanks,
Bill

[mmullins_98]

A couple of questions:

1. What version of SyncBackSE are you running?
2. Are you manually starting SyncBackSE or is it started with Windows Task Scheduler?
3. Are the profiles in the group being run in parallel?
4. If not run in parallel could you change the first profile in the group to not be the first and see if it matters when run?
5. Is the path to the folder on the destination on a USB or NAS?

[bhenshaw]

A couple of questions:

1. What version of SyncBackSE are you running?

v 10.2.68.0 64-bit

2. Are you manually starting SyncBackSE or is it started with Windows Task Scheduler?

I have the option set to start with windows.

3. Are the profiles in the group being run in parallel?

No... sequentially.

4. If not run in parallel could you change the first profile in the group to not be the first and see if it matters when run?

I will give that a try and let you know what happens.

5. Is the path to the folder on the destination on a USB or NAS?

The destination is a folder on my computer in My Documents.

[bhenshaw]

Sorry, I answered from memory and one answer I gave was incorrect.

5. Is the path to the folder on the destination on a USB or NAS?

Actually, the folder is on a Western Digital portable hard drive attached to my computer via USB.

[mmullins_98]

It is sounding like the network connection may be slow to connect upon Windows start up.

Try modifying your first profile in the group and under "MISC." put a few seconds for the "Pause for < 0> seconds before the profile starts scanning for changes (helps with Network connection problems)".

A delay option is also available in Windows Task Scheduler where the Conditions are set to start the task. Look at "Advanced settings" "Delay task for: xxx".

[bhenshaw]

Try modifying your first profile in the group and under "MISC." put a few seconds for the "Pause for < 0> seconds before the profile starts scanning for changes (helps with Network connection problems)".

I added a delay of 2 seconds and have not been having any problem since then.

Thanks for the tip.

Bill

[okbitell]

Try modifying your first profile in the group and under "MISC." put a few seconds for the "Pause for < 0> seconds before the profile starts scanning for changes (helps with Network connection problems)".

I added a delay of 2 seconds and have not been having any problem since then.

Thanks for the tip.

Bill

I've got it and I'll try this

[bhenshaw]

I'm still having the problem about 10% of the time. It doesn't help to change around the order of the profels in the group. group.

Bill

[bhenshaw]

I think I figured out what was causing the problem. It didn't help to add any delay or to change the order of the profiles in the group.

What did help was changing the name of the source.

Originally the sources were defined like this: \\LG2022\Users\xxxx\... where LG2022 is the computer name. Most of the time I wouldn't get the error. About 20 or 30% of the time I would get the error "Cannot connect to source".

I changed the source to be \\10.0.0.78\Users\xxxx\... where 10.0.0.78 is the IP address. I made the change a couple of weeks ago and haven't gotten the error yet.

So it looks like the problem had something to do with converting the computer name to the IP address.

Bill