Ask a question?
  • Contact Us
  • Support Case System
  • Support Forum

I Suspect That My User Is Experiencing Port Or Networking Problems. What Do I Do?

Port and networking problems arise in a variety of contexts. Choose the context that corresponds to your user:

  1. Do firewall restrictions prevent a user from download OpenLink software?
    • Test both HTTP and FTP links.
    • Provide a DAV link to the file.
    • Attempt to FTP the file to a user site.
    • Attempt to email components to the user.
    • Provide files to user via CD. (Requires Manager Approval.)
  2. Do networking problems prevent transfer of an OpenLink download to the target machine?
    • Urge the user to seek assistance from the on-site network administrator.
    • Tell the user to transfer the file(s) via CD or disk.
  3. Do port problems prevent Multi-tier users from starting their Request Brokers?
    • Login to the machine that contains the Multi-tier server components.
    • Use a text editor to open the oplrqb.ini file that resides in the /bin sub-directory of the OpenLink installation.
    • Locate the [Protocol TCP] section.
    • Locate the Listen parameter. (1.x and 3.x users locate PortLow.)
    • Close oplrqb.ini.
    • Run netstat -a.
    • If Listen or PortLow is occupied, assign a new port in oplrqb.ini.
    • If Listen or PortLow is not occupied, this may not be a port problem.
  4. Do users not know what ports to pass in OpenLink data source names? Inform users that the only OpenLink-specific ports appear in the [Protocol TCP] section of the server component's ~/openlink/bin/oplrqb.ini file. Any other port would be gleaned from database-related configuration files or utilities.
  5. Do firewalls prevent Multi-Tier clients from contacting Multi-Tier Request Brokers?
    • Login to the machine that contains the Multi-Tier server components.
    • Use a text editor to open the oplrqb.ini file that resides in the /bin sub-directory of the OpenLink installation.
    • Locate the [Protocol TCP] section. For example:
            [Protocol TCP]
            PingWatchdog = No
            PingInterval = 600
            ;IPAddress      = 127.0.0.1
            PortLow      = 5000
            PortHigh     = 5020
      
    • Make sure PortHigh is uncommented and set. PortHigh should equal PortLow + the number of concurrent connections granted by the license + a few extra ports.
    • Record the PortLow-PortHigh range.
    • Record the Listen port value. (OpenLink 1.x and 3.x do not have Listen.)
    • Close oplrqb.ini.
    • Open the Listen and PortLow-PortHigh TCP ports on the firewall.
    • Open UDP port #60001--in addition to TCP PortLow-PortHigh--to accommodate 1.x and 3.x drivers.
  6. Do Multi-Tier port settings restrict the number of concurrent connections?
    • Login to the machine that contains the Multi-Tier server components.
    • Use a text editor to open the oplrqb.ini file that resides in the /bin sub-directory of the OpenLink installation.
    • Locate the [Protocol TCP] section. For example:
            [Protocol TCP]
            PingWatchdog = No
            PingInterval = 600
            ;IPAddress      = 127.0.0.1
            PortLow      = 5000
            PortHigh     = 5020
      
    • Make sure PortHigh is uncommented and set. PortHigh should equal PortLow + the number of concurrent connections granted by the license + a few extra ports.
    • Save changes and exit the file.
    • Restart or reinitialize the Request Broker and test.