Network Discovery Troubleshooting
This article provides a detailed guide to address common issues encountered during Network Discovery in the CYRISMA platform, with practical resolutions and best practices to ensure a successful scanning process.
- User Manual
- Agents
- The Cyber Risk Assessment Process
- API Documents
- General Questions and Troubleshooting
- The Cyber Risk Assessment Process (Video Tutorials)
- Sales and Prospecting Articles
- CYRISMA Partner Portal Access
- Glossary
- CYRISMA Change Log
- Support Ticket SLA
- Onboarding Framework
- PSA Integrations
- Billing Questions
- Self Onboarding Guide
Table of Contents
1. Common Network Discovery Issues
1.1. Network Discovery Results Are Empty
1.2. Devices Found but No Operating System Identified
1.3. Devices Cannot Be Added as Targets
1.4. Scan Results Show IP Addresses Instead of Hostnames
2. Proactive Troubleshooting Steps
2.1. Validate Scanning Agent Configuration
2.2. Use the Correct Service Account
2.3. Analyze Logs
2.4. Schedule Scans During Off-Peak Hours
3. Step-by-Step Network Discovery Process
Step 1: Navigate to Network Discovery
Step 2: Configure and Schedule the Scan
Step 3: Run the Scan
Step 4: View Results
Step 5: Merge Targets
4. Best Practices for Network Discovery
Credential Management
Agent Placement
Log Analysis
AV/Endpoint Protection Exclusions
DNS Configuration
1. Common Network Discovery Issues
1.1. Network Discovery Results Are Empty
Symptoms:
- No devices detected after running a scan.
Possible Causes:
- Agent placement issues.
- Incorrect IP range or subnet configuration.
- Firewall or IDS/IPS blocking traffic.
Resolutions:
-
Verify Agent Placement:
- Ensure the scanning agent resides within the same subnet as the target devices.
-
Check IP Ranges:
- Confirm the correct IP ranges or subnet are configured during the scan setup.
-
Inspect Network Restrictions:
- Work with the IT team to ensure firewalls or IDS/IPS are not blocking scan traffic.
-
Log Analysis:
- Check logs in
C:\Cyrisma_Agent
for error messages.
- Check logs in
1.2. Devices Found but No Operating System Identified
Symptoms:
- Discovered devices lack operating system details.
Possible Causes:
- Incorrect or insufficient credentials.
- Endpoint protection software blocking scanning activities.
Resolutions:
-
Validate Credentials:
- Test access using the following command:
net use \\[Target_IP]\C$ /user:[username] "[password]"
-
Update Service Credentials:
- Open the CYRISMA_Agent service on the scanning agent host.
- In the Log On tab, update the service account to one with admin rights for the subnet.
- Restart the service.
-
Whitelist Agent Activities:
- Add the following directories and executables to AV/endpoint protection exclusions:
C:\Cyrisma_Agent
C:\Cyrisma_Agent\App\PsExec.exe
C:\Cyrisma_Agent\Bin\PsCopy.exe
- Add the following directories and executables to AV/endpoint protection exclusions:
1.3. Devices Cannot Be Added as Targets
Symptoms:
- Devices appear in the discovery results but cannot be selected for merging (no checkboxes).
Possible Causes:
- Device types (e.g., IoT devices, printers) not supported for scanning.
- Mismatch in expected target configurations.
Resolutions:
-
Verify Device Eligibility:
- Only computers and supported devices can be added to the target list.
-
Review Device Configuration:
- Ensure devices are properly configured and accessible with provided credentials.
1.4. Scan Results Show IP Addresses Instead of Hostnames
Symptoms:
- Discovered devices are listed by IP addresses only.
Possible Causes:
- DNS issues in the network.
- Network restrictions preventing hostname resolution.
Resolutions:
-
Check DNS Configuration:
- Ensure proper DNS resolution is enabled and functional in the network.
-
Validate Hostname Access:
- Use commands like
ping
ornslookup
to confirm hostname resolution.
- Use commands like
2. Proactive Troubleshooting Steps
2.1. Validate Scanning Agent Configuration
- Navigate to Admin > Scan Agents.
- Update credentials and validate the agent.
2.2. Use the Correct Service Account
- If the scanning agent runs as "system," it may lack network access rights.
- Update the CYRISMA_Agent service to use a network account with local admin rights.
2.3. Analyze Logs
- Review logs in
C:\Cyrisma_Agent
for error messages.
2.4. Schedule Scans During Off-Peak Hours
- Schedule scans during non-peak times to minimize server congestion and delays.
3. Step-by-Step Network Discovery Process
Step 1: Navigate to Network Discovery
- Go to Admin > Targets > Network Discovery.
Step 2: Configure and Schedule the Scan
- Provide administrative credentials during setup.
- Use the "Alternate Credentials" option if necessary.
Step 3: Run the Scan
- Ensure the agent is active and within the target subnet.
Step 4: View Results
- After the scan completes, click the scan row to view detailed results.
Step 5: Merge Targets
- Select devices to add by checking the boxes and clicking the Merge button.
4. Best Practices for Network Discovery
Credential Management
- Use valid administrative credentials and test them prior to scanning.
Agent Placement
- Ensure scanning agents are within the same subnet as the targets for optimal results.
Log Analysis
- Regularly review logs to identify and address issues promptly.
AV/Endpoint Protection Exclusions
- Add CYRISMA directories and executables to antivirus or endpoint protection exclusion lists to avoid false positives.
DNS Configuration
- Ensure proper DNS resolution to facilitate seamless device identification.