Troubleshooting EtherNet/IP Address Commissioning Tool

During operations there may be circumstances and errors that require troubleshooting. Possible causes and solutions to assist in resolving the situation are provided.
Possible causes for the circumstance that the tool cannot receive BootP/DHCP requests
  • The device is not configured to make BootP/DHCP requests (For example, the settings within the device are incorrect on the device or it set for static mode).
  • There is another BootP/DHCP server on the network (For example, a router, a computer, or a managed ethernet switch is providing BootP/DHCP services for a network).
  • The computer is not connected to the same physical network.
  • The computer is not configured to the same subnet.
  • The computer's network settings are incorrect.
    TIP:
    If user needs to change the Settings, the NIC's properties need to be changed.
  • The tool is configured to use a different network interface.
  • The tool is operating in a Virtual Machine (see Use EtherNet/IP Address Commissioning Tool in a virtual machine for more information).
  • The device may take an extended period of time to make a BootP/DHCP request.
    For example, the E300 motor protector takes about a full minute to make its first request, and devices wait an increasing amount of time between each request.
  • The computer is connected on the opposite side of a device utilizing Network Address Translation (NAT) (For example 1783-NATR device or a Stratix switch with NAT enabled).
  • The computer is connected via a wireless network (WiFi).
  • The BootP/DHCP port (67) is allocated by a different process on the workstation.
  • The BootP/DHCP port (67) is being blocked by the computer's firewall because the network profile is set to public.
Possible causes for the circumstance that the device is not accepting the IP address listed in the Tools configuration
  • The subnet mask, gateway address and possible DNS addresses are incorrect.
  • The computer is no longer receiving BootP/DHCP request from the device.
  • Another device on the network is already assigned the same IP address.
  • The configured IP address selected for the device is incorrect or does not match the subnet selected in the
    Settings
    .
Possible cause for the circumstance that the Commission from range is unable to assign addresses
  • The network already contains devices for addresses specified in the range.
Possible cause for the circumstance that the Commission from list does not present any available device to configure
  • The configuration list does not contain any items that have empty MAC addresses.
Before using the EtherNet/IP Address Commissioning Tool, users need to check the following items to avoid problems
  • Check if the selected workstation's Network Interface Card (NIC) is available (If the workstation contains multiple NICs, select the one attached to the subnet associated with the Ethernet devices that need configuration).
  • Check the Subnet.
    • Ensure the
      Subnet Mask
       is configured correctly in
      Settings
      .
    • Ensure the
      Gateway Address
       is either empty or configured correctly in
      Settings
      .
    • Ensure the devices to be configured are on the same subnet.
    • Ensure the IP addresses are in the subnet range.
  • Check if the required ports (EtherNet/IP Address Commissioning Tool UI Service: port 5670 and EtherNet/IP Address Commissioning Tool Windows Service: port 67) are available.
    TIP:
    If Ethernet IP Address Commissioning Tool ports are occupied by other applications, an error message displays. Free the port, and then restart the
    EtherNet/IP Address Commissioning Tool
    .
  • Check if EtherNet/IP Address Commissioning Tool UI Service (EIP Commission Tool UI Service) and Windows Service (EIP Commission Tool Windows Service)are running.
  • Check if the option
    Enable the background service
     is enabled on the
    Settings
     tab.
  • Make sure the EtherNet/IP Address Commissioning Tool currently using is only BOOTP/DHCP server in the network.
    TIP:
    Typically a business or IT managed network will contain a DHCP server. VMware, network routers, and many managed switches also have DHCP services so these types of configurations will create a conflict that prevents the
    EtherNet/IP Address Commissioning Tool
     from receiving BootP/DHCP requests from devices. An isolated network with DHCP disabled in the switches is recommended. Connecting a USB Ethernet adapter to the workstation running the
    EtherNet/IP Address Commissioning Tool
     can simplify the setup in virtual machines.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal