================================================================================
ARYNOX NETSCOPE - README, HELP & INFORMATION
================================================================================

Product Name: Arynox NetScope
Current Version: v12.2.0
Developer / Owner: Arynox | IT Services
Website: https://arynox.com
Official Download Repository: https://arynox.com/App_Repository/Arynox-NetScope/
Copyright: Copyright (c) 2026 Arynox | IT Services. All rights reserved.
Last Updated Release: 10/05/2026

================================================================================
1. WHAT IS ARYNOX NETSCOPE?
================================================================================

Arynox NetScope is a standalone Windows desktop application for network visibility,
diagnostics, packet capture, PCAP review, traffic analysis, device discovery,
HTTP/API testing, DNS troubleshooting, network tools, reporting, extension-based
enhancements, and Remote Agent monitoring.

It is designed for IT engineers, infrastructure teams, support teams, developers,
network administrators, and technical users who need practical answers quickly.
The app brings many common troubleshooting tools into one interface so users do
not need to jump between many different Windows commands, websites, and external
applications while under pressure.

Arynox NetScope is not a cloud service. It is built primarily as a local Windows
application. Normal standalone operation does not require a user account, browser
extension, mobile app, or cloud login.

Some optional features may make network requests only when enabled or started by
the user. Examples include update checks, online manufacturer lookup, Geo /
Reputation lookups, HTTP/API tests, DNS tools, WHOIS lookups, Speed Test, and
Remote Agent communication.

================================================================================
2. VERSION 12.2.0 - LATEST CHANGES
================================================================================

Version 12.2.0 aligns the main app, Agent, Agent Setup, Help files, version file,
release notes, built-in plugin labels, and in-app Help & Info page.

Main version and release changes:

- Main app version updated to v12.2.0.
- Arynox NetScope Agent version updated to v12.2.0.
- Arynox NetScope Agent Setup version updated to v12.2.0.
- version.json updated to v12.2.0.
- release-notes.html updated to describe the current release.
- Help and README content updated to match the current feature set.
- Built-in plugin/module version labels updated to v12.2.0.

PCAP and Save / Replay improvements:

- PCAP loading performance improved using asynchronous loading and virtualized
  DataGrid behaviour.
- Large PCAP files are handled more safely so the UI remains more responsive.
- PCAP Viewer keeps common Wireshark-style workflows inside the app.
- Save / Replay PCAP actions are clearer and connected to the built-in PCAP
  Viewer.
- Cell copy behaviour was corrected so copying a selected cell copies only the
  selected value, not the header name on a separate line.
- Multi-cell copy remains supported with tab/newline-separated output.

Capture Profile improvements:

- Capture Profile apply behaviour was fixed.
- Selecting a profile from the table or dropdown now applies the intended profile.
- Profile selection now updates the active filter/search fields consistently.
- Applying a profile refreshes the affected packet/live views immediately.

Traffic Visuals and Connection Map improvements:

- Traffic Visuals now show real Source IP -> Destination IP conversations.
- Connection Map details were corrected to avoid calling a public IP "Local".
- Connection Map details now use clearer fields such as Source, Destination,
  Direction, Protocol, Port, Packets, Bytes, Weight, Risk, and Last Seen.
- Direction is calculated more clearly as Inbound, Outbound, Internal, or External.

Network Scanner and device identification improvements:

- Added an internal manufacturer/OUI database stored under the NetScope AppData
  area.
- NetScope checks the local manufacturer database first before going online.
- If no local match exists and online lookup is enabled, NetScope checks online
  manufacturer/OUI sources and saves the result locally.
- Online manufacturer lookup is enabled by default in Settings.
- Only the OUI/MAC prefix should be used for online manufacturer lookup, not full
  packet data or PCAP files.
- Added Verify / Refresh Manufacturer Database action in Settings.
- Added Clear Manufacturer Cache action in Settings.
- Added stronger multi-source manufacturer lookup behaviour.
- Added Device Type / Fingerprint logic so the scanner no longer labels
  everything simply as "Device".
- Added detection for printers, HP printers/MFPs, NAS/storage, routers, Windows
  devices, Linux/server appliances, cameras/NVR/IoT devices, Apple devices,
  mobile/media/smart-home devices, UPS/power devices, and web-managed devices.
- Added stronger printer detection using service hints such as 9100 Raw Printer,
  631 IPP, 515 LPD, 5357 WSDAPI, printer hostnames, web titles, and manufacturer
  hints.
- Added Confidence, Vendor Source, and Evidence fields to make scanner results
  explainable instead of silent guesses.
- CSV export now includes the improved scanner fields.

Network Tools improvements:

- Ping, NSLookup, Port Scanner, Speed Test, Trace Route, WHOIS Lookup, Reverse
  DNS, SSL Inspector, and HTTP/API Tester now run independently.
- A long Trace Route or WHOIS Lookup should not block Ping, NSLookup, Port
  Scanner, Reverse DNS, Speed Test, SSL Inspector, or HTTP/API Tester.
- Each supported tool has its own async runner and cancellation state.
- The Stop action stops the currently selected tool instead of stopping every
  other tool.

Help & Info improvements:

- Help & Info was upgraded into an in-app searchable Help Center.
- Users can search directly inside the app instead of opening external documents.
- Quick buttons are available for common topics such as Capture, PCAP, Network
  Tools, Scanner, Traffic Visuals, Capture Profiles, Remote Agent, Exports,
  Privacy, and Troubleshooting.
- Help quick buttons now filter to the intended section consistently.
- Save / Replay and Privacy quick buttons were corrected so they behave like the
  other section buttons.
- The Help Center is designed for engineers who need answers within seconds.

================================================================================
3. IMPORTANT PRIVACY INFORMATION
================================================================================

Arynox NetScope is designed as a standalone application.

The application is not designed to collect, sell, upload, or transmit user data to
Arynox or any third party during normal standalone use.

Network checks and diagnostic operations are performed locally on the user's
machine, except when the user intentionally starts a feature that must communicate
with a target system, update endpoint, lookup provider, or remote Agent.

Examples:

- HTTP/API Tester sends requests to the URL entered by the user.
- Ping, NSLookup, Trace Route, WHOIS, Reverse DNS, SSL Inspector, Speed Test, and
  Port Scanner may communicate with the selected target or required network
  infrastructure.
- Geo/Reputation lookups may check information about public IP addresses.
- Remote Agent features communicate with the paired remote Agent machine.
- Update checking may request the public version file from arynox.com.
- Online manufacturer lookup may send an OUI/MAC prefix to an external lookup
  source if the local manufacturer database does not already contain the prefix
  and the setting is enabled.

Online manufacturer lookup privacy rule:

NetScope should use only the manufacturer prefix/OUI for lookup. It must not send
packet contents, PCAP files, scan result tables, usernames, passwords, API keys,
HTTP/API tester content, or captured traffic to a manufacturer lookup source.

Basic app-open usage count:

If enabled in Settings, NetScope may send a minimal app-open event to the Arynox
Stats endpoint so Arynox can understand app usage. This event should be limited to
product name, event type, app version, release date, anonymous install ID, and UTC
timestamp. The website/server may also see the public IP address, country where
available, user agent, and request time.

The app-open usage count must not send packet data, PCAP files, scan results,
remote reports, usernames, passwords, API keys, admin credentials, captured
traffic, device names, MAC addresses, or HTTP/API tester content.

================================================================================
4. LEGAL AND RESPONSIBLE USE
================================================================================

Arynox NetScope is intended for legitimate network diagnostics, IT administration,
troubleshooting, learning, support, and security-aware monitoring.

Users must only use the application on networks, systems, devices, services, and
API endpoints that they own, manage, or have permission to test.

Network scanning, port scanning, packet capture, Remote Agent use, and HTTP/API
testing may be sensitive activities in corporate environments. Use them only when
authorised and follow company policy, local law, EU privacy requirements, and all
relevant acceptable-use rules.

Do not use Arynox NetScope to inspect, scan, test, monitor, capture, or interfere
with systems without permission.

================================================================================
5. WINDOWS REQUIREMENTS
================================================================================

Recommended operating system:

