Steve Krause Posted January 27, 2012 Report Share Posted January 27, 2012 Upgraded to the latest version of VZAccess Manager yesterday, which I use with my Verizon 4G LTE Dongle. After the upgrade, each time I try to connect I get an Error Code 2101, and it won't connect. Is anyone having the same issue? Does anyone have a fix? I'm still crawling all the Verizon support sites and forums, and so far nothing... I'm running the following VZ Access Manager Client: VZ Access Manager Version 7.7.1.5 (2730h) Consumer Release. Quote Link to comment Share on other sites More sharing options...
Steve Krause Posted February 4, 2012 Author Report Share Posted February 4, 2012 Quote Upgraded to the latest version of VZAccess Manager yesterday which I use with my Verizon 4G LTE Dongle. After the upgrade, each time I try to connect I get an Error Code 2101 and it won't connect. Anyone having the same issue? Anyone have a fix? I'm still crawling all the Verizon support sites and forums and so far nothing... I'm running the following VZ Access Manager Client: VZ Access Manager Version 7.7.1.5 (2730h) Consumer Release. No fix yet however I've found if I close the VZ Access Manager Client and re-open, usually I can get a connection made. <sigh> Quote Link to comment Share on other sites More sharing options...
Larry Posted February 13, 2012 Report Share Posted February 13, 2012 Yeap, I am too. Verizon was no help. They said it was just signal in the area they were trying to use the device. Not so! It worked fine prior to the upgrade.Definitely looking for a resolution. I am not sure if we can roll back the upgrade. Quote Link to comment Share on other sites More sharing options...
Larry Posted February 13, 2012 Report Share Posted February 13, 2012 Yeap, I am too. Verizon was no help. They said it was just signal in the area they were trying to use the device. Not so! It worked fine prior to the upgrade.Definitely looking for a resolution. I am not sure if we can roll back the upgrade. OK, I have the word (IE: admission!?) from Verizon. The firmware upgrade definitely causes this issue. We connected another new UML290 that did not have the firmware upgrade. Upon launching vzaccess manager, the firmware upgrade notice came up, of course. If you say no to the upgrade, vzaccess manager closes. They are sending a newer device free. Until there is a firmware upgrade for the failed firmware upgrade, our UML290 is out of action. Quote Link to comment Share on other sites More sharing options...
Abe Posted February 14, 2012 Report Share Posted February 14, 2012 Upgraded to the latest version of VZAccess Manager yesterday which I use with my Verizon 4G LTE Dongle. After the upgrade, each time I try to connect I get an Error Code 2101 and it won't connect. Anyone having the same issue? Anyone have a fix? I'm still crawling all the Verizon support sites and forums and so far nothing... I'm running the following VZ Access Manager Client: VZ Access Manager Version 7.7.1.5 (2730h) Consumer Release. My UML 290 works great via my Cradlepoint router. But I'm getting the 2101 and 2107 when connected directly to my Win7 notebook. Weird. Quote Link to comment Share on other sites More sharing options...
Larry Posted February 14, 2012 Report Share Posted February 14, 2012 As it turns out, the error most encountered is 2101. The 2107 was a misspell by an end user. Verizon is sending replacement devices to us. It appears once the firmware upgrade is accepted the trouble begins. All of our computers using the UML290 are Win7. The error, just to be clear, occurs when using the Verizon wireless network, not wifi.Just to keep it interesting, now one of our users with the same card is getting Error WMC100. Same result, it cannot connect to the Verizon wireless network. 1 Quote Link to comment Share on other sites More sharing options...
Abe2 Posted February 14, 2012 Report Share Posted February 14, 2012 I believe I have this issue resolved. The problem is with the VZ Access Manager software. Take a look at this read me: Download and run the program as described. Quote Link to comment Share on other sites More sharing options...
Steve Krause Posted February 15, 2012 Author Report Share Posted February 15, 2012 As it turns out, the error most encountered is 2101. The 2107 was a misspell by an end user. Verizon is sending replacement devices to us. It appears once the firmware upgrade is accepted the trouble begins. All of our computers using the UML290 are Win7. The error, just to be clear, occurs when using the Verizon wireless network, not wifi.Just to keep it interesting, now one of our users with the same card is getting Error WMC100. Same result, it cannot connect to the Verizon wireless network. Yeah that's not fun..... Lots of issues on this one. Quote Link to comment Share on other sites More sharing options...
Steve Krause Posted February 15, 2012 Author Report Share Posted February 15, 2012 I believe I have this issue resolved. The problem is with the VZ Access Manager software. Take a look at this read me: http://www.vzam.net/download/download.aspx?productid=921 Download and run the program as described. That's the REV I'm already using. I'm running VZ Access Manager Version 7.7.1.5 (2730h) Consumer Release. I got this from clicking HELP -> About VZ Access Manager. Quote Link to comment Share on other sites More sharing options...
rushpet808 Posted February 28, 2012 Report Share Posted February 28, 2012 Upgraded to the latest version of VZAccess Manager yesterday which I use with my Verizon 4G LTE Dongle. After the upgrade, each time I try to connect I get an Error Code 2101 and it won't connect. Anyone having the same issue? Anyone have a fix? I'm still crawling all the Verizon support sites and forums and so far nothing... I'm running the following VZ Access Manager Client: VZ Access Manager Version 7.7.1.5 (2730h) Consumer Release. Do you know witch one of the two i used for Windows 7 professional? Im getting 2101 and 2107 with both... Pantech UML290 7.7.1 (2730h) 3 OR 7.7.1 (2730h) 3 Vista SP2 http://www.vzam.net/download/supported.aspx Quote Link to comment Share on other sites More sharing options...
rushpet808 Posted February 28, 2012 Report Share Posted February 28, 2012 Do you guys know witch one of the two software do i use if im using Windows 7 pro? http://www.vzam.net/download/supported.aspx Quote Link to comment Share on other sites More sharing options...
Steve Krause Posted March 1, 2012 Author Report Share Posted March 1, 2012 As it turns out, the error most encountered is 2101. The 2107 was a misspell by an end user. Verizon is sending replacement devices to us. It appears once the firmware upgrade is accepted the trouble begins. All of our computers using the UML290 are Win7. The error, just to be clear, occurs when using the Verizon wireless network, not wifi.Just to keep it interesting, now one of our users with the same card is getting Error WMC100. Same result, it cannot connect to the Verizon wireless network. Hey can you confirm @Larry that verizon is actually sending you a new device? I'm still having issues daily with this one. Quote Link to comment Share on other sites More sharing options...
Steve Krause Posted March 1, 2012 Author Report Share Posted March 1, 2012 Upgraded to the latest version of VZAccess Manager yesterday which I use with my Verizon 4G LTE Dongle. After the upgrade, each time I try to connect I get an Error Code 2101 and it won't connect. Anyone having the same issue? Anyone have a fix? I'm still crawling all the Verizon support sites and forums and so far nothing... I'm running the following VZ Access Manager Client: VZ Access Manager Version 7.7.1.5 (2730h) Consumer Release. @rushpet808 I'm pretty sure you want to download this client for Windows 7 Pro. - http://www.vzam.net/download/download.aspx?productid=921 Quote Link to comment Share on other sites More sharing options...
Philippe Heller Posted March 8, 2012 Report Share Posted March 8, 2012 There is a work around. It is on the vzam.net website. When you go to download the access manager for windows 7, it has a link for a .pdf file which explains how to set up the device as a LAN device, bypassing the Windows issue. http://www.vzam.net/uploadedFiles/UML290%20VPN%20Connection%20Issues%20-%20Read%20Me.zip It worked for me. 1 Quote Link to comment Share on other sites More sharing options...
kissassy Posted March 9, 2012 Report Share Posted March 9, 2012 If you receive an error 2107 please go to vzam.net and hit Download Now. Go to the link below where it has the Read Me and click on it. Open that and open the Application. When you run the application, Click Checking Device. Then the next button will be available to click, Set to Lan Mode. Click. It will run for a bit and then tell you it was Successfully updated. Try to connect again in VZ Access manager. Should work, did for me! Quote Link to comment Share on other sites More sharing options...
Steve Krause Posted March 16, 2012 Author Report Share Posted March 16, 2012 If you receive an error 2107 please go to vzam.net and hit Download Now. Go to the link below where it has the Read Me and click on it. Open that and open the Application. When you run the application, Click Checking Device. Then the next button will be available to click, Set to Lan Mode. Click. It will run for a bit and then tell you it was Successfully updated. Try to connect again in VZ Access manager. Should work, did for me! Great tip @kissassy will give that a shot today. Quote Link to comment Share on other sites More sharing options...
Karen Ripple Posted April 13, 2012 Report Share Posted April 13, 2012 April 13th and I'm fighting this same battle with a newly delivered UML290 using VZ Access Manager Version 7.7.1.5 (2730h). Tech Support is oblivious to the problem still. The work around described looks promising, and I'll give it a try. Quote Link to comment Share on other sites More sharing options...
Pukka1 Posted April 26, 2012 Report Share Posted April 26, 2012 One of the posters above is incorrect. Error 2107 is not a typo. I have been getting both error 2101 and 2107 with my Pantech UML290 running the most current version and on the Win 7 platform. Verizon has been hit and miss with their response. They have done the uninstall-reinstall route multiple times, swapped out my Pantech 3 times and the problem still occurs. I have downloaded patches that they have suggested and I am still not happy. Quote Link to comment Share on other sites More sharing options...
BobVel Posted May 25, 2012 Report Share Posted May 25, 2012 April 13th and I'm fighting this same battle with a newly delivered UML290 using VZ Access Manager Version 7.7.1.5 (2730h). Tech Support is oblivious to the problem still. The work around described looks promising, and I'll give it a try. Please hit "detect device" to get it to work. Or, set it to "LAN" mode. Quote Link to comment Share on other sites More sharing options...
BobVel Posted May 25, 2012 Report Share Posted May 25, 2012 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 1 Quote Link to comment Share on other sites More sharing options...
Steve Krause Posted July 2, 2012 Author Report Share Posted July 2, 2012 Upgraded to the latest version of VZAccess Manager yesterday which I use with my Verizon 4G LTE Dongle. After the upgrade, each time I try to connect I get an Error Code 2101 and it won't connect. Anyone having the same issue? Anyone have a fix? I'm still crawling all the Verizon support sites and forums and so far nothing... I'm running the following VZ Access Manager Client: VZ Access Manager Version 7.7.1.5 (2730h) Consumer Release. Verizon just posted a new version upgrade for my VZAccess Manager. I'm now running version: 7.7.7.0 (2767c) and so far, no issues with Error code 2101 or 2107. When it updated it might also have updated my USB Pantech UML290 also. It's now running Firmware: L0290VWBB12F.248. Hardware Version REV_03. Is anyone fixed with this last update? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.