

- #Goodsync connect password reset install#
- #Goodsync connect password reset manual#
- #Goodsync connect password reset windows 7#
As seen from other posts, the same error message has different solutions. Yet, this was the solution for me, in my particular case. To summarize, it is quite possible that I needed to change all of the above to finally make something so simple work. When installing, add a description to the template.
#Goodsync connect password reset install#
it is possible that the password is indeed incorrect? So I went again to the Windows 8.1 host and checked the account and lo and behold the account has no password! What? It has been going with the same password for years! Must have been the 1.5GB Windows Update that I did a few days ago. Save it as something like 'my-goodsync.xml' within /boot/config/plugins/dockerMan/templates-user You can then install it either via apps tab (Previously installed), or via Docker - Add Container, Select my-goodsync from the template drop down. What finally made the breakthrough was trying another VM that used to work perfectly but this time was producing the same error. USE USER ACCOUNTS AND PASSWORDS TO CONNECT TO OTHER COMPUTERS ~~īut I still was not able to logon successfully (using correct password!), so.
#Goodsync connect password reset manual#
Additional GoodSync Documentation: Manual Connect / Server Manual. HOME GROUP CONNECTIONS - I changed it from the "recommended" setting of Master Password Recovery Dual Master Password. ~~ I also tried something I found on the web, suspecting that the Windows 8.1 host was the problem. (I also verified the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\LmCompatibilityLevel is not an issue and that the zone and time are set identically to the host)
#Goodsync connect password reset windows 7#
Windows 7 VM guest connected to Windows 8.1 laptop host), they both must have the same Workgroup. Note: It goes without saying that on a "domainless" setup (e.g. In such case, simply add a password, and your network logon will come to life again.

What I have discovered is that this error can also occur if a single user defined in the the system has no password.

So I am fairly positive that the problem is with the client machine not with the server. However, I tried this with a different computer NOT in the domain (with a local account) and it was working. This one I cannot add to the domain because it is on another network. We have a lot of other computers connecting correctly, but they are all in the domain. The server it is trying to connect to is a windows2008 server. However, although this was working for years, it stopped working around 2 months ago. I have a windows7 machine where I connect the network drives with the following command: > net use t: \\pathname\foldername /user:Username password
