Setting up networking configuration

To set up networking based on system networking information:
  1. Make sure that RICOH ProcessDirector has access to a Domain Name System (DNS) server. The DNS server must have correct entries for the host name and IP address of each RICOH ProcessDirector primary computer and application/secondary computer on the network.
      Note:
    • RICOH ProcessDirector supports both IPv4 and IPv6 protocols. If you use IPv4, IP addresses can be expressed using dotted-decimal addresses or the fully qualified host name. If you use IPv6, you must use the fully qualified host name of the server.
    • If you use an IPv6 address, you must complete additional configuration steps after you install RICOH ProcessDirector. See Configuring to use IPv6 addresses.
  2. In your firewall, open any ports that RICOH ProcessDirector uses. Depending on your configuration, you might need these ports:

    Ports to open for the RICOH ProcessDirector primary server

    Port Used by (Client) Used for (Purpose)
    15080 User workstation Access to the RICOH ProcessDirector user interface if not using TLS.
    15090 Administrator workstation Access to the RICOH ProcessDirector Feature Manager interface if not using TLS.
    15443 User workstation Access to the RICOH ProcessDirector user interface if using TLS.
    15453 Administrator workstation Access to the RICOH ProcessDirector Feature Manager user interface if using TLS.
    515 Customer application Required when sending jobs to RICOH ProcessDirector using LPR.
    5001-65535 Customer mainframe Sending jobs to RICOH ProcessDirector using Download for z/OS or AFP Download Plus. The port numbers defined in RICOH ProcessDirector must match the port numbers defined as printers on the mainframe.
    15080 or 15443 RICOH TotalFlow Print server Sending printing status to RICOH ProcessDirector.
    15081 Administrator workstation Importing the custom PDF printer definition to the RICOH ProcessDirector server that will be communicating with the printer

    Only necessary when using custom PDF printers. Most systems do not use custom PDF printers.

    Ports to open for printers

    Port Used by (Client) Used for (Purpose)
    161 RICOH ProcessDirector primary server Getting printer status and information using SNMP.
    8010 RICOH ProcessDirector primary server Getting printer status and information using SNMP.
    9100-9103 RICOH ProcessDirector primary server Sending jobs to a printer with a EFI Fiery controller using Postscript job tickets.

    Ports to open for LDAP server

    Port Used by (Client) Used for (Purpose)
    389, 636, or other port as configured. RICOH ProcessDirector primary server Using LDAP to authenticate users.

    Ports to open for printers that support JMF interfaces 1

    Port Used by (Client) Used for (Purpose)
    80 RICOH ProcessDirector primary server Sending IMSS queries using the HTTP protocol.
    8010 RICOH ProcessDirector primary server Sending JMF files to EFI Fiery controllers.
    9100 (default) - 9103 RICOH ProcessDirector primary server Sending jobs to a printer with a EFI Fiery controller using Postscript job tickets.

    9100 is the default port. EFI printers use port 9102.

    1These printers are defined in RICOH ProcessDirector as Ricoh PDF Printer objects.

    Ports to open for Passthrough printers

    Port Used by (Client) Used for (Purpose)
    515 RICOH ProcessDirector primary server Receiving jobs from RICOH ProcessDirector using LPR.

    Ports to open for IPDS printers

    Port Used by (Client) Used for (Purpose)
    5001-65535 RICOH ProcessDirector primary server Sending files to RICOH ProcessDirector using Download for z/OS or AFP Download Plus.

    These port numbers are configured when you create the input devices that receive these jobs. Open these ports after you define the input devices.

    Ports to open for a transform server

    Port Used by (Client) Used for (Purpose)
    16080 Administrator workstation Accessing the Transform Features user interface if using any of the RICOH Transforms.

    Ports to open for the Reports feature

    Port Used by (Client) Used for (Purpose)
    5432 RICOH ProcessDirector primary server and any system accessing RICOH ProcessDirector reports data Accessing the PostgreSQL database used to store data collected by the Reports feature. This database might be on the primary computer or on a different computer on your network.

    Using a PosgreSQL database installed separately as the primary database or when collecting data with the Reports feature.

    This port can be different depending on the port you specified when setting up the database.

    Ports to open for a primary PostgreSQL database

    Port Used by (Client) Used for (Purpose)
    5442 RICOH ProcessDirector primary server Communication with the PostgreSQL database for RICOH ProcessDirector.

  3. Verify network connectivity:
    1. To verify that host name resolution is working, enter this command:
      host localhost

      If you can access the DNS server, the response includes the host name localhost or loopback and the address 127.0.0.1. For example:

      localhost.mycompany.com is 127.0.0.1

    2. From the computer where you will access the RICOH ProcessDirector user interface, use both the host name and the IP address to ping the primary computer.
    3. From all application and secondary computers (if any), ping the primary computer.
    4. From the primary computer, ping all secondary computers (if any).
    5. Contact the network administrator if you are not successful with any of these verifications.
  4. Verify that the speed, duplexing, and autonegotiation settings for the Ethernet card are those that your network administrator recommends for optimum performance. The optimum settings are different for each installation.
    To display and change these settings:
    1. Log in as the root user.
    2. To display the Ethernet settings, enter:
      ethtool eth0
    3. If necessary, use the ethtool command to change these settings. Check with the network administrator for the appropriate flags and values for your network. For example, this command sets full-duplex mode:
      ethtool -s eth0 duplex full

      This command sets autonegotiation on:

      ethtool -s eth0 autoneg on

  5. Verify that the system listens on open ports. You can use the netstat command to verify the listening ports.
Parent topic: Installing required software