Topic
  • 13 replies
  • Latest Post - ‏2017-02-07T14:19:54Z by AbhishekDanej
SystemAdmin
SystemAdmin
152 Posts

Pinned topic Unable to discover Windows 2008

‏2011-10-22T20:27:23Z |
Hey Guys,

I am not able to discover Windows 2008 from TADDM. Getting the following error message:
2011-10-22 18:48:20,373 DiscoverManager DiscoverWorker-14 SessionSensor-10.14.91.142 ERROR session.UnscopedGateway - Problem with WMI: com.collation.platform.session.SessionClientException: !!! TaddmTool Error: SELECT BuildVersion FROM Win32_WMISetting failed: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

I have checked that the user ID is with Admin rights
UAC is already disabled
Using Redhat Cygwin for ssh connection.

PLease help
Updated on 2011-11-04T13:29:23Z at 2011-11-04T13:29:23Z by doormat18
  • doormat18
    doormat18
    178 Posts

    Re: Unable to discover Windows 2008

    ‏2011-10-24T11:41:51Z  
    A couple questions, can you open a remote desktop session into the box using the account? Can you connect to C$ on the target using the account?
  • SystemAdmin
    SystemAdmin
    152 Posts

    Re: Unable to discover Windows 2008

    ‏2011-10-31T10:31:19Z  
    • doormat18
    • ‏2011-10-24T11:41:51Z
    A couple questions, can you open a remote desktop session into the box using the account? Can you connect to C$ on the target using the account?
    Hi,

    Sorry for the late response. I am able to take remote session of the server.

    For the 2nd question regarding C$, I am assuming that you are talking about drive sharing. As per security policies, we are not allow to share drives on the server. Hence, access to C$ is blocked.
  • doormat18
    doormat18
    178 Posts

    Re: Unable to discover Windows 2008

    ‏2011-10-31T12:31:50Z  
    Hi,

    Sorry for the late response. I am able to take remote session of the server.

    For the 2nd question regarding C$, I am assuming that you are talking about drive sharing. As per security policies, we are not allow to share drives on the server. Hence, access to C$ is blocked.
    Just saw this in the documentation.

    "Note: The service account must have read/write access to the \WINDOWS\system32 or \WINDOWS\system64 directory and its subdirectories. On Windows Server 2008 systems, new users do not have the required access by default, so you must explicitly grant it for the service account."

    Could this be the issue?
  • SystemAdmin
    SystemAdmin
    152 Posts

    Re: Unable to discover Windows 2008

    ‏2011-11-01T12:03:59Z  
    • doormat18
    • ‏2011-10-31T12:31:50Z
    Just saw this in the documentation.

    "Note: The service account must have read/write access to the \WINDOWS\system32 or \WINDOWS\system64 directory and its subdirectories. On Windows Server 2008 systems, new users do not have the required access by default, so you must explicitly grant it for the service account."

    Could this be the issue?
    Even after changing the access rights on Windows\system32, it is not working. Getting the same error message:

    CTJTP1163E The following WMI session and SSH sessions cannot be established (SSH: Problem with WMI: com.collation.platform.session.SessionClientException: !!! TaddmTool Error: SELECT BuildVersion FROM Win32_WMISetting failed: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)); WMI: SELECT BuildVersion FROM Win32_WMISetting failed: Access is denied.System.UnauthorizedAccessException: Access is denied. ).

    Tried also tried the following document. However, session sensor is still failing.
    http://www-01.ibm.com/support/docview.wss?uid=swg21286976

    I even provided full access to Windows\temp. I also disables Windows firewall service. However, discovery still failed with the below error message
    CTJTP1163E The following WMI session and SSH sessions cannot be established (SSH: Problem with WMI: com.collation.platform.session.SessionClientException: !!! TaddmTool Error: SELECT BuildVersion FROM Win32_WMISetting failed: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)); WMI: SELECT BuildVersion FROM Win32_WMISetting failed (0x800706ba: The RPC server is unavailable.): 0x800706ba: System.Runtime.InteropServices.COMException (0x800706BA): The RPC server is unavailable. ).
  • doormat18
    doormat18
    178 Posts

    Re: Unable to discover Windows 2008

    ‏2011-11-01T13:49:40Z  
    Even after changing the access rights on Windows\system32, it is not working. Getting the same error message:

    CTJTP1163E The following WMI session and SSH sessions cannot be established (SSH: Problem with WMI: com.collation.platform.session.SessionClientException: !!! TaddmTool Error: SELECT BuildVersion FROM Win32_WMISetting failed: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)); WMI: SELECT BuildVersion FROM Win32_WMISetting failed: Access is denied.System.UnauthorizedAccessException: Access is denied. ).

    Tried also tried the following document. However, session sensor is still failing.
    http://www-01.ibm.com/support/docview.wss?uid=swg21286976

    I even provided full access to Windows\temp. I also disables Windows firewall service. However, discovery still failed with the below error message
    CTJTP1163E The following WMI session and SSH sessions cannot be established (SSH: Problem with WMI: com.collation.platform.session.SessionClientException: !!! TaddmTool Error: SELECT BuildVersion FROM Win32_WMISetting failed: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)); WMI: SELECT BuildVersion FROM Win32_WMISetting failed (0x800706ba: The RPC server is unavailable.): 0x800706ba: System.Runtime.InteropServices.COMException (0x800706BA): The RPC server is unavailable. ).
    "RPC server unavailable" generally points to network access problems between the gateway and target.

    http://www-01.ibm.com/support/docview.wss?uid=swg21498567

    Can you reach the target from the gateway without any problems? Are you sure that you are using the gateway that you expect to use? Are there any firewall restrictions on the gateway blocking access to the target?
  • SystemAdmin
    SystemAdmin
    152 Posts

    Re: Unable to discover Windows 2008

    ‏2011-11-02T04:51:06Z  
    • doormat18
    • ‏2011-11-01T13:49:40Z
    "RPC server unavailable" generally points to network access problems between the gateway and target.

    http://www-01.ibm.com/support/docview.wss?uid=swg21498567

    Can you reach the target from the gateway without any problems? Are you sure that you are using the gateway that you expect to use? Are there any firewall restrictions on the gateway blocking access to the target?
    Hi, I have check with the network team, they said that there is a firewall in between the gateway and target server. However, Port 22, 135 and 445 are already open. I also tried wbemtest from my anchor/gateway (Both are same in our case and in different subnet from target server) to the target server and it failed to. Please let me know if any specific port is needed to be open between the gateway and target server.

    Thanks & Regards,
    Ramandeep Singh Mokha
  • SystemAdmin
    SystemAdmin
    152 Posts

    Re: Unable to discover Windows 2008

    ‏2011-11-02T10:38:29Z  
    Hi, I have check with the network team, they said that there is a firewall in between the gateway and target server. However, Port 22, 135 and 445 are already open. I also tried wbemtest from my anchor/gateway (Both are same in our case and in different subnet from target server) to the target server and it failed to. Please let me know if any specific port is needed to be open between the gateway and target server.

    Thanks & Regards,
    Ramandeep Singh Mokha
    Hi,

    I tried to run discovery on the server within the same subnet where no firewall is installed and got the following error message. I provided the full access to Windows\System32 and Windows\Temp folders as well.

    CTJTP1163E The following WMI session and SSH sessions cannot be established (SSH: Problem with WMI: com.collation.platform.session.SessionClientException: !!! TaddmTool Error: SELECT BuildVersion FROM Win32_WMISetting failed: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)); WMI: InstallProvider failed: could not copy files to remote host: System.Exception: WNetAddConnection2: No network provider accepted the given network path ).
  • doormat18
    doormat18
    178 Posts

    Re: Unable to discover Windows 2008

    ‏2011-11-02T12:58:10Z  
    Hi,

    I tried to run discovery on the server within the same subnet where no firewall is installed and got the following error message. I provided the full access to Windows\System32 and Windows\Temp folders as well.

    CTJTP1163E The following WMI session and SSH sessions cannot be established (SSH: Problem with WMI: com.collation.platform.session.SessionClientException: !!! TaddmTool Error: SELECT BuildVersion FROM Win32_WMISetting failed: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)); WMI: InstallProvider failed: could not copy files to remote host: System.Exception: WNetAddConnection2: No network provider accepted the given network path ).
    Can you temporarily enable the default admin share (C$) and see if that resolves the issue?
  • SystemAdmin
    SystemAdmin
    152 Posts

    Re: Unable to discover Windows 2008

    ‏2011-11-04T13:00:14Z  
    • doormat18
    • ‏2011-11-02T12:58:10Z
    Can you temporarily enable the default admin share (C$) and see if that resolves the issue?
    Hey Thanks.. I am able to discover it fine now.

    Here are the things which we need to ensure following before discovering Windows 2008 server.

    1. UAC need to be disabled.
    2. Any firewall should be disabled (HW/SW) - I am still trying to find out the ports which need to be open incase there is a HW firewall.
    3. TADDM user should have Read and Write permission on System32 / System64 (Depending upon the CPU bit).
    4. C:\Windows folder should be shared for the 1st time discovery and share name should be "admin$" (This share can be disabled after the discovery.

    Thanks for your support. :)
  • doormat18
    doormat18
    178 Posts

    Re: Unable to discover Windows 2008

    ‏2011-11-04T13:29:23Z  
    Hey Thanks.. I am able to discover it fine now.

    Here are the things which we need to ensure following before discovering Windows 2008 server.

    1. UAC need to be disabled.
    2. Any firewall should be disabled (HW/SW) - I am still trying to find out the ports which need to be open incase there is a HW firewall.
    3. TADDM user should have Read and Write permission on System32 / System64 (Depending upon the CPU bit).
    4. C:\Windows folder should be shared for the 1st time discovery and share name should be "admin$" (This share can be disabled after the discovery.

    Thanks for your support. :)
    I am glad you were able to discover it. I would also add to step 4 that whenever you do a TADDM upgrade (including FixPacks) you would also need to enable the share so that the new Windows discovery code can be pushed to the targets.
  • jysingh6
    jysingh6
    1 Post

    Re: Unable to discover Windows 2008

    ‏2017-01-31T12:55:35Z  
    • doormat18
    • ‏2011-11-04T13:29:23Z
    I am glad you were able to discover it. I would also add to step 4 that whenever you do a TADDM upgrade (including FixPacks) you would also need to enable the share so that the new Windows discovery code can be pushed to the targets.

    Hi,

    I am also getting the same error on few servers . I have added taddm user in administrators group and it's working for few machine. But on few machines i am getting new 2 below errors. Guys please help me. I am new to this tool.

    i checked all things you have mentioned above and all is fine.

     

    CTJTP1161E The application cannot establish the following WMI session: SessionClientException: InstallProvider failed: could not copy files to remote host: System.Exception: WNetAddConnection2: The specified network password is not correct.

    CTJTD0851E No connection could be established. The specified port could not be opened.

     

     

    Updated on 2017-01-31T13:07:41Z at 2017-01-31T13:07:41Z by jysingh6
  • doormat18
    doormat18
    178 Posts

    Re: Unable to discover Windows 2008

    ‏2017-01-31T14:17:15Z  
    • jysingh6
    • ‏2017-01-31T12:55:35Z

    Hi,

    I am also getting the same error on few servers . I have added taddm user in administrators group and it's working for few machine. But on few machines i am getting new 2 below errors. Guys please help me. I am new to this tool.

    i checked all things you have mentioned above and all is fine.

     

    CTJTP1161E The application cannot establish the following WMI session: SessionClientException: InstallProvider failed: could not copy files to remote host: System.Exception: WNetAddConnection2: The specified network password is not correct.

    CTJTD0851E No connection could be established. The specified port could not be opened.

     

     

    Looks like the copy of the files is failing. See if you can connect to the target machine manually through \\target\admin$ and transfer files. Work your way through this exercise first.

  • AbhishekDanej
    AbhishekDanej
    1 Post

    Re: Unable to discover Windows 2008

    ‏2017-02-07T14:19:54Z  
    • doormat18
    • ‏2017-01-31T14:17:15Z

    Looks like the copy of the files is failing. See if you can connect to the target machine manually through \\target\admin$ and transfer files. Work your way through this exercise first.

    Just saw this thread.. I'm facing similar problem for discovering Windows 2012 servers. This is a new setup and I have not been able to discovery any Windows server till now. Have discovered 1 Linux server.

    My TADDM server, DB2, gateway (cygwin) and anchor ..all are on single Windows 2012 machine. I have tested that wbem is working, using wbemtest server. I can even do "\\10.x.y.z\c$ from my TADDM server to target Windows server.

    In my DiscoverManager log, i see errors with my anchor service... also similar errors are visible for SessionSensor.

     

    The cygwin sshd service is running by srvadmin@mydomain domain user, while the ADDM service is running via 'ajcadmin' local user.

     

    2017-02-07 10:37:20,372 DiscoverManager [DiscoverWorker-0] 2017020710370751#AnchorSensor-anchor-@10.252.28.14-8497 WARN auth.SshKeyManager - [PLATFORM.SECURITY.W.7] can't find ssh2 key file : C:\Users\ajcadmin.TADDMDR01\.ssh\id_dsa
    2017-02-07 10:37:20,372 DiscoverManager [DiscoverWorker-0] 2017020710370751#AnchorSensor-anchor-@10.252.28.14-8497 DEBUG session.SshSession - @SSH: attempt failed: TRYING ajcdom\srvadmin[[ssh2,useKey=1]: SessionClientException: CTJTP1002E The following ssh2 key file is not found: C:\Users\ajcadmin.TADDMDR01\.ssh\id_dsa @com.collation.platform.session.SshSession$SshSessionValidator@6f2cd8b6
    2017-02-07 10:37:20,372 DiscoverManager [DiscoverWorker-0] 2017020710370751#AnchorSensor-anchor-@10.252.28.14-8497 WARN auth.SshKeyManager - [PLATFORM.SECURITY.W.6] can't find ssh1 key file : C:\Users\ajcadmin.TADDMDR01\.ssh\identity
    2017-02-07 10:37:20,372 DiscoverManager [DiscoverWorker-0] 2017020710370751#AnchorSensor-anchor-@10.252.28.14-8497 DEBUG session.SshSession - @SSH: attempt failed: TRYING ajcdom\srvadmin[[ssh1,useKey=1]: SessionClientException: CTJTP1001E The following ssh1 key file is not found: C:\Users\ajcadmin.TADDMDR01\.ssh\identity @com.collation.platform.session.SshSession$SshSessionValidator@6f2cd8b6
    2017-02-07 10:37:20,372 DiscoverManager [DiscoverWorker-0] 2017020710370751#AnchorSensor-anchor-@10.252.28.14-8497 DEBUG session.SshSession - Trying Password SSH version=[2] host={addressType=6;stringNotation=10.252.28.14;isPlaceholder=false;}] user=[ajcdom\srvadmin]
    ..
    ..
    ..
    2017-02-07 10:37:20,549 DiscoverManager [DiscoverWorker-0] 2017020710370751#AnchorSensor-anchor-@10.252.28.14-8497 DEBUG session.SshSessionClient - Setting up SSH session to com.collation.platform.security.auth.WindowsHostAuth[ajcdom\srvadmin][XXXXX]/null@{addressType=6;stringNotation=10.252.28.14;isPlaceholder=false;}
    2017-02-07 10:37:24,764 DiscoverManager [DiscoverWorker-0] 2017020710370751#AnchorSensor-anchor-@10.252.28.14-8497 DEBUG session.Ssh2SessionClient - Error in creating SSH2 Session to ajcdom\srvadmin@10.252.28.14: Exception: [SSH2FatalException: Permission denied; SSH2FatalException: Permission denied]
    ..
    ..
    2017-02-07 10:37:24,768 DiscoverManager [DiscoverWorker-0] 2017020710370751#AnchorSensor-anchor-@10.252.28.14-8497 WARN session.SshSessionClient - Command [cmd.exe /c echo AbstractSessionClient verifying session] failed in session Ssh2SessionClient#709972056 SSH:/WindowsHostAuthcom.collation.platform.security.auth.WindowsHostAuth[ajcdom\srvadmin][XXXXX]/null@10.252.28.14: SessionClientException: CTJTP1125E An error occurred when creating the SSH2 Session to ajcdom\srvadmin@10.252.28.14: Exception: [SSH2FatalException: Permission denied; SSH2FatalException: Permission denied].
    2017-02-07 10:37:24,769 DiscoverManager [DiscoverWorker-0] 2017020710370751#AnchorSensor-anchor-@10.252.28.14-8497 DEBUG session.SshSessionClient - Spent 4.219 seconds in executeCommand
    2017-02-07 10:37:24,769 DiscoverManager [DiscoverWorker-0] 2017020710370751#AnchorSensor-anchor-@10.252.28.14-8497 DEBUG session.SshRetry - SSH exec for ajcdom\srvadmin@10.252.28.14: attempt 1/5:  [uid.iler7vyi] failed after 4.219 seconds: SessionClientException: CTJTP1125E An error occurred when creating the SSH2 Session to ajcdom\srvadmin@10.252.28.14: Exception: [SSH2FatalException: Permission denied; SSH2FatalException: Permission denied].
    2017-02-07 10:37:24,769 DiscoverManager [DiscoverWorker-0] 2017020710370751#AnchorSensor-anchor-@10.252.28.14-8497 DEBUG session.AbstractSessionClient - execute(cmd.exe /c echo AbstractSessionClient verifying session): failure: com.collation.platform.session.SessionClientException: CTJTP1125E An error occurred when creating the SSH2 Session to ajcdom\srvadmin@10.252.28.14: Exception: [SSH2FatalException: Permission denied; SSH2FatalException: Permission denied].
    ..
    ..
    2017-02-07 10:37:24,772 DiscoverManager [DiscoverWorker-0] 2017020710370751#AnchorSensor-anchor-@10.252.28.14-8497 DEBUG session.SshSession - @SSH: failure summary for com.collation.platform.session.SshSession$SshSessionValidator@6f2cd8b6:
        TRYING ajcdom\srvadmin[[ssh2,useKey=1]: SessionClientException: CTJTP1002E The following ssh2 key file is not found: C:\Users\ajcadmin.TADDMDR01\.ssh\id_dsa
        TRYING ajcdom\srvadmin[[ssh1,useKey=1]: SessionClientException: CTJTP1001E The following ssh1 key file is not found: C:\Users\ajcadmin.TADDMDR01\.ssh\identity
        TRYING ajcdom\srvadmin[[ssh2,useKey=0]: SessionClientException: CTJTP1125E An error occurred when creating the SSH2 Session to ajcdom\srvadmin@10.252.28.14: Exception: [SSH2FatalException: Permission denied; SSH2FatalException: Permission denied].
    ..
    ..
    com.collation.platform.session.SessionClientException: CTJTP1190E The server did not complete the authorization process.
        at com.collation.platform.session.SshSession$SshSessionValidator.getLastException(SshSession.java:378)
        at com.collation.platform.session.GatewaySession$GatewaySessionValidator.getLastException(GatewaySession.java:210)
        at com.collation.platform.security.auth.AbstractAuthContainer.validateAndCache(AbstractAuthContainer.java:145)
        at com.collation.platform.security.auth.AuthManager.validateAndCache(AuthManager.java:73)
        at com.collation.platform.session.GatewaySession.getUncachedSessionClient(GatewaySession.java:122)
        at com.collation.platform.session.AbstractSession.getSessionClient(AbstractSession.java:219)
        at com.collation.platform.session.AbstractSession.getSessionClient(AbstractSession.java:162)
        at com.collation.platform.session.SessionFactory.probeSession(SessionFactory.java:325)
        at com.collation.platform.session.SessionFactory.getNewSession(SessionFactory.java:455)
        at com.collation.platform.session.SessionFactory.getSession(SessionFactory.java:256)
        at com.collation.platform.session.SessionFactory.getSession(SessionFactory.java:137)
        at com.collation.discover.anchor.AnchorTunnel.makeTunnel(AnchorTunnel.java:744)
        at com.collation.discover.anchor.AnchorClient.makeTunnel(AnchorClient.java:1169)
        at com.collation.discover.anchor.AnchorClient.findTunnel2(AnchorClient.java:1144)
        at com.collation.discover.anchor.AnchorClient.findTunnel(AnchorClient.java:1133)
        at com.collation.discover.anchor.AnchorClient.connect(AnchorClient.java:746)
        at com.collation.discover.anchor.AnchorClient.<init>(AnchorClient.java:252)
        at com.collation.discover.anchor.RemoteAnchorClient.<init>(RemoteAnchorClient.java:82)
        at com.collation.discover.anchor.RemoteAnchorHandle.createAnchor(RemoteAnchorHandle.java:102)
        at com.collation.discover.agent.net.AnchorAgent.discover(AnchorAgent.java:102)
        at com.collation.discover.engine.AgentRunner.doRegularDiscovery(AgentRunner.java:323)
        at com.collation.discover.engine.AgentRunner.run(AgentRunner.java:247)
        at com.collation.discover.engine.DiscoverEngine.processWorkItem(DiscoverEngine.java:745)
        at com.collation.discover.engine.worker.DiscoverWorker.processWorkItemWithMetrics(DiscoverWorker.java:99)
        at com.collation.discover.engine.worker.DiscoverWorker.run(DiscoverWorker.java:168)
    2017-02-07 10:37:24,794 DiscoverManager [DiscoverWorker-0] 2017020710370751#AnchorSensor-anchor-@10.252.28.14-8497 DEBUG session.SessionFactory - getNewSession[gateway] ipSimple=10.252.28.14

     

    Thanks!

    Abhishek