In order for DomainScan Pro to monitor the network flawlessly, DomainScan Pro Service must have full access to probe network devices on the network. This means that a firewall rule must exist that grants DomainScan Pro Service full access to the entire network.

For instance, Windows XP with SP2 or Norton Internet Security will block traffic to/from DomainScan Pro by default

For DomainScan Pro to work, some network functionality cannot be blocked. DomainScan Pro use the same protocols that Windows and other type of network devices uses in order to communicate with one another.

On the host server, it is required that the Computer Browser service runs without restrictions, because this service is responsible for obtaining and maintain the list of currently known computers, and DomainScan Pro will by default base device collection on this service being able to deliver the list.

If the service is either not running or blocked by a software firewall (Windows Firewall will block this service from running on Windows XP SP2), then DomainScan Pro will fail to monitor devices, unless device lists are defined.

To test whether or not the service is working properly, use the Connection Test option in DomainScan Pro (in the Help menu).
If the test fails, please refer to this Microsoft document, which, in details, explains the reason for this behavior and how to make the service run uninterrupted.

Another way to test if Windows is capable of returning device names, open a Command prompt, and type ‘Net View’.

These Windows services and protocols must be allowed to communicate with the network (inbound and outbound):

RPC, DCOM and SMB.

Refer to this document for the corresponding TCP/UDP port names.

It is highly recommended that the echo request (ping) command is enabled on monitored devices as this will significantly lower the scan cycle period and it will allow DomainScan Pro to function out-of-the-box.

For the mail system to work, TCP port 25 must be opened to the mail server where DomainScan Pro must place messages.
(DomainScan Pro supports alternative TCP ports if the mail server is configured to use an alternative port)

In case that SNMP queries or monitors are to succeed, SNMP traffic is running on UDP ports 161 and 162

For DomainScan Pro to be able to communicate with Active Directory, a number of ports must be enabled, but because of the fact that all needed ports are required to be opened in order for Active Directory to work, no additional ports needs to be configured.