- Windows 10 64-bit
- Windows 11 64-bit
- Windows Server editions may be used for the Remote Agent service where supported

Recommended environment:

- Standard Windows desktop environment for the main NetScope Console
- Internet connection for external API, DNS, website, SSL, update, online lookup,
  WHOIS, Speed Test, and Geo/Reputation features
- Administrator rights may be required for Npcap installation, Remote Agent setup,
  URL reservation, firewall rule creation, Windows service installation, and some
  packet capture operations

================================================================================
6. PACKAGE COMPONENTS
================================================================================

Arynox NetScope may be distributed as separate packages:

1. ArynoxNetScope.zip
   Main desktop application / console.

2. ArynoxNetScopeAgentSetup.zip
   Remote Agent setup package used to install/uninstall the Agent service on
   another machine or server.

3. Optional extension packages
   Safe local extension packages containing extension manifests and supported
   actions.

4. Optional Npcap installer
   Packet capture driver installer, if redistribution rights allow it to be
   included with the app package.

================================================================================
7. NPCAP REQUIREMENT FOR LIVE PACKET CAPTURE
================================================================================

Some NetScope features work without any additional driver. Advanced live packet
capture normally requires Npcap on Windows.

Npcap is the packet capture driver commonly used by tools such as Wireshark. It
allows applications to access low-level network packet information from the
network adapter.

Features that may require Npcap:

- Live packet capture
- Adapter packet monitoring
- Wireshark-style packet visibility
- Loopback capture for 127.0.0.1 traffic, if Npcap loopback support is installed
- Remote packet capture on Agent machines
- Any advanced feature that depends on raw packet capture

Features that can still be used without Npcap:

- HTTP / API Tester
- DNS tools
- Ping-style checks
- Trace Route-style checks
- Port testing
- SSL checks
- WHOIS Lookup and Reverse DNS
- Network Scanner functions that use normal Windows networking
- Remote Agent inventory management where packet capture is not required
- Reports and export features that do not require live capture
- Settings, Help & Info, and Extensions

================================================================================
8. UPDATE CHECKS
================================================================================

Arynox NetScope can check the public version file at:

https://arynox.com/App_Repository/Arynox-NetScope/version.json

Official main app download:

https://arynox.com/App_Repository/Arynox-NetScope/ArynoxNetScope.zip

This update check does not send packet data, capture data, reports, adapter data,
PCAP files, usernames, passwords, HTTP/API tester content, or network content to
Arynox. It is a simple request to a public version file.

================================================================================
9. MAIN APPLICATION AREAS
================================================================================

The exact menu names may vary slightly by build, but Arynox NetScope may include:

- Dashboard / Overview
- Network Adapters
- Network Scanner
- Packets
- PCAP Viewer
- DNS Analyzer
- Sessions
- Traffic Visuals
- Smart Issue Detection
- Geo / Reputation
- Real-time Alerts
- Capture Profiles
- Network Tools
- Save / Replay
- Reports
- Extensions
- Remote Agents
- Export
- Settings
- Help & Info

================================================================================
10. NETWORK SCANNER
================================================================================

The Network Scanner discovers devices on authorised local networks and presents
results in a structured, exportable table.

Typical result fields may include:

- IP Address
- Hostname / Device Name
- MAC Address
- Manufacturer / Vendor
- Vendor Source
- Device Type
- Confidence
- Status
- Response Time
- Open Services
- HTTP / Web Title
- OS / Platform Hint
- Evidence
- First Seen
- Last Seen
- Notes

Manufacturer lookup behaviour:

1. NetScope extracts the OUI/MAC prefix if a MAC address is available.
2. NetScope checks the local manufacturer database first.
3. If no local match exists and online lookup is enabled, NetScope checks online
   lookup sources.
4. When a manufacturer is found online, NetScope saves it to the local database.
5. Future scans can use the cached local result first.

Local manufacturer database path:

%AppData%\Arynox\NetScope\device-identity-db.json

Settings:

- Enable online manufacturer lookup when local DB has no match
- Verify / Refresh Manufacturer Database
- Clear Manufacturer Cache

Device Type / Fingerprint logic:

