BobVel

Members
  • Content Count

    2
  • Joined

  • Last visited

  • Days Won

    1

BobVel last won the day on June 14 2018

BobVel had the most liked content!

Community Reputation

1 Neutral

About BobVel

  • Rank
    Newbie
  1. Here's the real deal. There is a device detection issue with the 2730h build in which the application thinks the device is an NDIS ("LAN") device. With the build and firmware previous to 2730h, the device was indeed in "LAN" mode so there were no issues connecting. Since you upgraded the device to WinMB, the build sometimes thinks the device is in "LAN" mode (ROOT CAUSE) so it uses a certain set of functions to establish the connection. Obviously, these commands are incorrect so you reach said errors. As a quick workaround, you can either re-run the application or hit the "Detect Device" button. At these points, the application correctly identifies the device as a WinMB device and uses the correct set of functions to establish the connection. A more permanant solution is to actually set the device to back to LAN mode. Once in LAN mode, the application does not confuse the device mode and all your problems go away. In order to set it to LAN mode, use the link that had previously provided. Again, there is a bug in the software but it has already been addressed in the next release. Link to set device to LAN mode.http://www.vzam.net/uploadedFiles/UML290%20VPN%20Connection%20Issues%20-%20Read%20Me.zip
  2. Please hit "detect device" to get it to work. Or, set it to "LAN" mode.