I support quite a few people who use USB 3G dongles; many have moved to Snow Leopard, where some have been having problems. None of these people are having problems with Vodaphone, as they support the Mac very well, and have up-to-date 64-bit drivers. We were having some troubles with ZTE 622 3G dongles on Snow Leopard, and here's one possible fix. I had a brain wave for these modems, though, as I support other clients on mobile broadband. I noticed that Vodaphone has a driver for ZTE products as part of their mobile connect suite (64-bit as well).

So I downloaded and installed as a test. Rather than using the troublesome ZTE Connect, I used the Network System Preferences panel, added the ZTE modem port, and used *99# as number. Sbornik zadachi po atomnoj i yadernoj fizike irodov reshebnik.

Presto, a stable connection on 3G with no annoying pop-up saying the driver extension is incompatible or not installed correctly, etc. Always make sure you disconnect from 3G before unplugging the modem, as you can otherwise cause a kernel panic.

ZTE MF100 Drivers Download. Tech Tip: If you are having trouble deciding which is the right driver, try the Driver Update Utility for ZTE MF100. It is a software utility that will find the right driver for you - automatically. Overall Rating: (77 ratings, 84 reviews). If after installing your MBRN3000 router and 3G+ USB modem, you get the. Go to and select the Downloads tab.

Very interesting post on ZTE modems within Snow Leopard. I use O2 UK with a ZTE MF100 modem and this may allow me to get rid of the poorly coded O2 Mobile Connect application. This is not completely in scope with your post, but I was wondering if you have any experience with O2 Mobile Connect at all? With O2 UK mobile broadband users have access to WiFi hotspots like BTOpenZone.

Unfortunately, the authentication for such a hotspot is handled entirely by O2 Mobile Connect, and of course only the Windows version supports that functionality leaving Mac users with no workaround. I was just curious if you had any understanding of the authentication mechanism used by the Windows Mobile Connect application - it would be great to be able to figure out a workaround for that issue as well.