NetScope uses ports, hostnames, manufacturer names, service labels, web titles,
and other hints to identify the device type. It may classify devices as:

- HP printer / MFP
- Printer / print server
- NAS / storage
- Network device
- Router / DNS appliance
- Camera / NVR / IoT
- Windows computer/server
- Windows / SMB device
- Linux/server or appliance
- Apple device
- Mobile / Android device
- Media / smart-home device
- UPS / power device
- Web-managed device
- Known vendor device
- Unknown device

Printer detection examples:

- 9100 Raw Printer / JetDirect
- 631 IPP Printer
- 515 LPD Printer
- 5357 WSDAPI
- Hostname containing HP, LaserJet, OfficeJet, DeskJet, PageWide, MFP, Brother,
  Canon, Epson, Xerox, Lexmark, Kyocera, Ricoh, Zebra, or similar
- Web title containing printer management or embedded web server hints

Evidence examples:

- Confidence=High; Vendor=HP Inc.; VendorSource=Online lookup / cached; Services=80 HTTP, 443 HTTPS, 9100 Raw Printer; WebTitle=HP Embedded Web Server
- Confidence=Medium; Vendor=Synology; Services=445 SMB, 5000 Synology DSM; DeviceType=NAS / storage

Important:

Network scanning can create network traffic and may trigger security monitoring or
firewall alerts. Use the scanner only on authorised networks. Keep deep checks and
large ranges under control in corporate environments.

================================================================================
11. NETWORK TOOLS
================================================================================

Network Tools provide common troubleshooting actions from one place.

Supported tools may include:

- Ping
- NSLookup
- Port Scanner
- Speed Test
- Trace Route
- WHOIS Lookup
- Reverse DNS
- SSL Inspector
- HTTP / API Tester

Current behaviour:

Each tool is designed to run independently. A long-running Trace Route, WHOIS
Lookup, Port Scanner, or Speed Test should not block the other tools from running.
Each supported tool has its own async runner and cancellation state.

Stop behaviour:

- Stop affects the currently selected/running tool.
- Other tools can continue running.
- The selected tool's Run button may be disabled while that specific tool is busy.
- Switching to another tool should allow that tool to run independently.

================================================================================
12. HTTP / API TESTER
================================================================================

The HTTP / API Tester is used to test web pages, APIs, services, and endpoints.

Typical API tester fields:

- URL
- HTTP method
- Request headers
- Request body / JSON payload
- Send button
- Stop button
- Clear results button
- Response output

Example GET request:

URL:
https://qr.arynox.com/api/v1/account

Method:
GET

Request Headers:
Authorization: Bearer YOUR_API_KEY
Accept: application/json

Request Body:
Leave empty

Example POST request:

URL:
https://qr.arynox.com/api/v1/qrs/create

Method:
POST

Request Headers:
Authorization: Bearer YOUR_API_KEY
Accept: application/json
Content-Type: application/json

Request Body:
{
  "name": "NetScope API Test QR",
  "content_type": "url",
  "qr_type": "static",
  "url": "https://arynox.com"
}

Important:

- Headers go in the Request Headers box.
- JSON or form payload goes in the Request Body box.
- Do not put headers inside the body box.
- For GET requests, the body is usually empty.
- For POST, PUT, and PATCH requests, the body is commonly used.

================================================================================
13. PCAP VIEWER
================================================================================

The PCAP Viewer opens and reviews Wireshark-compatible .pcap capture files inside
NetScope. It provides practical packet review without forcing users to leave the
application for common troubleshooting tasks.

Typical PCAP Viewer actions:

- Open an existing .pcap file
- Open the latest local capture
- Open a saved capture from Save / Replay
- Save the currently loaded PCAP as another file
- Open the capture in external Wireshark if installed
- Review packets in a structured packet list
- Click a packet to view decoded protocol details
- Review raw packet bytes in hex and ASCII format
- Apply quick filters, built-in saved filters, or custom filters

The packet list may include:

- No.
- Time
- Source
- Destination
- Protocol
- Length
- Info

Performance notes:

