Unfortunately, there are no settings within our
software that will either cause or prevent a 1326 error from
occurring. Please also understand that this specific error is
coming from the Operating System itself and not from our software.
Our software simply asks the Operating System on your local machine
to execute standard Microsoft Windows API calls to connect to the
remote machine, and its your Operating System that is returning
this error message back to our software.
You should also be able to duplicate this error completely outside of our software, by trying to map a drive to the admin$ share on the remote machine.
We have done extensive testing with regard to the 1326 issue, and whenever we see this specific error we have always been able to duplicate it within the Operating System itself. Therefore, it could be some type of Policy (Domain or Local Security Policy, etc...) setting within the O/S that is causing this to occur. We’ve also had other users tell us this specific error was directly related to an Admin Rights issue within the Policy settings within their environment, but they never wrote back to explain exactly which setting within their environment that was causing their issues.
Unfortunately, if you cannot connect to the machine via the O/S itself, they you also cannot use those credentials to connect using our software either. Therefore, you may also want to try creating another Administrator account, and then also try using that account to connect to the remote machine.
However, there are a few other things you can try out:
1. If the remote machine is running Windows XP, make sure that "Simple File Sharing" is disabled on the remote machine. Simple File Sharing only exists within Windows XP, and should not be confused with File & Printer Sharing which exists in all Operating Systems.
Basically, this is how you disable "Simple File Sharing" in Windows XP Professional (remember it cannot be done in XP Home):
Open My Computer.
Select Tools / Folder Options.
Click on the View Tab.
Go all the way to the bottom of the list and
Disable "Use simple file sharing (Recommended)".
2. We recently received this feedback from another user. So you can try this out as well. Try adjusting the "ForceGuest" policy setting on the remote machine to make sure all users authenticating to this machine over the network are actually authenticating as themselves, and not as the Guest account.
This policy can be found in the Local Security Policy on the Remote Machine:
Administrative Tools -> Local Security Policy -> Security Options -> Network access: Sharing and security model for local accounts
…and change from "Guest Only – local users authenticate as Guest" to "Classic – local users authenticate as themselves".