Tap Adapter collision between eCatcher and SOFOS VPN
@anongfoksrhb
Customer called in regarding possible causes for a tap adapter collisions between Sofos VPN and eCatcher. I am creating a ticket to track this issues, as the customer is waiting a response for Sofos VPN regarding the tap adapter that they are using.
-
Kyle,
I wouldn't say that you can't do anything with said info. By filling John in on the root issue, he, you, and your other support colleagues can certainly pressure development to remedy a situation that is causing customer issues. Also, remedying a situation that should have never happened in the first place. Has development issued an ETA on the availability on the updated version? The fix is literally a search and replace and recompile.
"Matt
0 -
I have not received an ETA, but I will remind them again.
0 -
Thanks for the replies. I will try to add and rename, as you suggested. Depending on the installation order of Sophos and eWon, we already see one or two TAP adapters on the system. On one system we have them working both under some conditions. For the Sophos connection to work, we need to connect eCatcher first. So it seems like Sophos uses the first available TAP adapter and only works if the eWon TAP is already in use.
It is kind of disappointing that this issue still exists after such a long time. Why don't they solve it?
Kind regards,
John
0 -
Thank you.
"Matt
0 -
I have just checked with the developers and they are looking at a fix for this for the fall release of eCatcher. I can't speak for Sophos.
0 -
I know the topic is over an year old, but the problem is still not solved. After a clean install of one of out PCs there is a conflict between ecatcher and sophos (basically almost anything, based on OpenVPN). If I install the ecatcher tap adapter - it overwrites the sophos's one and vice versa. Years ago I managed somehow to make the both programs live on the same PC, but I cannot remember how.
But, if you sell a device for 700+ Euro (which, I think is based mainly on open source software) you should at least take the effort to make it right! FYI there are competitors in east Europe, which sell similar routers for a fraction of the price and they work pretty well (personal experience, ewon was my boss's choice)!!!0 -
Dimirov,
Yes, we still have this issue. It is a shame that even after showing Ewon exactly what the issue is and how to fix it, they won't do anything.
"Matt
0 -
Obviously, HMS is just another company that gives no support to their customers. COVID-19 will be blaimed, I guess.
0 -
Hello,
We have been discussing this with our R&D team and while I was hoping to have a release data before posting we do not have one yet. They are still looking into a fix but they have not been able to guarantee a date.
Until a release is made with a fix we still have our workaround available. This adds a second tap adapter and rename it. This can be done after install. You might need to install both sophos and ecather before running this fix. This script is available in the installation driver folder Talk2mVpnService > driver with the file called install.bat . The script will will add an adapter then rename it for ecathcer. The folder link should look something like C:\Program Files (x86)\eCatcher-Talk2M\Talk2mVpnService\drivers
Once in this directory right click on install.bat and select run as administrator. If this still gives you issues, possibly renaming the current adapter, you can run the addtap.bat script to add a adapter without renaming it then navigate to you network connections in control panel and rename the adapter to manually to "Talk2m-eCatcher".Best regards,
Deryck0 -
Thank you, Deryck! The install.bat solved it for us (we are using Pritunl VPN client, not Sophos).
0 -
Hello
Thank you for updating us that this solution worked for you. I am glad it was able to resolve with your VPN software.
0
Iniciar sesión para dejar un comentario.
Comentarios
41 comentarios