Home Installing WebPort WebPort User Interface Technical Reference Glossary Search


Troubleshooting WebPort LAN Connections

The WebPort uses a LAN connection for connecting locally to a PLC or to a PC.

Use the following information to help you troubleshoot WebPort LAN connections:

  1. By default, Allow Ping is unchecked in the WebPort Configure:Security dialog. This means that you cannot 'see' the WebPort on your LAN network. If you wish to perform some network checks, turn on Allow Ping so that you can do the checks. When finished, uncheck the option. See Configuring Security Setup for the WebPort.
  2. To avoid cabling issues, ensure you use the RJ-45 cabling guidelines provided in the hardware specification. See Hardware Specifications.
  3. Earlier versions of the WebPort required a crossover cable to communicate between the LAN and a PC. You may use a crossover RJ-45 cable to connect a PLC or a PC to the WebPort LAN as later versions of the WebPort (1.00 onwards) use autosensing to determine which cable is in use.
  4. If the WAN and LAN are in the same subnet, the WebPort will not be able to route properly. In addition, if you physically connect the LAN to the WAN, and the LAN is set up as a DHCP server, which is the default setting, the WebPort will be unable to function properly. You may also disrupt your company's network. Ensure that the LAN and WAN are on different subnets.
  5. If you connect your PC to a WebPort's LAN port, and then connect your PLC to the WebPort's serial port, you have to enable passthrough on the Configure:Serial dialog. You then access your PLC using the WebPort's local IP address. See Configuring Serial Communications Setup and Connecting a PLC Running on a Virtual Machine to a WebPort
  6. If you change the LAN address on the WebPort while the WebPort is still connected to WebPort Connects, the Connects routing does not update. Example. If you establish a remote VPN connection to the WebPort, you are not able to access the devices on the LAN because the static route added to the PC is still pointing to the previous LAN address. To fix this, you need to temporarily disconnect the WebPort from the Connects service, then re-connect it. This updates the route(s).