Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

Installation scenarios in ServerProtect for Microsoft Windows/Novell Netware

    • Updated:
    • 13 Apr 2016
    • Product/Version:
    • ServerProtect for Microsoft Windows/Novell Netware 5.7
    • ServerProtect for Microsoft Windows/Novell Netware 5.8
    • Platform:
    • N/A N/A
Summary
This article will help you select the most appropriate scenario to install ServerProtect on your network(s). The following scenarios focus on Local Area Networks (LANs), although it is also possible to manage ServerProtect across Wide Area Networks (WANs) such as, corporate Intranets, using TCP/IP.
Details
Public

Trend Micro ServerProtect supports Microsoft Windows and Novell NetWare platforms. If you are installing ServerProtect on your network for the first time, you must set the destination server as an Information Server, then configure the Normal Servers to join it. An Information Server must have at least one ServerProtect domain to manage its Normal Servers.

 
If you have many servers concentrated in different geographical locations, set up an Information Server (IS) in each location.

The following table shows the different installation environments for each ServerProtect setup component on Microsoft Windows platforms:

Installation Scenarios on MS Windows
Windows VersionInformation ServerNormal ServerManagement Console
Windows 2000 Professional  
Windows 2000 Server/Advance Server
Windows 2003 Server family 32-bit
Windows 2003 Server family 64-bit
(WOW64)

(WOW64)
Windows 2008 Server family 32-bit without Hyper-V
Windows 2008 Server family 64-bit with Hyper-V
(WOW64)

(WOW64)
Windows 2008 Server family 64-bit without Hyper-V
(WOW64)

(WOW64)
Windows 2008 server family 32-bits server core mode  
Windows 2008 server family 64-bits server core mode  
Windows XP Desktop family  
Windows Vista Desktop family  
 
Windows 2003 server family includes the Standard version, Enterprise version, Storage Server, and Datacenter Server.

This section describes the firewall settings of ServerProtect components. Make sure to configure your firewall correctly ensure that the communication is open.

Firewall Setting for machines with Management Consoles
  • Open the 1000-1009 port for TCP protocol.

    1000-1009 is used by Management console to receive the event back message from information server.

    The management console will listen at the port 1000 when startup. If the port is occupied by other program, management console will find one available port from 1000 – 1009.

Firewall settings for the Information Server
  • Open the 5005-5014 ports in TCP protocol.

    Port 5005 is used to receive the commands from Management Console. Normally, 5005 must be opened. If it is used by other program, please find one available port from 5006-5014 and open firewall setting.

  • Open ports 3000-3009 (UDP).

    Port 3000 is used to receive broadcast message. If port 3000 is occupied by certain program, please find one available port from 3000-3009 one by one and open the firewall.

  • Open ports 137-139 for RPC Over named pipe.
    • 137 (UDP)
    • 138 (UDP)
    • 139 (TCP)

    These ports are opened to enable SPNT to use RPC over named pipe protocol to communicate.

  • Open port 3628 (TCP).

    Port 3628 is used to receive event back.

  • Open port 1921 for SPX/TCP with Netware.

    Port 1921 is used to communicate with Netware in SPX/TCP protocol.

Firewall setting in the Windows machine with Normal Server
  • Open port 5168 for listening RPC over TCP/IP from the Information Server.

    Port 5168 is used to receive commands from information server.

  • Open ports 137-139 for named pipe.
    • 137 Protocol is UDP
    • 138 Protocol is UDP
    • 139 Protocol is TCP

    These ports are opened to enable SPNT to use RPC over named pipe protocol to communicate.

    Firewall settings in the netware machine with Normal Server.

  • Open port 9921 (SPX/TCP).

    This port is used to receive commands from the Information Server

If you are installing ServerProtect for the first time, and all the servers on your network are running a Windows Server, the installation is quite straightforward.

To deploy ServerProtect in a Microsoft Windows environment:

  1. Install the Information Server.
  2. Install the Normal Server on the Information Server computer.
  3. Install the Management Console on the Information Server computer.

    You can install additional Management Consoles on any Windows server or desktop system computer in the network.

     
    Only one Management Console can manage an Information Server at any given time.
  4. Update ServerProtect pattern and scan engine files.
  5. Create additional ServerProtect domains to manage your Normal Servers.
  6. Install the remaining Normal Servers using the Management Console.

Steps 1, 2 and 3 can be executed simultaneously during the initial Setup.

Even in NetWare environments, the portion of the network where the Management Console and the Information Server play their roles still has to be installed and executed on Microsoft Windows platform(s). Only the ServerProtect Normal Server component for NetWare (NW) is installed on NetWare server platforms.

ServerProtect can be used to protect a file server network composed of server platforms of both Microsoft Windows and Novell NetWare.

Microsoft Windows - Novell NetWare Mixed Environment

Microsoft Windows - Novell NetWare Mixed Environment

ServerProtect can be managed from multiple locations across a WAN. However, to ensure proper network performance, Trend Micro suggests that you install Information Servers in the same network domain of a workgroup of the network as the Normal Servers they manage.

Because the Management Console uses TCP/IP to communicate with Information Servers, it’s easy to manage ServerProtect from any point inside most company Intranets.

Premium
Internal
Rating:
Category:
Configure; Install
Solution Id:
1096993
Feedback
Did this article help you?

Thank you for your feedback!

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support


To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.


Need More Help?

Create a technical support case if you need further support.