Cosy 141 vs Cosy 131
We ship eWON Cosy with our machines for remote access/troubleshooting purposes. This particular customer has a few machines with eWONs on them. They were originally shipped with the old-style Cosy 141. WAN ports set up as DHCP. They all work - no problem. Then, one of them "died" and I tried to replace with a Cosy 131 (as 141s now obsolete). WAN port set up the same (DHCP). This Cosy worked fine here when I set it up. When installed in customer's machine, the Cosy would never come online (T2M light never lit). We had to "borrow" a 141 from one of the other machines and plug it into the same internet cable that didn't work with the 131 and it works fine. So what is the difference - or rather, what needs to change on the 131 to have it come online? (i.e. T2M light ON and eCatcher show the Cosy 131 as "Online"?). Our service tech went so far as to bring the 131 back to me and I plugged it into our internet connection and it came online, no problem. Why will 141 come online and 131 won't @ customer's location?
-
Hello
the Cosy would never come online (T2M light never lit)
What happens when the customer tried to do the T2M VPN wizard did it finish successfully?0 -
We typically don't run through the setup at our customer's plants. We set up the Cosy "in-house"; and set it up for DHCP. When we ship to the customer, typically, they just plug it in and it works. That's how we set up the 141s previously, and that's how we set up the 131s as well. We never had problems setting up the 141s in-house; but when we switched to the 131s, then we had problems with the T2M VPN wizard. There was some back and forth between our I-T dept & eWON as to which side is to "blame". Not sure what came out of it, other than now when we run the 131s through the wizard, we first have to set it up with a specific static IP address on our network for the WAN. Once the VPN wizard completes, then we go back and set the IP address for DHCP. Never had any problems with the 141s. So, evidently, there is something different with the 131s and I'm guessing this has something to do with our current problem.
0 -
Hello
Since I have never used 141, I am not sure regarding that, but regarding the 131 if the T2M led is off, it should be either the T2M wizard did not finish successfully, or the customer might not have access to the VPN servers? Ewon Technical Support - Talk2m VPN Servers
What happens if the customer runs the connection checker -> Talk2m Connection Checker (ewon.biz)0 -
I will suggest that and see what happens.
0 -
But on second thought - with "borrowing" a 141 from a different machine - mounting it next to the 131 - and then just move the ethernet/internet cable from the 131 to the 141 and it connects to the VPN servers without problem - I don't believe the connection checker is going to tell us anything. Do you agree?
0 -
Yes, that was my initial thoughts as well but as I said I have no idea regarding 141(if it has the same working principle on the VPN access), I thought giving a try for what I know from 131 and see what outcome it gives.
You can also check if the @Led is also turned off or is it on?
What firmware is the customer on? can he try to update the firmware if it is an old one? Ewon Software Download | Ewon Technical Support0 -
The 131 and 141 will have some differences, like default settings, the access server used, etc. due to the firmware not being updated since 11.3 for the 141 (when it went obsolete). The best place to check for differences would be the Firmware Release Notes since 11.3.
0
Please sign in to leave a comment.
Comments
7 comments