Mobile Broadband (3 Three UK ZTE MF622) and 10.5.3

Question

Hi,
I have recently updated to 10.5.3 and now find that my 3 Mobile Broadband no longer works. All was fine under 10.5.2.
I have deinstalled the drivers and reinstalled with no joy.
I used the 3 supplied drivers from the USB modem itself (it mounts as a USB drive initially) which are revision B06 initally under 10.5.2 and these work fine creating 2 entries in Network Prefs Pane and installing an app (ZTE Mobile Connection). Launching this app and hitting connect on 10.5.2 produces a usuable broadband connection.
However under 10.5.3 the 2 network entries do not get installed and although the application runs and connects, Safari (and any other internet using app) fails as there is no route out to the net presumably because of the lack of network entries.
Needless to say I am getting nowhere with 3 customer services as although the modem supports Mac, sadly the helpdesk don't and can't assist me. They say its a Mac issue and I'm on my own.
I can find no later drivers and can only put this down to 10.5.3. I have installed the drivers on a fresh 10.5.3 Mac (e.g one that hasn't had mobile broaband on it before) and get the same issues.
I can find no reference to any issues for anyone else so I can only conclude its just me doing something wrong.
Any help/experiences greatly appreciated particularly in maybe recreating the network entries from scratch if anyone is using the same/similar combination of hardware/software as me.
Regards
NIALL8-(

Answer 1

Hi Niall,
I am running ZTE MF622 and 10.5.3 successfully on my Macbook Air.
Have you set up the network preferences pane using the ZTEUSBModem entry? Even though you should use the Three 'ZTE Mobile Connection' app to connect to the Three service, it seems the Network Preferences settings help. After setting a new location (perhaps 'Three') the network preference settings should be;
Configuration: default
Telephone Number: *99#
Note that I occasionally get a hang up on closing the ZTE Mobile Connection app. This resolves with a force quit - and I'm guessing it may improve with future firmware updates.
Regards