As you mentioned from the outset that you are connecting to both devices from your laptop, it would suggest that there is some network topology in play here? A switch or router appliance perhaps between your laptop and the devices?
The EtherNet/IP driver in RSLinx Classic relies on the ability to propagate Broadcast TCP/IP packets onto the wire (network). It's quite possible that an appliance between your laptop and the devices is configured to block Broadcast traffic. This is usually done to prevent what are known as Broadcast Storms (I won't elaborate). The Ethernet devices driver, which you now have configured and working thanks to Ron, uses Unicast TCP/IP, which is typically never blocked. This is likely why it worked.
Further to this deduction, the ME Transfer Utility is using FactoryTalk Linx (formerly RSLinx Enterprise) to communicate with the PanelView terminal. FactoryTalk Linx uses the Ethernet/IP driver as standard, and hence is using Broadcast TCP/IP, which I again suspect is being blocked.
Similar to Ron's good advice in RSLinx Classic, you can also manually add the communications path to the PanelView terminal in FactoryTalk Linx. Under the Communications Setup in the application for the PanelView terminal, right-click on the EtherNet, Ethernet driver and then Add Device. Either use the Find Device box at the top with the PanelView terminal catalog number, or manually search through the EtherNetIP Devices folder until you have your PanelView model and firmware revision. Double-click on it to add it. In the window that appears, manually enter the IP address for the PanelView terminal.
Right-click on the EtherNet, Ethernet driver and select Start Browsing. The PanelView terminal should now hopefully show up and be available in the ME Transfer Utility. This, again, is forcing FactoryTalk Linx to use Unicast TCP/IP.
Regards,
George
