Troubleshooting and FAQs
5
-
15
Configuration Issues
#
ISSUE
CORRECTIVE ACTION
Issues with Trend Micro Control Manager
1
Network VirusWall
Enforcer 2500 is
unable to register with
the Control Manager
server
Check all network connections and ensure you have correctly
performed preconfiguration (refer to the
Getting Started Guide
>
Preconfiguring Network VirusWall Enforcer 2500
section for more
information).
Network VirusWall Enforcer 2500 only registers to Control Manager
3.5 through port 443. If Control Manager is installed on Windows
2003, configure the firewall to allow port 443 to communicate with
Network VirusWall Enforcer 2500.
If the OS on which Control Manager 3.5 resides is Windows Server
2003, Network VirusWall Enforcer 2500 may not be able to use the
Control Manager time service to synchronize with the server and will
therefore be unable to register to the Control Manager service.
To remedy this problem, choose one of the following:
1. Install Active Directory on the Windows Server 2003 server so
Network VirusWall Enforcer 2500 can synchronize with the
Windows Server 2003 time service.
2. Disable the Windows Server 2003 time service and enable
Trend
Micro Network Time Protocol
so Network VirusWall Enforcer 2500
can synchronize with the Control Manager server time service.
OR
Check to ensure that ports 80 and 443 are enabled in Control
Manager’s IIS settings.
OR
If there are multiple IP addresses bound to the Control Manager
server’s network card, Network VirusWall Enforcer 2500 may not
register to Control Manager successfully using FQDN. To resolve
this issue, configure only one IP address per network card.
2
Network VirusWall
Enforcer 2500
displays a
sync time
error and is unable to
register to CM server
A sync time error displays when Network VirusWall Enforcer 2500 is
unable to synchronize with the Control Manager server.
To remedy this problem, do the following:
On the Web console
Administration
>
Time Settings
screen,
select Use a NTP server to update the time.
T
ABLE
5-3.
Troubleshooting Network VirusWall Enforcer 2500 configuration
issues