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 NetBIOS
After you run the Domino® Server Setup program, complete these procedures:
Defining a NetBIOS LANA number for a Notes® network port
To run NetBIOS on a server, after you complete the Server Setup program, you must determine the NetBIOS LANA number to which the Notes® network port will be bound. The NetBIOS LANA number is a logical number that represents a NetBIOS transport protocol stack on a NIC. You must know which transport protocol Notes workstations and other Domino® servers are using for NetBIOS within your workgroup or company.

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:
    - Server setup tasks specific to NetBIOS
      After you run the Domino® Server Setup program, complete these procedures:
      - Defining a NetBIOS LANA number for a Notes® network port
        To run NetBIOS on a server, after you complete the Server Setup program, you must determine the NetBIOS LANA number to which the Notes® network port will be bound. The NetBIOS LANA number is a logical number that represents a NetBIOS transport protocol stack on a NIC. You must know which transport protocol Notes workstations and other Domino® servers are using for NetBIOS within your workgroup or company.
      - Creating additional network ports for NetBIOS
        After you run the HCL Domino® Server Setup program, you can create network segments for multiple NetBIOS interfaces on the same computer by adding an HCL Notes® network port for NetBIOS for each additional NIC.
- Configuring users and servers
  Topics in this section describe how to set up users and servers.

Defining a NetBIOS LANA number for a Notes® network port

To run NetBIOS on a server, after you complete the Server Setup program, you must determine the NetBIOS LANA number to which the Notes® network port will be bound. The NetBIOS LANA number is a logical number that represents a NetBIOS transport protocol stack on a NIC. You must know which transport protocol Notes® workstations and other Domino® servers are using for NetBIOS within your workgroup or company.

About this task

If the computer running the Domino® server has more than one NIC running the same protocol stack, you must define a different NetBIOS LANA number for each Notes® network port for NetBIOS.

NetBIOS systems using the same transport protocol should be in the same Notes® named network. If you create Connection documents on the server, the LAN port you select must also be for the same transport protocol.

Procedure

From the Domino® Administrator, click the server for which you want to define a LANA number.
Click the Configuration tab.
From the Domino® Administrator's Tools pane, select Server > Setup Ports.
Select the portname port, where portname is the name of the NetBIOS port for which you are defining a LANA number.
Click Portname Options, and select Manual.
Enter the correct LANA number.
Click OK.

To find the LANA number for a NetBIOS protocol on a Windows™ XP or 2000 system

About this task

A Microsoft™ Windows™ XP or 2000 system does not have a direct means to see the LANA associations. For Windows™ XP or 2000 systems you can either review the system's registry bindings or use a Microsoft™ tool called LANACFG to see and change the LANA number assignments.

The following is an example of the tool's output from a Windows™ 2000 server.

lanacfg [options]

showlanapaths - Show bind paths and component descriptions for each exported lana

setlananumber - Change the lana number of a bind path

rewritelanainfo - Verify and write out lana info to the registry

showlanadiag - Show lana diagnostic info

From the DOS prompt, enter

C:\>lanacfg showlanapaths

You see the following:

Lana:   4

-->NetBEUI Protocol-->3Com EtherLink III ISA (3C509/3C509b) in Legacy mode

Lana:   7

-->NetBEUI Protocol-->WAN Miniport (NetBEUI, Dial Out)

Lana:   3

-->NWLink NetBIOS

Lana:   0

-->WINS Client(TCP/IP) Protocol-->Internet Protocol (TCP/IP)-->3Com EtherLink III ISA (3C509/3C509b) in Legacy mode