glassfish
  1. glassfish
  2. GLASSFISH-18327

install-node-dcom does not abide by --windowsdomain parameter

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Blocker Blocker
    • Resolution: Fixed
    • Affects Version/s: 3.1.2_b20
    • Fix Version/s: 3.1.2_b21, 3.1.2.2
    • Component/s: distributed management
    • Labels:
      None
    • Environment:

      Windows 2008 R2
      Glassfish 3.1.2_b20

      Description

      Running the command install-node-dcom ignores the --windowsdomain or -d parameters.

      asadmin> install-node-dcom --windowsdomain domain.net
      Enter the value for the hosts operand> somehost
      Enter remote password for serviceaccount@somehost>
      com.sun.enterprise.util.cluster.windows.process.WindowsException: Logon failure:
      unknown user name or bad password.
      Command install-node-dcom failed.

      As can be seen, the windows domain is ignored and the asadmin is attempting to connect to somehost with a local account.

        Activity

        Hide
        easarina added a comment -

        Byron, could you give me the fix as a patch, so I can verify the fix, using a negative testcase.

        Show
        easarina added a comment - Byron, could you give me the fix as a patch, so I can verify the fix, using a negative testcase.
        Hide
        Byron Nevins added a comment -

        BugDB 13917234

        Show
        Byron Nevins added a comment - BugDB 13917234
        Hide
        mtobler added a comment -

        Is there a release Date for this fix? I am trying to set up Clustering using DCOM on multiple 2008 R2 Servers and I consistently get the following:
        asadmin> validate-dcom --passwordfile do-not-delete gf01
        remote failure:
        Successfully verified that the host, gf01, is not the local machine as required.
        Successfully resolved host name to: gf01/172.18.11.169
        Successfully connected to DCOM Port at port 135 on host gf01.
        Successfully connected to NetBIOS Session Service at port 139 on host gf01.
        Successfully connected to Windows Shares at port 445 on host gf01.
        The remote file, C: doesn't exist on gf01 : Logon failure: unknown user name or bad password.

        I have gone through every document I can find on this issue and have verified all settings/registry kays/etc are correct and this won't go away. I get the same via the console.

        Show
        mtobler added a comment - Is there a release Date for this fix? I am trying to set up Clustering using DCOM on multiple 2008 R2 Servers and I consistently get the following: asadmin> validate-dcom --passwordfile do-not-delete gf01 remote failure: Successfully verified that the host, gf01, is not the local machine as required. Successfully resolved host name to: gf01/172.18.11.169 Successfully connected to DCOM Port at port 135 on host gf01. Successfully connected to NetBIOS Session Service at port 139 on host gf01. Successfully connected to Windows Shares at port 445 on host gf01. The remote file, C: doesn't exist on gf01 : Logon failure: unknown user name or bad password. I have gone through every document I can find on this issue and have verified all settings/registry kays/etc are correct and this won't go away. I get the same via the console.
        Hide
        Byron Nevins added a comment -

        It *is* fixed in the open-source 4.0 codebase. You could always go grab the one changed file and build it. I commented on the filename and the subversion revision number in this issue. There is no date yet for the next 3.x version of GlassFish.

        Show
        Byron Nevins added a comment - It * is * fixed in the open-source 4.0 codebase. You could always go grab the one changed file and build it. I commented on the filename and the subversion revision number in this issue. There is no date yet for the next 3.x version of GlassFish.
        Hide
        rdblaha1 added a comment -

        I do not see a reply to the comment mtobler 22/Jun/12. I receive a similar response for validate-dcom and can find no solution in an forum, blog, or tutorial. In this issue and GLASSFISH-18451 the trail ends June 2012. Where can I find an answer. (Glassfish 3.1.2.2, Java 1.6.0_45).

        The only difference for what I am getting returned is the last lines.

        Using command line:

        C:\glassfish\glassfish3122\glassfish\bin>.\asadmin --port 4892 --passwordfile C:\glassfish\glassfish3122\glassfish\domains\testing_cluster\config\dcom-passwords validate-dcom -w Rick.Blaha -v=true TestWeb2
        remote failure:
        Successfully verified that the host, TestWeb2, is not the local machine as required.
        Successfully resolved host name to: TestWeb2/10.3.30.129
        Successfully connected to DCOM Port at port 135 on host TestWeb2.
        Successfully connected to NetBIOS Session Service at port 139 on host TestWeb2.
        Successfully connected to Windows Shares at port 445 on host TestWeb2.
        dcom.no.remote.file.access : Logon failure: unknown user name or bad password.

        Command validate-dcom failed.

        I only need direction to the document solution whether found in another issue or wherever. If I am completely out of the ballpark tell me that too.

        Show
        rdblaha1 added a comment - I do not see a reply to the comment mtobler 22/Jun/12. I receive a similar response for validate-dcom and can find no solution in an forum, blog, or tutorial. In this issue and GLASSFISH-18451 the trail ends June 2012. Where can I find an answer. (Glassfish 3.1.2.2, Java 1.6.0_45). The only difference for what I am getting returned is the last lines. Using command line: C:\glassfish\glassfish3122\glassfish\bin>.\asadmin --port 4892 --passwordfile C:\glassfish\glassfish3122\glassfish\domains\testing_cluster\config\dcom-passwords validate-dcom -w Rick.Blaha -v=true TestWeb2 remote failure: Successfully verified that the host, TestWeb2, is not the local machine as required. Successfully resolved host name to: TestWeb2/10.3.30.129 Successfully connected to DCOM Port at port 135 on host TestWeb2. Successfully connected to NetBIOS Session Service at port 139 on host TestWeb2. Successfully connected to Windows Shares at port 445 on host TestWeb2. dcom.no.remote.file.access : Logon failure: unknown user name or bad password. Command validate-dcom failed. I only need direction to the document solution whether found in another issue or wherever. If I am completely out of the ballpark tell me that too.

          People

          • Assignee:
            Byron Nevins
            Reporter:
            jp2011
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: