RSLinx sends out a broadcast which every address should respond to. Since a ping is not broadcast but rather sent directly to the destination the router passes it along. But only after enabling directed-broadcast at the router. This has the exact symptoms you describe, unable to browse remote subnet, but able to ping each component singly. I know from personal experience that the router between the subnets needs to have directed-broadcast enabled to use ETHIP in RSLinx.
Sorry, I'm kind of late to the party here. My guess is that either your working computers networking are not configured identically to your non-working computer, or that there is a firewall or router difference.
RSLINX CLASSIC LITE 3.60.00 DRIVER
When you are setting up an Ethernet driver in RSLinx, the term 'remote subnet' is the traditional TCP/IP meaning, where there is an IP router in between your network and the remote network. The term 'remote subnet' is causing a little confusion as well.Įarthscape is thinking of it in terms of a network that is accessible only by browsing from one network module to another across a ControlLogix backplane. It's also possible that something in your IP network is preventing the broadcast from working correctly. If your Windows firewall is blocking those responses (or the broadcast itself), that would be consistent with the fact that the Ethernet Devices driver works, and with your description of other computers with the exact same configuration working correctly. The EtherNet/IP driver uses a broadcast packet to send out a "List Identity" service request, to which all the EtherNet/IP devices send back an identity packet.