Problems with Verizon's VZAccess Manager running under Leopard

When I had 10.4.x installed, I used Apple's native WWAN support for my v740 from Verizon, without any problems. After upgrading to Leopard, it no longer works. Patched up to 10.5.1, check for other updates. The WWAN patch from February is only for Tiger and won't run in Leopard.

I'm going to download VZacess, but I am afraid I'll have the same problems you are having. I'd rather use Mac native card support, but their is of course no info at all on the support site. Wish us luck, and if any fanboys would like to chime in and help, that'd be great.

I have Verizon Wireless' VZAcess Manager running on my MacBook Pro (Core2 Duo 2.4Ghz, w/ 4Gig RAM), and have notice absolutely no issues running under Leopard. I did not do a clean install when I upgraded, and have noticed absolutely no issues with VZAccess.

Don't know if this helps, but hopefully it will let you know that it does work on other similar setups without any issues.

I have never tried it with my MacPro, because it is connected to a cable modem for high-speed internet access.

I am having a different problem with VZ Access Manager. FYI: I already had my v740 card working with Tiger on my 15" MacBook Pro and I was using VZ Access Manager because I would get an error with Apple's built-in WWAN utility.

When I upgraded to Leopard, I actually did a full, clean install and not an upgrade. I installed the latest version of VZ AM and now I get the "913" Error every time I try to connect (this happens at the "Registering with Network" portion of connecting). I spent 45 mins on the phone with Verizon and a very helpful young lady but no luck...I did find out that the "913" Error is a very generic error meaning a connection problem (doh!)

Any one have any ideas? I'm paying 70+ a month for this service I can't use and having to cough up $9.95 in hotels each night...I'd really like to get this working short of going back to Tiger.

Thanks all.
KD

The 913 error is not related to the drivers or OS compatibility - it means that your aircard is not connecting to the tower signal.

The Verizon support person should have reset your card's registration and then led you through the process of re-Activating the card. You can try it from the VZ Manager's Options menu, but you will probably need Verizon's inside help to clear the old data.

HTH

I'm using the VZAccess Manager v3.7 on Leopard with no problems. I am also using a PCMICA Verizon card with an ExpressCard34 adapter.

I just installed it and it still does not work for me. The setup program says it finds the device but when the manager application is ran, it is not shown. And just like on 10.4.10, the un-install feature does not work and I had to manually rip it out of my system.

Good luck to all who try to use it.

paul

I should have included a little more information but I was trying to keep my post down to novelette size. Here goes the new stuff:

When I said I was using the latest version, it was 3.7, the new version that Verizon just released. This version still gives me the 913 error.

As far as working with Verizon to re-activate my card, we did that twice in the support call. We would un-install the software, install it, re-activate the card and the card would properly activate. But when I try to connect, "913" error every time.

Any more ideas? Is there possible that my original version of VZ AM left some file on my system that is causing me problems (I'm only 3 months into my coversion to the Mac)? I appreciate everyone's posts.
KD

KD,

Spent some quality time with Verizon support just yesterday fighting this issue. I got bumped to their second tier group because I was on a Mac and actually got a person who was quite helpful. She ended up "resetting my card on their network" and that is what did the trick. I didn't let her hang up until I connected, rebooted, and re-connected.

Doubt that the old version of VZAM is hurting you as I was getting the same error despite never having it on my machine.

Good luck...

Have installed VZAccess Manager 3.7.0 and my curser is still freezing intermittently. I use a USB720 modem and Mozilla Foxfire 2.0.0.9. Any more suggestions?

I am having the same exact problem, where you able to resolve it? Any help would be appreciated? Please and thank you.

Just went through similar situation today the first time I tried to use my USB720 - routed to a Level 3 support technician.

She pointed out that the automatic update feature for VZAccess does not work reliably, and that upgrades need to be manually done from the web site, vzam.net. I tried updating as my first step, and it went through the motions. Turns out my version was 6 months older.

Unfortunately for me, when I try to download the file on my Mac, after much anticipation, I get a 404 error.

If anyone is willing to share the update file for a USB720, I'd appreciate it.

Not relishing the idea of spending time on the train without it. I might have to read a book or look at the scenery. (shudder)

Finally solved the "freezing cursor" problem:
Downloaded VZAccess Manager updates 3.7.0, then 3.10.0 from vzam.net website. Both downloaded successfully, but did not solve the cursor problem for me.

I decided it was time to call Verizon tech support. She told me that still a newer version is available, 3.12.0. I downloaded that from the vzam.net site, again successfully. But when I went to try it out, the USB 720 modem would not connect. Called tech support again, got a person who tried to be very helpful but could not solve the problem. Sadly, he did not have anyone to refer me to, as he was the person with the most Mac knowledge! While waiting for this tech support person to call me back for a three way discussion with Apple Care, I reread all the responses from this discussion group, put it all together and found my answer by myself. I tried Hawkeye's (Jan 31) suggestion to reactivate the card (VZAccess menu: options, then activation) and that worked!

Tech support confirmed that a 913 error message indicates that the aircard is not connecting to the tower signal.
Reactivating the card worked to reconnect from the 913 error message.
3.12.0 finally solved the cursor problem (so far).

By the time tech support called back, I gave him the solution!

Thank you everyone for the support!