Jump to content

Support

Administrators
  • Posts

    695
  • Joined

  • Last visited

Posts posted by Support

  1. Karel,

     

    What about the Classic engine in build 1490?

     

    What we changed between 1483 and 1490 is that the ARP ping is not used for monitoring of the online state anymore. In 1483 it's still used. However it gives incorrect results on Windows XP (when an asset goes offline, it still shows as online for about 10 minutes, as its MAC is still present in the ARP table), and also if there is Proxy ARP enabled on a switch or router.

     

    Are all your PCs on static or dynamic IP addressing? (static IPs have a padlock icon next to the IP address in the tree, and dynamic IPs don't have it).

  2. Hi,

     

    I have a suggestion for Wake-on-LAN:

     

    The suggested version in the blog entry uses only a mac address for the wol command. This works only on the same Layer 2 segment (within a IP subnet).

     

    A good enhancement would be, if you could use a WOL-command that does support sending packet over L3 with a IP-network broadcast address. (You need to calculate the Broadcast IP for the subnet and have it as variable i.e. %PC-Subnetbroadcast%)

     

    Hi Karel,

    This was a planned enhancement for the standard WOL action, but adding a possibility to pass a remote broadcast address in custom actions is a nice feature too, thanks.

     

     

    Marius,

    Thank you for updating this topic with new useful actions.

  3. I'm not sure what are you trying to do here. Allow this regular account to run only specified programs (with specified full paths) or what? If so, this will fail, because tnilinagent is always uploaded to a randomly named directory in the home directory of a user, and then also unpacked to another random temp directory, so the path where it's run from is never known beforehand.
    You can always run the scan manually, if needed:

    chmod 755 tnilinagent_x64
    ./tnilinagent_x64 -silent

    I'm not a master of setting up the sudoers file, but from what I know, you only need to specify the user in it to allow him to elevate to root. If you have further restrictions, that may not work: you should consult with your Unix admins.

  4. The problem is not in the support of child domains, there is no need to support them specifically. The problem is in access rights. If you can access a computer's "admin$" shared resource, you will be able to scan it (via SMB protocol; RPC protocol is more tedious to set up properly). If you are using a user that is domain admin in your parent domain, make sure that it's an admin in the child domain too and that it's a member of the Local Admins ground on the computers from that domain. If you are using a user from a child domain, make sure to specify the user name in full format (DOMAINNAME\Username) to avoid any ambiguity.

  5. Please disable one of the options:

     

    Options - Scanner - Use Nmap engine

    Options - General - Check the online status of assets periodically

     

    and see if it helps.

    Then please enable it back and disable another option of these two. See if it helps also or not. Please let us know which of them (or both) helps.

  6. Yes, it's possible. Actually, this error message is quite specific and it would better be sent to our support email rather than the forums, but... As we are already here, this is the original error message:

     

    >>> etc\sudoers: syntax error near line 26
    sudo: parse error in \etc\sudoers near line 26
    sudo: no valid sudoers sources found, quitting

     

    The problem is that you have syntax error in your "\etc\sudoers" file. Your admins should fix this file. The non-root user that you use should be specified in sudoers correctly to be able to run the scan, and the file should not contain errors.

     

    The error that the program itself throws:

     

    Cannot create file "C:\Users.....". The filename, directory name, or volume label syntax is incorrect

     
    is secondary and appears because the program receives the filename for saving the scan results after the ">>>" sequence which appears in the sudo error. So as soon as the sudoers file is fixed, you should be running fine.
×
×
  • Create New...