crecode.com

Using the IP Query function in Software Access barcode code39 in Software Using the IP Query function




How to generate, print barcode using .NET, Java sdk library control with example project source code free download:
5. using software todeploy code 3 of 9 with asp.net web,windows application .NET CF Using the IP Query function Assuming we have installed t he OCS-NG server on a Linux distribution, we might also have the third option of the Security menu. This tool scans a manually specified host for a rather exhaustive list of details. It can also find out if the host was inventoried and/or just discovered.

It determines the operating system (if available), DNS, and NetBIOS name. The web interface of IP Query is basically a frontend to the IPDISCOVER-UTIL Perl script. That is why it is only available on Linux machines due to the Perl interpreter.

Of course, there are workarounds for this too. It is based on the world-class security scanner and notorious penetration testing/security auditing tool, nmap. You can find more information about nmap from the following link:.

http://nmap.org/. Alright, so we know that the heart of the IP Query function is nmap, but it has a few other requisite components as well, which are as follows: nmblookup (part of the samba suite, tested on 3.0.7/3.

0.10) Perl module Net::IP Perl module DBI Perl module DBD::mysql Perl module XML::Simple. We need to specify the IP ad Code39 for None dress and mask to carry out the scan. The output is shown in the next screenshot:. [ 133 ]. Investigating the Process of Gathering Inventory Data A final warning regarding ip discover-util.pl (Perl script); it requires write access (permissions) to the root directory. This warning message might appear in red.

If we are running it on the Linux/Unix platform and we still cannot see the IP Query option from the Security pane, then write access permissions might be the cause for this warning message. Let"s set the appropriate directory permissions by using the following commands:. #chown -R 775 /var/www/html/ocsreports #chown -R 775 /var/www/html/ipd Let"s check out the results of running the previous commands:. #ls -l drwxrwxr-x 2 root Code-39 for None apache 4096 Oct 30 16:51 ipd drwxrwxr-x 9 root apache 4096 Jan 26 14:07 ocsreports. Once the permissions are set , this warning message will disappear when looking at hosts that are not inventoried, and the IP Query option will also appear under the Security pane. We can also verify the configured parameter under the Config . Interface tab. Look for the 39 barcode for None IPDISCOVER_IPD_DIR folder. This stands for the IpDiscover folder.

As expected, it should point to the location where we actually have the IPD located. The beauty of the IP Query function is that once it is working fine, it also adds a little Analyze function next to uninventoried hosts. This way, we can scan one of those hosts by clicking on it, instead of noting its network address and running a manual IP Query.

. [ 134 ]. 5 . Summary. Throughout this chapter, we Software Code 3/9 focused on the mechanism that fuels the OCS-NG inventory. We learned what separates the uninventoried hosts from inventoried ones, and how to track as well as analyze these. We elaborated on the IpDiscover process by explaining the elevation mechanism as well.

Now, we know how some of the hosts become IpDiscover activated. As there are no two identical infrastructures, we might be required to tweak those server-side variables that alter the behavior of IpDiscover. Thankfully, those parameters make sense and are clearly documented.

In order to keep our inventory organized, we might want to define network types and name our subnets. These custom names and Uids can then be used to categorize the queries" results. Finally, we have seen how the IP Query function works on Linux platforms that have the OCS-NG central management servers enabled.

It"s a useful Perl script based on nmap and other tools. The web interface makes a really straightforward interface. The next chapter covers the nuts and bolts of package deployment and remote execution.

In the next chapter, we will see how to get the most out of our OCS-NG inventory, how to create and deploy packages, customize this process, add another layer of security by involving certificates, and finally, how to monitor and troubleshoot the process (if required).. [ 135 ].
Copyright © crecode.com . All rights reserved.