Please excuse me if I am posting this in an inappropriate thread.
I was curious as to whether or not anyone has come up with a work around for the block that third party software is experiencing. Specifically, under ERALink32 the product in question would utilize a telnet session to convey information from the software into the Reynolds system.
Is the issue just that the since the software uses a telnet emulator it would not to use an SSH connection instead? Is it a combination of Telnet-vs-SSH connectivity -AND- the address (IP?) for which it is connecting to? Otherwise, is this a moot point since these upgrades have shut out 100% of all third part software solutions?
So I'm curious, how have dealerships dealt with a workaround for software packages that have been blocked by ERAccess that once worked flawlessly under ERALink?
I was curious as to whether or not anyone has come up with a work around for the block that third party software is experiencing. Specifically, under ERALink32 the product in question would utilize a telnet session to convey information from the software into the Reynolds system.
Is the issue just that the since the software uses a telnet emulator it would not to use an SSH connection instead? Is it a combination of Telnet-vs-SSH connectivity -AND- the address (IP?) for which it is connecting to? Otherwise, is this a moot point since these upgrades have shut out 100% of all third part software solutions?
So I'm curious, how have dealerships dealt with a workaround for software packages that have been blocked by ERAccess that once worked flawlessly under ERALink?