Announcement

Collapse
No announcement yet.

More AD Problems

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

  • More AD Problems

    We currently are migrating from NT to AD domains, we are in co-existence at the moment.

    I have migrated my own machine over to AD, correct name resolution is occuring and everything else is fine.

    Except when I try to change my nice new domain in Hyena to a 2000 Domain. Hyela tells me to tun it on W2k/XP/.net machine - of which my machine is 2000.

    I hae entered the ASDI path in correctly also.

    Anyone got a fix?

    Running Win2k Pro SP2, Hyena 4.1, AD Servers are all SP2.

  • #2
    Re: More AD Problems

    What sort of error are you getting, or what is happening when you try to expand the W2K domain in Hyena left window ? At that point, Hyena gets the name of a domain controller for the domain, and that is where most problems will be noticed.

    Please send a screen shot of your domains Object Manager configuration to [email protected]. In general, your domain AD path would be either:

    LDAP://domainname
    or
    LDAP://dnsdomainname.com
    Kevin Stanush
    SystemTools Software Inc.

    Comment


    • #3
      Re: More AD Problems

      I've since found that this works under a Domain Admin but not an Account Operator, this is probably by design?

      The error when trying to open the domain in the left pane is - "This Object can only be managed when Hyena is running under Windows 2000, Windows XP, or Windows .NET. To manage Active Directory objects using Windows NT, change the domain type to be a "Windows Domain" in Hyena's Object Manager"

      I am running Win2k. I will send my screen-shot later if we still have a problem.

      Thanks!

      Comment


      • #4
        Re: More AD Problems

        This is a strange problem. When a Windows 2000 domain is expanded, Hyena checks to see if the client is running Active Directory. Since some NT 4.0 systems can run most Active Directory services, this can be a bit tricky to easily determine. What Hyena does is look for the existence of a file named "adsldp.dll" when it is first run. If it finds this file, Hyena assumes that the client is running Active Directory. See if the client that the Account Operators are using (or the account that they are using Hyena under) has access to this file.

        There are not any intentional design features in Hyena to ensure that any particular user security level can run or use any particular function.

        -kevin
        Kevin Stanush
        SystemTools Software Inc.

        Comment


        • #5
          Re: More AD Problems

          Changed the permissions to Everyone Full to no avail.

          Sent my screenshot of settings to the support email address for analysation.

          Cheers.

          Comment


          • #6
            Re: More AD Problems

            Hmm, built another machine with XP and its works fine in there with the same settings.

            Oh well.

            Comment


            • #7
              Re: More AD Problems

              We made a small change to Hyena to perhaps work around this problem. Let me know if support did not send you a url to the modified version. Essentially, we now try two different ways to find the adsldp.dll file.

              If you continue to have problems, let me know if you want to try the patch.

              fyi, XP is very unpredictable when managing Active Directory. Also, for full AD functionality, you have to load the .Net Server admin tools, but Hyena can function correctly without this.

              thanks
              Kevin Stanush
              SystemTools Software Inc.

              Comment


              • #8
                Re: More AD Problems

                Just installed the patch on the dodgy machine, and it didnt work. Still the same error "You must run on a 2000 machine" even though it is!

                Its not important to me anymore, because I have ditched that machine, but I can continue to try fixes for you if you wish.

                Comment


                • #9
                  Re: More AD Problems

                  I was having this same error. I found that I had entered the ADSI path AND the ADSI server information. Everytime I would try to get this to work it would fail with the same error msg.

                  Through trial and error, I found that by entering the path only and removing the server name took care of the issue.

                  Comment

                  Working...
                  X