7 Replies Latest reply on Oct 3, 2017 11:21 AM by cwinning

    Invalid Credentials

    swichowski Rookie

      I have 10 machines on my network that are receiving the following errors

      In the server logs I receive Error =5    and          System.ComponentModel.Win32Exception: Access is denied    

      On the Shavlik Operations Monitor it says Credentials invalid

      No logs are created on the machines being scanned only on the server

      All other machines scan and patch fine.  They are in the same OU as other machines and receiving the same policy's.

      I have tried multiple credentials

      Check the firewall

      Moved the computer to no policy's group and back.

      I can log into the machine with the credentials I scan it with and get to the registry.

      I can Ping and URL to the machine from the server.

       

       

       

      Thank you

      Steve.

        • 1. Re: Invalid Credentials
          cwinning CommunityTeam

          Hello,

           

          What does this return?  net use \\machinename\IPC$

           

          Thanks,

          Charles

          • 2. Re: Invalid Credentials
            swichowski Rookie

            The command completed successfully

            • 3. Re: Invalid Credentials
              cwinning CommunityTeam

              Hello,

               

              Not logs on the target would be created because of the scan failure.

              Logs from the console would help, they would show you how we are resolving it by.  Machine Name, FQDN or IP address.

              How are you credentials added?  domain\account?

               

              Something to test:

              Enable All logging in Tools > Options > Logging

              Create a new Machine Group and add a single machine by machine name.

              Add credentials to the Machine Group. (verify these credentials are valid for the target. I would suggest typing the password again in Manage > Credentials)

              Attempt a scan.

               

              Thanks,

              Charles

              • 4. Re: Invalid Credentials
                swichowski Rookie

                Error 201 Network Connection Error. Verify that you can remotely log on to the specified machine

                • 5. Re: Invalid Credentials
                  cwinning CommunityTeam

                  Hello,

                   

                  We're going to need logs from a test like this, they will provide more information on what is failing during the scan.  Open a Support Case and provide the following:

                   

                  Make sure logging is set to All, Tools > Options > Logging.

                  Scan the machine from the test Machine Group.

                  Provide all the logs (zipped) from C:\ProgramData\LANDESK\Shavlik Protect\Logs

                  Take a screenshot of the Machine Group too.

                  Attach everything to the case.

                   

                  Please let me know if you have any questions.

                   

                  Thanks,

                  Charles

                  • 6. Re: Invalid Credentials
                    swichowski Rookie

                    This is a disconnected network and I can not take any logs off of it for security reasons

                    • 7. Re: Invalid Credentials
                      cwinning CommunityTeam

                      Hello,

                       

                      Well that is going to make this more complicated, the error 201 could indicate a network issue, DNS issues, permissions issues or other issue.  It may be advisable to crack open the logs and look at logs from C:\ProgramData\LANDESK\Shavlik Protect\Logs

                       

                      ST.EngineHost.managed.username@* is the important one here.  This will show the resolution of the target.  Look for errors and verify the DNS is looks correct.

                      ST.EngineHost.native.username@* is for the scan.  This may show you errors when it tries to connect.

                      ST.Protect.managed.username@*  This may show you errors when it tries to connect.

                       

                      You have 10 machine that won't scan, but other do.  Since the console would attempt to connect to the machines using the same method, there must be something different with these machine. Any ideas?  OS?  GPO? LAN or WAN?

                      What version console are you running?  Help > About will give you version and build.

                       

                      Try scanning the target by IP and FQDN. (separate tests)

                       

                      Thanks,

                      Charles