If you plan to do more of these you really need your own router that you manage as part of the installed package IMO. If this data is comprimised later by changes he may make to the router that customer may try to hold you accountable for any future security issues.
The other bad thing about using a customers home equipment for this is that he may have sensitive documents and financial data on this computer or NAS drive which many home have nowdays. With the VPN all traffic is encrypted and much harder to tamper with. Start port forwarding Port 80 and everything else is not locked down perfectly the IMO you are "Askin for a Hackin". I would still setup the VPN if I were you. I always very strongly recommend the use of a VPN for this sort of application, though I've had several bad experiences with D-Link equipment. Try using the TCPING utility () to connect to Port 44818 over your internet connection to the site. This causes RSLinx to skip the TCP Port 2222 step. The easy solution is to append ":EIP" to the end of the IP address or hostname in the Ethernet Devices node list. Many VPNs and routers will block the TCP Port 2222 connection attempt, assuming it's some sort of port scan attack. If it gets three "Port Closed" responses in a row, it will switch to trying TCP Port 44818. The "Ethernet Devices" driver in RSLinx Classic tries TCP Port 2222 first, to determine if the target device is an old PLC-5E or SLC-5/05. That obviously won't work over the Internet. The "EtherNet/IP" driver in RSLinx Classic, however, uses a broadcast packet to detect devices. TCP Port 44818 is the correct port for the Allen-Bradley "EtherNet/IP" protocol that the MicroLogix 1400 uses.
0 kommentar(er)
