The server administration is web-based. When double-clicking the desktop icon, it opens http://localhost in your web browser, which means the default port number is 80. Fail to see the administration page, it’s because the default port #80 has been engaged by other web applications. And nChronos will try to use port 81 (1 increment at a time). So you can try this URL in your browser: http://localhost:81. If port 81 is unavailable, try 82.
The administration port is used for the web browser to open nChronos Administration portal pages. The communication port is open for nChronos console to connect to the server.
Yes, the connections between nChronos server and console are encrypted by private encryption algorithm, which secures data transmissions and minimizes the length of data.
First you need to make sure the server is up and running, and then check if you use the same communication port number as specified on the server (by default port # 3,000). Then you need to check your account and password.
You need to click-n-drag on the trend chart to select a time slice. When a time span specified, the views will show data among that time period only.
Please follow these steps to drill-down: check the items you need to drill-down in any view (except the Summary view) > right-click to open context menu > hover cursor on Drill Down > select a sub statistics type.
This is because only the email server with port number 25 is supported. Therefore, you need to make sure the mail server accepts connections from port 25, and the port number is set 25 in Alarm Options.
In any view, check the items that you want to download the packets of them, right-click and choose Download Packets from the context menu. Then specify a local folder and file name to save the packets, and click Start button.
Note that you are not suggested to check too many items and download packets from a remote server because they may take a large volume of traffic and take a long time.
Comments
nChronos analyzes network traffic by analyzing packets. It cannot be integrated to an SIEM solution for correlating network events with log data.
RSS feed for comments to this post