Shipped a machine six months back with an eWON Cosy 131 on it for remote support, S7-1200 on the machine LAN at 192.168.1.10, Cosy LAN side at 192.168.1.250. First support call came in this week and I can't reach any of it.
eCatcher on the laptop connects fine, Talk2M shows the Cosy online and green, tunnel comes up. Ping 192.168.1.10 times out, so does a ping to the Cosy itself, and TIA V17 can't find the CPU either. Someone on another forum reckoned it was an old eCatcher, so I updated that to the current version and rebooted the Cosy from the Talk2M page while I was at it. Came back online, same thing.
Is it the Cosy firmware, or does the 1200 need a gateway set, which I'll admit I never checked. The tunnel's green and I can't even ping the Cosy's own LAN address, which I can't explain at all, so any thoughts on where that traffic ends up?
Before the firmware. What's the IP range of the network your laptop is on right now, home or office? ipconfig, the adapter with the default gateway. And does eCatcher throw a warning when you connect, a yellow one about the LAN?
Working from home today. Laptop is 192.168.1.23, gateway 192.168.1.1, the ISP router. eCatcher does show a yellow thing when it connects, I've been closing it. Something about an IP conflict. I'll read it properly next time.
Read the yellow one before the firmware. Your home network and the machine LAN are both 192.168.1.0 removed link Ping 192.168.1.10 and the laptop checks its routing table, sees that range on the wifi and sends it to your living room. It never enters the tunnel. The Cosy shows online because the tunnel doesn't care what you route into it.
Move your home router to 192.168.50.x or anything not 192.168.1.x. There's also a NAT option on the Cosy so the machine side appears on a different range, but I've never set it up, read the Talk2M note first.
Someone did a decent article on the remote access side: https://plctr.com/remote-monitoring-and-control-of-plc-systems/
Home router's on 192.168.50.x now. Ping to the Cosy at 192.168.1.250 answers. Ping to the 1200 at 192.168.1.10 still times out and TIA still can't see it, so its one step further and no luck on the CPU.
Pretty sure it's the gateway you mentioned now. Your laptop arrives through the tunnel from a 10.x address, the CPU gets the ping, and has no router to send the reply back through. Device configuration, PROFINET interface, Ethernet addresses, tick Use router, 192.168.1.250. You'll need someone on site to download it, or a local laptop.
Site guy plugged in and set Use router to 192.168.1.250 off my instructions, downloaded it. Ping answers, TIA goes online through the tunnel, support job done.
So it was two things stacked and both of them mine. My home LAN was 192.168.1.x, same as the machine, so the ping never went into the tunnel at all. Moving the home router to 192.168.50.x sorted that, and then the CPU had no gateway to reply through until Use router was ticked and pointed at the Cosy.
Machine LAN range and the router tick are on the shipping checklist now. I still can't explain why the ping to the Cosy itself failed before the subnet change if the tunnel was up. Same reason I guess.
Thanks wandak, petek.
192.168.1.x on both ends. Half the remote tickets I get.