Program hangs for a while, especially after common settings dialog closing. SpiderNM setting dialog right panel is empty, there are no linksets available for monitoring.

In case that program hangs (waiting cursor displaying) and not responding to user input after:

• immidiatly after local monitoring start
• pressing OK button in common settings dialog (F12) and after opening this dialog
• pressing OK button in SpiderNM settings dialog (F10) and after opening this dialog (link \ linksets panel looks empty)

it is possible no connection between workstation and CU server.

First of all, check remote access enabled in a common setup dialog (F12) and CU server IP address entered correctly inside field remote packet source IP-address.

There is a technical requirement for SPIDER local monitoring program working: workstation can establish TCP-coonection over 10240 port.

For example, CU server IP-address is 192.168.50.30. To check CU server TCP-connection possibilitym run command interpretator (Start -> Execute -> cmd) and enter following:

C:\>telnet 192.168.50.30 10240

In other cases (for example, Connection refused or Can't resolve name) it is required to consult with system administrator that provide service for IP-network for workstation and CU server. The next data can be useful:

1. Command output for ping 192.168.50.30
2. Command output for tracert 192.168.50.30
3. Workstation IP-addres ipconfig /all
4. Information about that TCP-connection over 1024 port required When using Windows firewall, it can be wrong configured for blocking 10240...