Large PCAP files can contain many thousands or millions of packets. NetScope uses
asynchronous loading and virtualized grids to keep the UI more responsive. For very
deep protocol analysis, Wireshark remains the specialist external tool.

Copy behaviour:

- Selecting one cell and pressing Ctrl+C copies only that cell value.
- Headers should not be copied when the user selected only a cell.
- Multi-cell copy remains supported.
- Full row copy is available where supported.

================================================================================
14. PCAP VIEWER FILTERS
================================================================================

PCAP Viewer filters are display filters. They do not modify the PCAP file. They
only control which rows are shown in the packet list.

Supported practical examples:

tcp
udp
arp
dns
http
tls
not arp
not dns
ip.addr == 192.168.0.20
ip.src == 192.168.0.20
ip.dst == 8.8.8.8
port == 443
tcp.port == 443
udp.port == 53
tcp and ip.addr == 192.168.0.20
not arp and not dns
tcp or udp

NetScope PCAP filters are practical NetScope display filters, not full Wireshark
display filters. The supported syntax focuses on common troubleshooting use cases
and may be expanded over time.

================================================================================
15. CAPTURE PROFILES
================================================================================

Capture Profiles are saved monitoring presets. A profile should change the focus
of the live capture view and related analysis, not only rename something visually.

Examples:

General Monitor:
Balanced monitoring for normal network visibility.

DNS Issues:
Focuses on DNS traffic and DNS-related issues.
Typical filter:
protocol: DNS OR port: 53

Debug Website/API:
Focuses on web/API traffic.
Typical filter:
protocol: HTTP OR protocol: TLS OR protocol: DNS OR port: 80 OR port: 443

Security Watch:
Focuses on common high-risk/admin ports.
Typical filter:
port: 3389, 445, 22, 1433, 3306

Expected behaviour when applying a profile:

- Set active profile name
- Apply packet/live view filter
- Update visible capture focus
- Refresh filtered views immediately
- Enable relevant Smart Issue Detection behaviour where supported
- Keep collecting real traffic internally where supported
- Make it clear to the user which profile is active

================================================================================
16. TRAFFIC VISUALS AND CONNECTION MAP
================================================================================

Traffic Visuals provide a cleaner view of connection activity and traffic-related
events.

Current connection display rules:

- Traffic Visuals should show Source IP -> Destination IP.
- Connection Map details should use Source and Destination, not confusing Local /
  Remote labels where public IPs may appear in the wrong column.
- Direction should explain the traffic relationship.

Direction examples:

- Private IP -> Public IP = Outbound
- Public IP -> Private IP = Inbound
- Private IP -> Private IP = Internal
- Public IP -> Public IP = External

Connection Map details may include:

- Source
- Destination
- Direction
- Protocol
- Port
- Packets
- Bytes
- Weight
- Risk
- Last Seen

================================================================================
17. DNS TOOLS AND DNS ANALYZER
================================================================================

DNS tools help test name resolution. They can be used to check whether a domain
name resolves correctly and to troubleshoot cases where a website or service
cannot be reached by name.

Example targets:

- arynox.com
- qr.arynox.com
- google.com
- cloudflare.com

The DNS Analyzer page focuses on DNS-related capture and diagnostic information.
When the DNS Issues capture profile is applied, NetScope can focus the live view
on DNS traffic such as protocol DNS and port 53.

================================================================================
18. SSL / CERTIFICATE CHECKS
================================================================================

The SSL Inspector is used to inspect HTTPS/TLS services and certificate details.
It may show:

- Target host and port
- TLS protocol version where available
- Cipher suite information where available
- Handshake result
- Certificate validation result
- Certificate chain status
- Expiry warnings
- Issuer and subject distinguished names
- Common Name, Organization, Organizational Unit, Country, Locality, State
- SAN, Basic Constraints, Key Usage, Extended Key Usage
- AKI, SKI, CRL Distribution Points, AIA, OCSP, CA Issuers URL
- Certificate policies and custom extensions where present
- SHA-1 and SHA-256 fingerprints
- PEM certificate output and raw detailed view

Some fields may be unavailable if the remote server does not present them or if
they are not exposed by the underlying Windows/.NET platform.

================================================================================
19. SAVE / REPLAY
================================================================================

Save / Replay allows users to keep useful packet captures for later review,
documentation, sharing, or troubleshooting follow-up.

Current workflow focuses on Wireshark-compatible PCAP files. Users can:

- Save the current local capture as a PCAP file
- Load a selected PCAP for review
- Open an external PCAP file
- Open a selected saved PCAP directly in the built-in PCAP Viewer
- Save the selected PCAP as another file
- Keep packet evidence for escalation or network engineering review
- Open PCAP files in Wireshark when deeper external analysis is needed

Saved captures should be selectable in a clear way. Where a radio selection is
shown, clicking inside the radio cell should make selection easy and fast.

================================================================================
20. REPORTS AND EXPORT
================================================================================

Reports and export features help document findings, share results with a team, or
keep a technical troubleshooting record.

Export options may include:

- JSON snapshots
- CSV snapshots
- Network Scanner CSV exports
- Remote Capture CSV exports
- Wireshark-compatible PCAP exports

Avoid exporting or sharing sensitive information unless authorised. PCAP files may
contain sensitive network metadata and sometimes payload data depending on the
traffic captured.

================================================================================
21. REMOTE AGENTS
================================================================================

Remote Agents allow the main NetScope Console to communicate with approved remote
machines where the Arynox NetScope Agent service is installed.

Architecture:

Arynox NetScope Console
Main desktop app used by the administrator/operator.

Arynox NetScope Agent
Separate background service installed on a remote Windows machine/server.

Agent version:
v12.2.0

Agent Setup version:
v12.2.0

Default port:
9443

Health check:
http://localhost:9443/health

Remote Capture requirements:

- Remote machine has Arynox NetScope Agent installed and paired
- Agent version should match the main app version
- Npcap must be installed on the remote machine for packet-level capture
- Correct remote adapter must be selected
- Firewall and Agent port access must allow console-to-Agent communication

Remote Capture data rules:

- Show real packet-level rows only
- Do not mix synthetic adapter-counter rows into packet results
- CSV exports should contain the real captured rows available in the Remote
  Capture Live table
- Remote PCAP downloads should contain the raw packet data recorded by the Agent

================================================================================
22. EXTENSIONS
================================================================================

Extensions allow NetScope to be expanded with safe, local, manifest-based modules.

Supported manifest names may include:

extension.json
plugin.json
*.netscopeext

Safe extension actions may include:

- Add alert rules
- Add capture profiles
- Run supported safe actions
- Open trusted URLs
- Provide traffic summary actions
- Add helpful metadata and documentation

Extensions should not silently execute arbitrary code, bypass security controls,
or perform hidden monitoring.

================================================================================
23. SETTINGS
================================================================================

The Settings page can include:

- Theme selection
- Behaviour options
- Capture-related settings
- Display preferences
- Tool behaviour
- Network adapter refresh interval
- Update checking preferences
- Basic app-open usage count setting
- Device identification / manufacturer lookup settings

Device identification settings:

- Enable online manufacturer lookup when local DB has no match
- Verify / Refresh Manufacturer Database
- Clear Manufacturer Cache

Network adapter refresh:

NetScope can refresh local adapter information while the app is open. This helps
when a laptop moves between networks, DHCP changes the IP address, VPN adapters
connect/disconnect, or Wi-Fi/Ethernet status changes.

================================================================================
24. HELP & INFO
================================================================================

The Help & Info page is now a searchable in-app Help Center.

It should help users answer operational questions quickly without opening external
documentation. This is especially important for engineers and support teams under
pressure.

Help Center features:

- Search box
- Clear search button
- Quick section buttons
- Capture troubleshooting
- Network Tools guidance
- DNS troubleshooting workflow
- Network Scanner/device identification help
- Traffic Visuals and Sessions explanation
- Capture Profiles help
- Save / Replay and PCAP help
- Remote Agent checklist
- Export/report/copy guidance
- Privacy/settings explanation
- Common problems and fast fixes
- Responsible-use section
- Version and ownership section

Quick buttons should filter to their intended section consistently.

================================================================================
25. TROUBLESHOOTING
================================================================================

PROBLEM: The app opens, but packet capture does not work.

Possible cause:
Npcap is not installed or the capture driver is unavailable.

Fix:
Install Npcap from https://npcap.com or run the included npcap.exe if provided in
the NetScope package. Restart NetScope after installation.

--------------------------------------------------------------------------------

PROBLEM: Capture Profile does not appear to apply.

Fix:
Select the intended profile from the dropdown or profile table and click Apply.
The active filter/search should update and the packet/live views should refresh.
If results still look unchanged, verify that the selected traffic actually exists
in the current capture.

--------------------------------------------------------------------------------

PROBLEM: Network Scanner shows Unknown Manufacturer.

Possible causes:

- MAC address was not available
- OUI prefix is not in the local database
- Online lookup is disabled
- Internet lookup failed
- Device uses a network module whose vendor differs from the device brand

Fix:
Enable online manufacturer lookup in Settings, run the scan again, or use Verify /
Refresh Manufacturer Database. Also check Device Type, Open Services, Hostname,
Web Title, Confidence, and Evidence because the device may still be identified by
fingerprint even if manufacturer is unknown.

--------------------------------------------------------------------------------

PROBLEM: HP printer or another printer is not recognised.

Fix:
Enable common port checks and enhanced device identification. Printer evidence can
come from ports 9100, 631, 515, 5357, hostname, web title, or manufacturer. If the
printer does not expose services or does not return a MAC/vendor, classification
may have lower confidence.

--------------------------------------------------------------------------------

PROBLEM: One Network Tool seems to take a long time.

Explanation:
Trace Route, WHOIS, Port Scanner, and Speed Test can naturally take longer than
Ping or NSLookup. In current versions, tools are separated so other tools should
still be runnable while one tool is busy.

--------------------------------------------------------------------------------

PROBLEM: Ctrl+C copies a header and the cell value.

Expected behaviour:
Selecting one cell should copy only that cell value. If this happens on a specific
page, report the exact page/menu and selected grid so the grid copy handler can be
corrected.

--------------------------------------------------------------------------------

PROBLEM: Help quick button shows the wrong section or empty results.

Fix:
Use Clear, then click the desired quick section again. Save / Replay and Privacy
quick buttons should behave like the other section buttons and filter to their
intended content.

--------------------------------------------------------------------------------

PROBLEM: Remote Agent health endpoint does not respond.

Fix on the Agent machine:

Invoke-RestMethod http://localhost:9443/health

If it fails, check:

- Agent service is running
- Port 9443 is available
- Firewall rule exists
- URL reservation exists
- Setup was run as Administrator

--------------------------------------------------------------------------------

PROBLEM: Port 9443 does not work.

Run PowerShell as Administrator:

netsh http add urlacl url=http://+:9443/ user=Everyone

Add firewall rule:

New-NetFirewallRule -DisplayName "Arynox NetScope Agent 9443" -Direction Inbound -Protocol TCP -LocalPort 9443 -Action Allow

Check if port is listening:

netstat -ano | findstr 9443

================================================================================
26. WINDOWS SECURITY WARNING
================================================================================

Windows may show a warning when running a newly downloaded EXE, especially if the
file is not code-signed.

This does not automatically mean the app is unsafe. It usually means Windows does
not yet recognise the publisher or the file reputation.

For a professional public release, use a code-signing certificate and sign the EXE
or installer.

================================================================================
27. COPYRIGHT AND COMPANY INFORMATION
================================================================================

Arynox NetScope is developed by Arynox | IT Services.

Website:
https://arynox.com

Copyright:
Copyright (c) 2026 Arynox | IT Services. All rights reserved.

Current version:
v12.2.0

Main app version:
v12.2.0

Agent version:
v12.2.0

Agent Setup version:
v12.2.0

Last updated release:
10/05/2026

The app, name, design, branding, documentation, and related materials are owned by
Arynox | IT Services unless otherwise stated.

================================================================================
28. SUPPORT
================================================================================

For more information about Arynox, services, products, and support, visit:

https://arynox.com

================================================================================
END OF FILE
================================================================================
