The Big Ten Network was one of the first dedicated networks for one college conference. Now it is easier than ever to watch the Big Ten Network without the need to pay for traditional pay TV and get locked into a two-year contract. UMH160R supports to receive all kinds of digital television signal in the world. 4) Support program edition and AD insertion via SD/HD-SDI output. With ASI and IP interfaces for input and output, SMP180 can be integrated into. The BTN-2 Broadband Telecommunications Node performs lightwave to RF.
![]()
Applies to: Inventory
If you’re having problems scanning your devices, this article will guide you through common troubleshooting steps.
Symptoms
When trying to scan your network and discover devices some devices may appear in the inventory list with limited (or almost no) deviceinformation (like software, events, disk usage, etc.). This can happen even after multiple network scans, or after enteringvarious scan credentials on the Device Scanning settings page.
What is an unknown?
Understanding what an “unknown” is and why you should resolve it is an important part of getting the most out of Spiceworks Inventory.
Often a device shows up in Inventory as “unknown” when that device has no ports are open or the network scan has login/password issues with the device.
Why you should resolve your unknowns
It is important to resolve unknowns rather than to simply regroup the device. As long as the device is an unknown you will not see the device’s full details (like disk usage, software installed, etc.) and you will be unable to fully use all of the Spiceworks functionality. More unknown devices make your scans take longer to complete, too.
Viewing devices with scan errors
![]() Resolving specific error messagesResolving Windows Unknowns
Refer to this troubleshooting article.
Resolving Apple and Linux unknowns
Refer to this troubleshooting article.
Resolving SNMP unknowns
Refer to this troubleshooting article.
My unknown won’t resolve
If you’ve tried everything and the device is still unknown, you still have a few options:
Why does a device have a scan error, yet is correctly classified?
Sometimes you might see a device in the correct group, but when you try to access the device information, you see a scan error because Spiceworks cannot access the device during the network scans. This scan error generally appears when you have an ActiveDirectory environment or you are scanning with NMap enabled.
Documentation and Resources
Check the documentation and references below, and you can also email us at [email protected] to get more help!
Feedback form placeholder | Delete this region to remove feedback form from page.
If you cannot find the product you are looking for, please refer to. DisclaimerAxis Communications AB disclaims all warranties, whether express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, title and non-infringement, or any warranty arising out of any proposal, specification or sample with respect to the software. Axis and/or its licensor(s) shall not be liable for loss of data, loss of production, loss of profit, loss of use, loss of contracts or for any other consequential, economic or indirect loss whatsoever in respect of sale, purchase, use or disposition of the software.
![]() Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |