Announcement

Collapse
No announcement yet.

Last logon from domain controller error

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Last logon from domain controller error

    I am exporting information on All users and getting an error when it's checking the different domain controllers. "Getting last logon information from 'LDAP:///CN=Administrator,CN=Users,DC=zintl,DC=com'...Unabl e to open directory object 'LDAP:///CN=Administrator,CN=Users,DC=zintl,DC=com'. E_ADS_BAD_PATHNAME. I get this for each user that is queried against. I am successfully checking 2 of our 3 domain controllers. Please let me know why I'm getting this message and how to resolve it.

    Additionally, I can check individual users last logon by right clicking on the user, select View Logon Infomation and check all DC's.

    Thanks
    Jeff

  • #2
    Re: Last logon from domain controller error

    Give us the exact steps you are taking to run this.

    Comment


    • #3
      Re: Last logon from domain controller error

      exact steps I'm taking to view and export last logon

      1. In Object Manager, AD Queries tab, Users (Detailed - General) added Last Logon to Query Directory Attributes. Last Logon is now displayed in the Users (Detailed - General) tabular view.

      2. Tools, Exporter Pro, Export Selected Objects, Settings > in Config Properties open AD (users, groups) / Detailed Users. Add Last Logon, Set Options > in Set User Export Options enable exporting user info from all DCs. Close Config Props and back on Export Selected Object > Start Export.

      On the Exporter screen I see the user then 3 entries for DC's. The first two are correct and the last one is blank with the error message. This happens for each user.

      Also, in Hyena's tree view it is listing one of our previous BDC's as a DC and not listing a current DC that should be there?

      Comment


      • #4
        Re: Last logon from domain controller error

        In the LDAP: path that you provided above, you indicated "LDAP:///". That is one too many slashes. Is that a typo or is that what is actually shown in the error ? You can verify the path for any object by double-clicking on it in the left window of Exporter Pro.

        As for adding the lastlogon information to Hyena's queries, I assume you know that this will only get the lastlogon (or any attribute) from only one DC. The only way to see a combined lastlogon from all DCs in Hyena is to use the View Logon Information function.

        Is the 3rd DC that you are seeing operational ? Both Hyena and Exporter Pro use the same function to get a list of DCs from AD, but this is a Microsoft function. How it works is anybody's guess. There could be a replication or directory issue on why AD is still showing the remaining DC. Is this the same DC that is showing this error ?

        On the Exporter screen I see the user then 3 entries for DC's. The first two are correct and the last one is blank with the error message. This happens for each user.

        Also, in Hyena's tree view it is listing one of our previous BDC's as a DC and not listing a current DC that should be there?
        Kevin Stanush
        SystemTools Software Inc.

        Comment


        • #5
          Re: Last logon from domain controller error

          The LDAP path I supplied is acorrect path and not a typo.
          I am able to export lastlogon info from DC's separately using your suggestion in my other topic.

          The 3rd DC is operational and is the one showing the error but it is a Windows NT 4 Server machine. Does this mean I'm outta luck or can Hyena gather information from NT based servers?



          [This message has been edited by jrohr (edited 10-27-2006).]

          Comment


          • #6
            Re: Last logon from domain controller error

            Looking at your post above, it isn't clear what you are selecting when you first use the Export Selected Objects option. Are you selecting users in the right window, or the domain itself?

            Also, in Hyena, right-click on a user and choose View Logon Information and then click Check All Domain Controllers. Do you get results from all 3 controllers?

            Comment


            • #7
              Re: Last logon from domain controller error

              I am selecting all users in the right window when using Export Selected Objects.

              Yes, I get results from all DCs when using the View Logon Information for a single user. I've verified the information is different for each DC as well.

              Comment


              • #8
                Re: Last logon from domain controller error

                Additionally, if you go to File->Manage Object View and click on your domain. Beside the ADSI Path box is a button with ... on it. Click that and find your domain in the list. Does that change the path from what you had previously? If so, click Update to save the change, then OK to close Object Manager.

                Run the export again the way you have been. If that still does not fix the issue, send some screen shots of everything to [email protected]temtools.com so we can see if we can get to a faster resolution for you.

                Comment


                • #9
                  Re: Last logon from domain controller error

                  The last logon exporting in EP won't work due to one of the domain controllers running NT 4.0. The LDAP path isn't valid in the error message, and this is probably due to the missing DC running NT 4.0. I suspect that if you look at the domain controller listing in Hyena, the DNS path will be blank, which is why the path is not right. Even if it had a DNS path, I don't think that the NT 4.0 controller would respond to the LDAP request.

                  I've looked at several ways to work around this and none of them work for a mixed NT 4.0 and Windows 200x set of domain controllers for reporting last logon information.
                  Kevin Stanush
                  SystemTools Software Inc.

                  Comment


                  • #10
                    Re: Last logon from domain controller error

                    Then I guess we'll have to wait until we take our NT Server machine out of production for net logons to get a report of lastlogon data. Thanks for troubleshooting this with me.

                    Comment

                    Working...
                    X