1 of 1 people found this helpful
The first article here will give you a good idea of how Discovery works, and what it needs. In your situation, there could be a router that does not pass ARP requests for example. Some additional stuff to get you going is there too.
Thanks. I'll check with out network provider.
Just an update. I have found that from the server, when I open the window for Network Domains, its blank. But with the Technician Client installed on my laptop, I am able to see and add the domain and OU's. Any ideas?
- Wouldn't it be better for someone to fill out all the options for Asset Discovery? So add the Network Domain, add the IP subnets, SNMP and the OUs? Or would this mean conflicting information?
- I've done a scan and found 4-5 devices that have the same MAC address. Weird thing is that the MAC Address in the table shows duplicates, but the computer preview displays the correct MAC.
- Does having multiple network connections screw up scans/audits? So example, we have users that go from wireless, to docking station (with ethernet) and maybe out of the office with a Forticlient VPN.
There may be a firewall or network protection of some kind between the server and the domain controller, is one possibility.
I wouldn't recommend using multiple scan criteria for Discovery that overlap the same machines. It could create problems with duplicate records, and at best it wouldn't really serve a purpose.
The duplicate Mac Addresses could be a result of using multiple scan criteria, but more likely is the router not passing arp requests that is discussed in the first link that I posted earlier, in my first reply.
Multiple connections will mess up scans/audits, but if you were to use Audit only (and no Discovery) there is a way to control what Track-It! looks for, or not, to determine matches when Auditing.
If you are mainly looking to Audit computers, we usually recommend not using Discovery, and running an Audit via login script instead. Discovery is okay, but it is limited to what your network will allow it to do - which is less and less as network security has become more stringent over the years.
See the Audit and Merge article that I posted in my first reply, and this one too: