eNSP common 40 error solution

Reference solution for 40 error reporting when starting eNSP AR routing

For some eNSP's own software, it depends on many other software, so some common bugs cannot be avoided. This time, I will share the solutions for device registration failure and AR routing startup 40 error report.

AR40 error: some common solutions integrated in CSDN

The first is the router problem. In some abnormal situations, AR error 40 will appear. Most people will solve this problem according to the official website, but some people will delete the VBox, and the VBox is not deleted cleanly, or the deletion is wrong, resulting in VirtualBox Host-Only Network becomes VirtualBox Host-Only Network #2, #3. In this case, you are probably cold at this time , first: you can no longer find the virtual network card of VirtualBox  Host-Only  Network  , and you can’t find it from hidden devices, so give up struggling unless you can find this Delete the virtual network card, then delete VBox and download VBox again (of course, you must ensure that you will delete VBox cleanly, including the contents in the registry), this is the first solution, of course I can’t achieve it, The only one is with the help of Notepad++

This is relatively simple, and I feel quite reliable in my tests.

The first is to delete the original version of eNSP and Orcle VM VirtualBox to completely delete this software, you can download the version of Virtualbox5.2.28, this software and eNSP are packaged and put into Baidu network disk, the link is https://pan.baidu.com/s /13EjhQDjUbwalrRDJNlXGDA extraction code: f27f, the operation is relatively simple

The failure to register the device should be due to the fact that the Virtual version is different from eNSP, which is not supported!

Guess you like

Origin blog.csdn.net/m0_53367084/article/details/116106134