Home
Configuring
Use this information to configure your network, users, servers (including Web servers), directory services, security, messaging, widgets and live text, and server clusters.
Configuring a network
This section presents the planning concepts and setup procedures necessary for a successful HCL Domino® deployment over a network. It provides information on network protocols from a Domino perspective but does not attempt to provide general network information.
Network security
Physical network security is beyond the scope of this documentation, but you must set it up before you set up connection security. Physical network security prevents unauthorized users from breaking through the network and using one of the operating system's native services -- for example, file sharing -- to access the server. Physical network security also comes into play when any data is exposed, as the potential exists for malicious or unauthorized users to eavesdrop both on the network where the Domino® system resides and on the system you are using to set up the server.

Configuring
Use this information to configure your network, users, servers (including Web servers), directory services, security, messaging, widgets and live text, and server clusters.
- Configuring a network
  This section presents the planning concepts and setup procedures necessary for a successful HCL Domino® deployment over a network. It provides information on network protocols from a Domino perspective but does not attempt to provide general network information.
  - Domino® and networks
    A variety of client systems can use wireless or wired technology to communicate with Domino® servers over local area networks (LANs), wide area networks (WANs), and metropolitan area networks (MANs). For example, Notes® workstations and Domino servers use the Notes remote procedure call (NRPC) protocol running over the LAN's network protocol to communicate with other Domino servers. Other client systems, such as Web browsers, Internet mail clients, wireless application protocol (WAP) devices, and personal information management (PIM) devices, can also communicate with Domino servers.
  - Network security
    Physical network security is beyond the scope of this documentation, but you must set it up before you set up connection security. Physical network security prevents unauthorized users from breaking through the network and using one of the operating system's native services -- for example, file sharing -- to access the server. Physical network security also comes into play when any data is exposed, as the potential exists for malicious or unauthorized users to eavesdrop both on the network where the Domino® system resides and on the system you are using to set up the server.
    - NRPC and Internet connection security
      To control connection access, you typically use a network hardware configuration, such as a firewall, reverse proxy, or Domino® pass-through server, to which you can authorize connections and define access to network resources.
    - Using a Domino® pass-through server as a proxy
      A proxy is a system that understands the type of information transmitted -- for example, NRPC or HTTP-format information -- and controls the information flow between trusted and untrusted clients and servers. A proxy communicates on behalf of the requester and also communicates information back to the requester. A proxy can provide detailed logging information about the client requesting the information and the information that was transmitted. It can also cache information so requesters can quickly retrieve information again.
    - TCP/IP security considerations
      In a TCP/IP network, configure all Domino® servers to reject Telnet and FTP connections. Furthermore, do not allow file system access to the Domino server or the operating system on which it runs, unless you are sure you can properly maintain user access lists and passwords and you can guarantee a secure environment.
    - Mapped directory links and Domino® data security
      To ensure data security, do not create a mapped directory link to a file server or shared Network Attached Storage (NAS) server for a Domino® server. These links can cause both database corruption and security problems.
  - Setting up Domino® servers on the network
    Before and after installing a Domino® server, perform required tasks.
- Configuring users and servers
  Topics in this section describe how to set up users and servers.

Network security

Physical network security is beyond the scope of this documentation, but you must set it up before you set up connection security. Physical network security prevents unauthorized users from breaking through the network and using one of the operating system's native services -- for example, file sharing -- to access the server. Physical network security also comes into play when any data is exposed, as the potential exists for malicious or unauthorized users to eavesdrop both on the network where the Domino® system resides and on the system you are using to set up the server.

Network access is typically controlled using network hardware -- such as filtering routers, firewalls, and proxy servers. Be sure to enable rules and connection pathways for the services that you and others will access.

Newer firewall systems offer virtual-private-network (VPN) services, which encapsulate the TCP/IP packet into another IP wrapper where the inner TCP/IP packet and its data are encrypted. This is a popular way to create virtual tunnels through the Internet between remote sites. If you want to have the Domino® server access both a private VPN and the Internet for SMTP mail, make sure your solution is able to handle full TCP data packets and that it allows dual connections. If not, the Domino® server system may require a second NIC to work around limitations of the VPN solution.