Unfortunately, the debug log didn't provide detailed information to understand the issue. Thank you for sending us the support zip. I also tried Mapping the Shared folder in the Guest OS and setting that in SyncBack as well. I even tried changing it to something simple with only lowercase letters (as I mentioned above), and no spaces or punctuation (which I know can sometimes mess things up). So I tried adding underscores to the ACTUAL directories name to match. VirtualBox added Underscores in place of the spaces to the name. When initially navigating to it in the virtual machine, VirtualBox links it to the VM as a Network name like so: Maybe this might help give us a clue as to what the problem MIGHT be: If there is a "Virtual IP Address" I could use/try, what might that be? Something that I might be able to tell SyncBack to use OTHER than a "UNC Path"? Rather than an "IP" address, does anyone have another suggestion that might give me a clue as to how VirtuaBox "Networks" shared folders to the Guest OS's?
I don't think that will work as I think this is a "Virtual" network connection. If I understand the suggestion, on the SyncBack Forum, they have suggested that I use an "IP" address instead of a "UNC path". which suggests that the resource name entered is invalid.Ĭan you please try using ' IP Address' instead of the host name in the UNC path to see if it resolves your issue(for example: \\IP Address\ DON.T_DELETE_-_Drawings\)įYI, I have changed the name of the folder to something simple (only lower case letters, no spaces, no punctuation) and I still get the same error message. You can refer to this link for the return value: Is returned from Windows, when SyncBackPro is trying to establish a network connection using Windows API call.
0 kommentar(er)
