Narrow down your computer's NICs as well, of course shut off WiFi, disable any VPN connections. The EtherNet/IP driver uses a broadcast packet so you have to carefully select which IP network it is connected to, and firewalls and VPNs often prevent it from working. Try also making an exception in your firewall for TCP Port 2222, an older A-B protocol that the RSLinx Classic Ethernet Devices driver likes to try and fail before trying port 44818. I presume you've verified that the PanelView is at that 192.168.1.103 address by looking at its actual configuration screens, and eliminated the possibility of a duplicate IP by unplugging it and verifying that PING fails. In addition to good old built-in PING, try TCPing with the target port 44818, to see if your computer can get a TCP connection through its firewall (and the device at that IP is listening on that port, which all A-B devices should). Can you get a response from the PanelView 800 in a Web browser ?
0 Comments
Leave a Reply. |