7 Ways ServiceTonic Network Discovery Tool Improves IT Asset Visibility

ServiceTonic Network Discovery Tool — Complete Setup & First Scan Guide

Prerequisites

• Windows machine (Windows 7/8/10/11 supported).
• Java Runtime Environment installed.
• Administrative access to the machine for installing services and opening ports.
• Credentials for any Windows devices you want deep-scanned (optional for basic ping/ARP).
• Port number available for the tool’s web UI (default chosen during install).

Installation (wizard)

1. Download the installer (ServiceTonic Network Discovery Tool Installer.exe).
2. Run installer as Administrator.
3. Accept license, choose ⁄₆₄-bit, set installation path.
4. Select port for the web UI, create an admin username and password.
5. Finish install; the tool runs as a service and exposes a web UI on http://127.0.0.1: (or the host IP).

Initial configuration

1. Open browser to http://127.0.0.1: and log in with admin credentials.
2. Review Quick Guide / First Steps PDF from the login screen.
3. Install any recommended Java updates if prompted.
4. (Optional) Configure service to start automatically and verify firewall allows the selected port.

Create a scan job (first scan)

1. From the UI, go to “Create New Scan” / “New Discovery”.
2. Add a description (e.g., “Initial LAN Discovery”).
3. Enter target IP range(s) or subnet(s) (CIDR or start–end).
4. Provide Windows credentials if you want agentless Windows inventory (username, password, domain).
5. Choose discovery depth:
   • Basic: ping/ARP to list devices (low impact).
   • Full: SNMP/WMI/SMB/port scan for detailed inventory (higher impact).
6. Configure scan options: timeout, parallel threads/workers, SNMP community strings (if applicable).
7. Save and start the scan.

What the first scan will produce

• Inventory list of discovered devices: hosts, printers, switches, routers, monitors.
• Per-device details: IP, MAC, hostname, vendor, basic open ports.
• Graphical network map showing device relationships (if enabled).
• Logs and a summary report with counts by device type and any failures.

Post-scan tasks

1. Review the discovery results table and open individual device details for verification.
2. Export results if needed (note: some export features may be limited in unregistered/demo builds).
3. Create or map discovered devices into your CMDB (if integration available).
4. Add credentials or SNMP community strings for devices that were only partially discovered; re-run targeted scans for more detail.
5. Schedule regular scans (daily or weekly) and configure notifications for new devices or critical changes.

Troubleshooting — quick checks

• No devices found: verify scan IP range, ensure tool has network access and correct subnet, check firewall rules, confirm target devices respond to ICMP.
• Partial data for Windows hosts: ensure provided Windows credentials are correct and account has remote query rights; enable WMI/Remote Registry if needed.
• SNMP devices not detailed: confirm SNMP version and community string (v1/v2) or user/password/auth/encrypt settings (v3).
• High CPU/network load during deep scans: reduce NMAP workers or switch to a lower discovery depth.

Best practices

• Start with a low-impact ping/ARP scan to establish baseline, then escalate to full scans for targeted segments.
• Use credentials (WMI/SMB/SNMP) where possible for richer inventory.
• Throttle or schedule deep scans during off-peak hours.
• Maintain and secure the tool’s admin account and web UI port.
• Regularly update Java and the discovery tool to the latest version.

If you want, I can produce a concise checklist or a sample scan configuration (IP ranges, timeouts, thread counts) tailored to a small (≤200 hosts) or large (>2000 hosts) network.