- Rslinx classic not showing enbt install#
- Rslinx classic not showing enbt driver#
- Rslinx classic not showing enbt software#
- Rslinx classic not showing enbt Pc#
The VPN blocks the EtherNet/IP browse because it is a broadcast packet. Fortunately this is moderately easy to fix if the IT techs will help out by opening up TCP ports 228, and UDP ports 228.
They'll block uncommonly used TCP ports to reduce the encryption engine load, and to prevent mis-use of the VPN circuit by malicious software.
Rslinx classic not showing enbt Pc#
VPN's typically are set up to only support the common kinds of traffic that PC users need Hypertext, e-mail transfer, file transfer, printing, etc. The VPN blocks the EtherNet/IP browse because it is an uncommon port. But then I noticed this key comment: This leads me to think that this might be an interaction between RSLinx and the VPN software. I was about to recommend checking the Default Gateway setting in your controllers' Ethernet configuration, because that is a very common reason for "I can see it locally, but not over a router/vpn/bridge" problem. I'll try getting the ports for RSLinx opened at one of these sites, to see if that works. I just tried the HTTP controller pages for both sites, I can view them on my side of the VPN for both. RSLinx on the local PC can see the devices, but RSLinx on my side of the VPN cannot. I can ping the devices from my side of the VPN, and also from the local PC while connected via VPN. At the 2nd site, the PLC network is connected to their IT network, but as a separate VLAN, using two new Cisco 2950C ethernet switches (actually the 2nd site is the same one from my previous post, re: the communication problem) 3.
At the 1st site, the PLC network is connected to their IT network with a simple home/office ethernet switch (yuk, but at least its not a hub).
Rslinx classic not showing enbt software#
I don't actually know if the Cisco VPN client software talks to software on their end, or to hardware? I know that both customers use mostly cisco equipment though. I don't know which type it would be - at both sites, we are using the Cisco VPN client software on our end (provided by the customer).
Rslinx classic not showing enbt driver#
I did try using the AB_ETH driver and adding the station numbers and ip addresses, but it still would not find any devices. I'm using the AB_THIP (Ethernet/IP) driver.
Rslinx classic not showing enbt install#
Also, RSLinx running on the local PC (the customer's) can see all the devices (using pcanywhere over the VPN I can see this) The two projects in question used: - One CompactLogix 元5E & two PanelView 600's for one project (frst site) - One CompactLogix 元2E & one PanelView Plus 1250 for another (second site) Now that I am using an upgraded install of RSLinx (so there are no old "not found" devices), I cannot see any devices in RSWho, at either of the sites! Is this a bug? A feature? Is there a workaround? Or a way to "force" RSLinx to see the devices again? short of travelling back to the USA an hooking up locally of course.
) Anyway, the problem is as once I have cleared out the old "not found" devices in RSWho, when I connect back to the previous project/customer, RSLinx can no longer see any of the devices. (I have since realised that I maybe should have used "Projects" in RSLinx to seperate things.?.
I have found that I can still see the devices in RSLinx when connected via the VPN, regardless of where I connect from, as long as the devices are still in the RSWho window (old "not found" devices/history - I don't know the correct term) When finishing with that project/customer for example, and moving on to another, I used to remove the old devices from the RSWho windows so they did not constantly show up as "not found". We're in Australia, and the last two projects have been in the USA. We have a couple of similar set-ups, where we connect to our customer's network via a VPN connection. Hi all, I have a strange problem with RSLinx comms over VPN.