5
2. ERA – client/server architecture
Technically, ESET Remote Administrator consists of two separate components: ERA Server (ERAS) and ERA Console
(ERAC). You can run an unlimited number of ERA Servers on your network as there are no limitations in the license
agreement for their use. The only limitation is the total number of clients your installation of ERA can administer
(see section 2.1.6 , “License keys”).
2.1 ERA Server (ERAS)
The server component of ERA runs as a service under the following Microsoft Windows© NT-based operating
systems: NT4, 2000, XP, 2003 and Vista. The main task of this service is to collect information from clients and to
send various requests to them. These requests, including configuration tasks, remote installation requests, etc., are
created through the ERA Console (ERAC).
ERAS is a meeting point between ERAC and client computers – a place where all information is processed,
maintained or modified before being transferred to clients or to ERAC.
2.1.1
Requirements
ERAS requires a Microsoft Windows NT-based operating system (NT4, 2000, XP, 2003, Vista). The Microsoft
Windows Server Edition is not necessary for ERAS to work. A computer with ERAS should be always online and
accessible via computer network by:
• Clients (usually workstations)
• PC with ERA Console
• Other instances of ERAS (if replicated)
The chart below lists the possible network communications used when ERAS is installed. The process era.exe listens
on TCP ports 2222, 2223, 2224 and 2846. Other communications occur using native operating system processes (for
example “NetBIOS over TCP/IP”).
Protocol
Port
Description
TCP
2222 (ERAS listening)
Communication between clients
and ERAS
TCP
2223 (ERAS listening)
Communication between ERAC and
ERAS
TCP
2221 (ERAS listening)
By default, this port offers
update packages using the Mirror
feature integrated in ERAS (HTTP
communication)
If using all features of the program, the following network ports need to be open:
Protocol
Port
Description
TCP
2224 (ERAS listening)
Communication between the agent
einstaller.exe and ERAS during
remote install
TCP
2846 (ERAS listening)
ERAS replication
TCP
139 (target port from the point of
view of ERAS)
Copying of the agent einstaller.
exe from ERAS to a client using the
share admin$ during push install
UDP
137 (target port from the point of
view of ERAS)
“Name resolving” during remote
install
UDP
138 (target port from the point of
view of ERAS)
“Browsing“ during remote install
TCP
445 (target port from the point of
view of ERAS)
Direct access to shared resources
using TCP/IP during remote install
(an alternative to TCP 139)
The minimum hardware configuration for the deployment of ERAS is also the minimum recommended
configuration for the Microsoft Windows operating system used on the machine.
