Discovery > Discovery Modules > Network Infrastructure > Host Connection > Host Connection by Shell Job > Troubleshooting and Limitations – Host Connection by Shell Job

Troubleshooting and Limitations – Host Connection by Shell Job

Troubleshooting

  • Problem: When running the Host Connection by Shell job, the following error may be displayed:

    Error: Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed.

    Solution: This may be caused by one of the following NetBIOS protocol limitations:

    • The network share is considered to be in use even though it is not, that is, the session is frozen. In this case, try the following command:

    • net use * /delete
      
    • The network share is in use by another user whose user name is bound to the local machine user name. In this case, you can reconfigure the remote machine security policy, or wait for the other user to finish working.

  • Problem: If HPCmd Commands Execution Context is set to User, the Host Connection by Shell job fails NTCMD discovery if the user's account does not have the right to Log on as a service.

    Solution: The user's account must have the right to Log on as a service. For details how to configure users with the right to Log on as a service, see http://technet.microsoft.com/en-us/library/cc739424(v=ws.10).aspx

  • Problem: Access Denied Error Message

    The following error message may appear while trying to discover Windows 2008 SP2 destination by NTCMD protocol:

    Connecting to remote server failed with the following error message: Access is denied. For more information, see the about_Remote_Troubleshooting Help topic.

    This appears if the user attempting to discover the destination host is not a local Administrator user. (It does not matter if the user is a member of the Administrators group.)

    Solution: The solution requires additional configuration of the security policy.

    The LocalAccountTokenPolicy key should be changed to allow users from the Administrator group to connect remotely with Administrator privileges. Run the following command in PowerShell on the discovered host:

    Set-ItemProperty -Path HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\
    Policies\System -Name LocalAccountTokenFilterPolicy -Value 1 -Type DWord

    For details of this special case, see "HOW TO ENABLE REMOTING FOR ADMINISTRATORS IN OTHER DOMAINS" at http://technet.microsoft.com/en-us/library/dd347642.aspx.

Limitations

  • Limitation: If an interface has a MAC address of 0, the job does not report that interface or the IP address assigned to it.

  • Limitation: This discovery supports the reporting of PAE state only for Windows Operating systems.