1 / 23

Configuring connections between Dr.Web Enterprise Servers

Configuring connections between Dr.Web Enterprise Servers. Configure connections between Dr.Web Enterprise Servers. Plan and draw the structure of the anti-virus network. Indicate all the estimated information flows and decide how many peer and parent-child connections will be in the network.

burtonb
Download Presentation

Configuring connections between Dr.Web Enterprise Servers

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Configuring connections between Dr.Web Enterprise Servers

  2. Configure connections between Dr.Web Enterprise Servers • Plan and draw the structure of the anti-virus network. • Indicate all the estimated information flows and decide how many peer and parent-child connections will be in the network. • Make sure that: • Both Enterprise Servers work correctly; • For each Enterprise Server, different keys (files Enterprise.key) are used; • The encryption keys (files drwcsd.pub) on both servers are different. • For each server connected to the network, configure a connection with "neighbouring" Servers.

  3. 1 2

  4. MAIN server 3 1 2

  5. AUXILIARY server

  6. 1 5 3 4 2

  7. AUXILIARY server 1 2

  8. AUXILIARY server The window for configuring the connection between the current server and the new server. 1 2

  9. AUXILIARY server

  10. AUXILIARY server

  11. AUXILIARY server • Network list input options: • separated by a dash (for example, 10.4.0.1-10.4.0.10); • separated by a comma and a space (for example, 10.4.0.1-10.4.0.10, 10.4.0.35-10.4.0.90); • using a network prefix (for example, 10.4.0.0/24).

  12. AUXILIARY server

  13. AUXILIARY server

  14. MAIN server 1 2

  15. MAIN server 5 1 2 3 4

  16. MAIN server 1 2

  17. AUXILIARY server 1 2

  18. The connection between the Enterprise Servers has been configured successfully.

More Related