administrator error 1326

Avast Business Avast Distributed Network Manager
1

Installing using ADNM.

XP workstation installs all go fine once Windows firewall settings opened up.

However, Win2k machines refuse to allow access or installation showing “administrator error 1326” in the install log.

Discovery services correctly identify machine and OS.

Since XP goes fine, I would like to assume the 2k machines have a sharing setting that needs to be opened for AVAST and ADNM.

All suggestions will be appreciated.

Bob

2

Error code translates to “Logon failure: unknown user name or bad password.”

Are you sure the supplied username/password is valid for these machines?
Are the machines part of a domain? Are you using a domain account?

3

The instll is coming from a domain administrator account and there is an administrator user, with the same password on the machines.

4

Try doing something like

net use * \win2kmachine\c$ /user:DOMAIN\user password

from the AMS (towards the Win2K machine, with the same username/password as you specified in the deployment task). Does it work??

If not, avast has no way to access the remote machine…

5

I would like to do a final reply for all of those that have had this same problem. Crazybob and I finally realized what was causing the problem. It was not the actual login to the domain with the administrator password, which we could do with no problem, but it was being able to login to the local machine with the administrator password.

In other words, if you cannot get into the local machine as an administrator, then there is excellent chance that avast will not either. This is where I believe the error 1326 is coming from.

So do the following if this happens:

  • Login to the domain as administrator
  • In Control Panel open User Accounts (Users & Passwords for 2000)
  • Highlight the administrator account for the local machine, if it does not exist then add it (Be sure to put in the local PC name in where it ask for the domain name).
  • Click on Reset Password for the local machine
  • Reboot and have and login on the domain either as the user or administrator. It should now work!

One last note, if the above still does not work, go in locally as administrator and rename it. At this point it will definitely work. Please note that to use this as a final resource, whereas, the above should work.

:smiley: