3 Replies Latest reply on Jun 14, 2012 3:17 PM by SolarWinds Community Team

    Problem managing a client

    SolarWinds Community Team

       

      I am unable to manage a new client on our network

       

      Source: Data Grid Server (SBSUTILITY02)
      Device: demerson.sbs.nycnet
      Details: Computer connect
      Exception occurred at 5/24/2011 10:34:58 AM: Attempt to connect to demerson.sbs.nycnet failed.
      The following attempts were made:

       

      ARP Resolution result: No
      DNS Resolution result: Yes
      NETBIOS Name Resolution: Yes
      MS Endpoint Mapper: Yes
      WMI Connection: No

       

      Call was canceled by the message filter
      COM Exception: Error Code: 0x80010002 . Unable to connect using account DEMERSON\administrator
      EminentWare Provider Connection: No

       

      Call was canceled by the message filter
      COM Exception: Error Code: 0x80010002 . Unable to connect using account DEMERSON\administrator
      File and Print Sharing Ports: Yes

       

      Successfully connected to direct hosting NetBIOS over TCP-IP port 445 which is required for 'File and Print Sharing'

       

      Any advice or assistance would be appreciated.

      Thank you.

      Omar

        • Re: Problem managing a client
          SolarWinds Community Team

          Verify you can currently ping the machine by name.

          Verify that the account specified in the error is an admin to that machine

           

          From the EminentWare Server machine:

          • From run or from a command prompt launch wbemtest.exe
          • Click on the Connect button
          • Edit the default path with \\machinename\root\default
          • Supply the credentials used in the EminentWare credential ring (also in the error message) to connect to that client
          • Click Connect.

          If you are unable to connect using wbemtest:

          • This could be that the Firewall is blocking WMI
          • This could be because dcom is disabled on that client machine

          Check the firewall on the client machine:

          To check that DCOM in enabled - From the client machine:

          • Launch dcomcnfg from run or from a command prompt
          • On Windows7 - Under Console Root -> Component Services -> Computers right click on my computer and choose properties
          • Check on the Default Properties Tab and make sure Enable Distributed COM is checked.

          -Sean

            • Re: Problem managing a client
              SolarWinds Community Team

               

              I am having this exact same error. 

              i am able to succesfully connect using wbemtest.exe to the server.

              however when i try to run a report now or go to any tab in computer explorer i get the following error

               

              Source: Data Grid Server (STRW007021)

              Device: pdgmsoad02.mso.net

              Details: Computer connect

              Exception occurred at 3/13/2012 12:58:02 PM: Attempt to connect to pdgmsoad02.mso.net failed.

              The following attempts were made:

              ARP Resolution result: No

              DNS Resolution result: Yes

              NETBIOS Name Resolution: Yes

              MS Endpoint Mapper: Yes

              WMI Connection: No

              Call was canceled by the message filter

              COM Exception: Error Code: 0x80010002 . Unable to connect using account mso\msoadmin

              EminentWare Provider Connection: No

              Call was canceled by the message filter

              COM Exception: Error Code: 0x80010002 . Unable to connect using account mso\msoadmin

              File and Print Sharing Ports: Yes

              Successfully connected to direct hosting NetBIOS over TCP-IP port 445 which is required for 'File and Print Sharing'

               

              please help thanks

                

                • Re: Problem managing a client
                  SolarWinds Community Team

                   

                  Can you access the machine with the System Information tab of Computer Explorer?

                  The reason this is significant is that the System Information tab does not require the EW WMI Provider to be present. If that tab fails to connect, we can focus our efforts on core WMI issues, rather than ExtPack specific issues.

                  One scenario in which I have seen this message generated is when an intervening firewall is blocking access to the WMI Ports. In fact, it happened to me. I had my firewall configured to allow access on ports 1024-3999, which in most instances should have been sufficient for a Win2003 client machine. However, as it turned out, the RPC EM assigned a port higher in the grid and the connection was failing because the firewall was blocking it. (I had replaced that client machine recently, so it's also possible that the previous machine had been customized to only use 1024-3999.)

                  More details on the specific port requirements for WMI can be found in the white paper EminentWare Components, Communications, and Required Ports.