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.
Setting up Domino® servers on the network
Before and after installing a Domino® server, perform required tasks.
Server setup tasks specific to TCP/IP
After you run the Domino® Server Setup program, complete these procedures:
Binding an NRPC port to an IP address
By default, all TCP/IP-based services on an HCL Domino® server listen for network connections on all NICs and on all configured IP addresses on the server. If you have enabled more than one Notes® network port for TCP/IP (TCP port for NRPC) on either a single Domino server or a Domino partitioned server, you must associate the NRPC ports and IP addresses by binding each port to an address.

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.
  - Setting up Domino® servers on the network
    Before and after installing a Domino® server, perform required tasks.
    - Setting up Notes® named networks
      The Domino® Server Setup program automatically places all servers that are in a Domino domain and that run the same network protocol in the same Notes® named network (NNN). In the Server document, the setup program assigns each NNN a default name in the format portname network.
    - Fine-tuning network port setup on a server
      After you install and set up a Domino® server, review the list of network ports that were enabled by the Server Setup program. Unless you customize network settings during setup, Domino enables ports based on the current operating system configuration. To conserve system resources, disable the ports for protocols that you do not need.
    - Server setup tasks specific to TCP/IP
      After you run the Domino® Server Setup program, complete these procedures:
      - Setting up a secondary name server
        To ensure that the Notes® Name Service is always available to Notes users, assign a secondary name server in users' Location documents.
      - Changing the TCP/IP connection-time-out interval
        You can increase the number of seconds that HCL Domino® waits before terminating a connection attempt. For example, increasing the time-out interval is often necessary on a server that dials up other Domino servers. The default time-out interval is 5 seconds.
      - Enabling support for IPv6 on a Domino® server
        You can enable support for IPv6 on a Domino® server that runs the IMAP, POP3, SMTP, LDAP, or HTTP service.
      - Reordering multiple server ports for TCP/IP
        If a Domino® server has multiple Notes® network ports for TCP/IP, the order in which these ports are listed in the NOTES.INI file and the Server document affects how other servers and workstations connect to this server. The Ports setting in the NOTES.INI file determines which port a workstation or server tries first. In the absence of other settings that bind an NRPC, POP3, IMAP, SMTP, or LDAP service to an IP address, all of these services will try to use the port listed first in the NOTES.INI file.
      - Binding an NRPC port to an IP address
        By default, all TCP/IP-based services on an HCL Domino® server listen for network connections on all NICs and on all configured IP addresses on the server. If you have enabled more than one Notes® network port for TCP/IP (TCP port for NRPC) on either a single Domino server or a Domino partitioned server, you must associate the NRPC ports and IP addresses by binding each port to an address.
      - Binding an Internet service to an IP address
        If the HCL Domino® server has multiple HCL Notes® network ports for TCP/IP (NRPC ports) and the server is also hosting the SMTP, POP3, IMAP, LDAP, or Domino IIOP (DIIOP) service, you must specify the NRPC port that you want the service to use in the NOTES.INI file. If you do not specify an NRPC port for an Internet service, by default the service will use the port listed first in the Ports setting in the NOTES.INI file. You can specify the same NRPC port for multiple Internet services.
      - Assigning separate IP addresses to partitions on a system with a single NIC
        If you use a single NIC with multiple IP addresses, you must complete additional configuration instructions, which are based on your operating system, for each server partition. Using separate IP addresses with a single NIC can have a negative impact on the computer's I/O performance.
      - Configuring a partitioned server for one IP address and port mapping
        To configure server partitions to share the same IP address and the same NIC, you use port mapping. With port mapping, you assign a unique TCP port number to each server partition and designate one partition to perform port mapping. The port-mapping partition listens on port 1352 and redirects HCL Notes® and HCL Domino® connection requests to the other partitions.
      - Changing a TCP or TLS port number
        The following sections describe the TCP ports that HCL Domino® services use and provide guidelines should you ever need to change these ports.
      - Confirming that TCP/IP is configured properly
        Before you can use TCP/IP for communication, confirm that the configuration is properly set up.
- Configuring users and servers
  Topics in this section describe how to set up users and servers.

Binding an NRPC port to an IP address

By default, all TCP/IP-based services on an HCL Domino® server listen for network connections on all NICs and on all configured IP addresses on the server. If you have enabled more than one Notes® network port for TCP/IP (TCP port for NRPC) on either a single Domino® server or a Domino® partitioned server, you must associate the NRPC ports and IP addresses by binding each port to an address.

About this task

When setting the NOTES.INI variables for port mapping, do not include a zone in a port mapped address. The zone is only valid locally.

Note: Do not change the assigned TCP port number unless you have a way to redirect the inbound connection with Domino® port mapping or a firewall that has port address translation (PAT).

Procedure

For each IP address, make sure you have added a Notes® port TCP/IP. Also make sure that each port has a unique name.
In the NOTES.INI file, confirm that these lines appear for each port that you added:
```
Ports=TCPIPportnameTCPIPportname=TCP, 0, 15, 0
```
Where TCPIPportname is the port name you defined.
For each port that you want to bind to an IP address, add this line to the NOTES.INI file:
```
TCPIPportname_TCPIPAddress=0,IPaddress
```
Where IPaddress is the IP address of the specific NIC.
For example:
```
TCPIP_TCPIPAddress=0,130.123.45.1
```
Note: Because IPv6 addresses include colons, you must enclose the address in brackets. For example:
```
TCPIP_TCPIPAddress=0,[fe80::290:27ff:fe43:16ac]
```
Optional: To help you later remember the function of each port, add the default TCP port number for NRPC to the end of the line you entered in Step 3, as follows:
```
:1352
```