Wireless Joint

Posted: **Sun Jan 30, 2022 1:44 pm**

Hi everyone:

I just got a used Novatel (AT&T) usb800 modem and I'm trying to get it working on Windows 10.. I'm NOT with AT&T. I'm in Canada, on a Canadian carrier.
After inserting my sim card from my carrier, the LED on the usb800 turned green.

I understood that the modem or Windows should automatically install the drivers.
However, that's not what Device Manager appeared to show, (see below).

I had already run some driver setup program from Novatel's website. I'm not sure exactly what that's for, but I installed it. No difference.

Now, I'm confused. The Devmgr window would seem to suggest the drivers just aren't installed. Yet I get a green light on the modem.
The AT&T modem window pops up in my browser, and shows at the top this (error?) message:

No networks available. Change Network Technology to "Global" to expand network search. (Change now).

If I click on change now, it simply takes me the settings page, but there are no words like "Network Technology" or "Global" on that page.

Do they mean the roaming setting? If so, I enabled that, and it still doesn't work.

Could the modem be carrier locked to AT&T? I thought their business devices were unlocked nowadays.

What am I missing here?

Posted: **Sun Jan 30, 2022 3:27 pm**

Hmm...it appears the modem is carrier locked to AT&T. I went to their webpage to unlock it, and got an error stating the modem was returned within 14 days of purchase. Ugh. Trying to contact person who sold me the modem. BTW, the page that tells you that the modem is carrier locked is quite well hidden.

Posted: **Sun Jan 30, 2022 5:57 pm**

The only driver that self loads for novatel devices is the RNDIS or(tether) port which is loaded for your device per your screenshot, the other 2 with the yellow ! are the modem and the diagnostic (status) port, you have to manually load them.
If you want to unlock that device and att wont do it for you then you have a couple of options, you can load unlocked firmware to it or have someone do it for you or there are few places that can sell you an unlock code.

if you need it, the hardware id's for it are as follows

diag
USB\VID_1410&PID_B023&REV_0318&MI_03
USB\VID_1410&PID_B023&MI_03
===========================================
consol
USB\VID_1410&PID_B023&REV_0318&MI_0c
USB\VID_1410&PID_B023&MI_0c
==========================================
modem
USB\VID_1410&PID_B023&REV_0318&MI_02
USB\VID_1410&PID_B023&MI_02
===========================================
hid
USB\VID_1410&PID_B023&REV_0318&MI_0e
USB\VID_1410&PID_B023&MI_0e
===========================================
ndis
USB\VID_1410&PID_B023&REV_0318&MI_00
USB\VID_1410&PID_B023&MI_00
===========================================

Posted: **Sun Jan 30, 2022 11:23 pm**

Thanks Rich.

Are those all the possible Device IDs, or does each one have all of those? Newbie question, I know...but I had to ask.

Which of the two options listed can/do you provide?

Also, where do I find/how do I manually load those two drivers you mentioned?

Posted: **Mon Jan 31, 2022 9:44 am**

Hogwild wrote: ↑Sun Jan 30, 2022 11:23 pm Thanks Rich.

Are those all the possible Device IDs, or does each one have all of those? Newbie question, I know...but I had to ask.

Those are the device id's for the usb800, it is possible they can change but only if the devices mode is changed or the firmware is altered to reflect a different pid/vid

Hogwild wrote: ↑Sun Jan 30, 2022 11:23 pm Which of the two options listed can/do you provide?

I can unlock it by firmware but I do not have access to AT&T's server anymore for codes.

Hogwild wrote: ↑Sun Jan 30, 2022 11:23 pm Also, where do I find/how do I manually load those two drivers you mentioned?

Most any driver in the same class will do, you can use novatel or zte or whatever you can find but be careful not to cross device classes or you will be blue screening every time you plug it in and need to restore your pc or edit the registry to correct it so create a restore point before you go messing with it unless you know what you are doing.

Posted: **Mon Jan 31, 2022 4:14 pm**

Thanks again. So, you mean you don't have access to unlock codes?

And I assume flashing firmware would be a significant cost and/or a bit of a process?

What would be the repercussion of flashing it with other firmware? Would the little webpage interface still be available in Windows if I did that?

Posted: **Mon Jan 31, 2022 6:20 pm**

Hogwild wrote: ↑Mon Jan 31, 2022 4:14 pm Thanks again. So, you mean you don't have access to unlock codes?

No I do not

Hogwild wrote: ↑Mon Jan 31, 2022 4:14 pm And I assume flashing firmware would be a significant cost and/or a bit of a process?

Yes a code would be less money

Hogwild wrote: ↑Mon Jan 31, 2022 4:14 pm What would be the repercussion of flashing it with other firmware? Would the little webpage interface still be available in Windows if I did that?

Well, that would depend on what you load to it, normally you would only need to flash the system partition to unlock, but I suppose that depends on who made the device you are working on, some only need a simple nv edit like most zte's, yours needs an unlocked system partition loaded to it.
here are your partitions and their address's and sizes

# Start Size A0 A1 A2 F# format ------ Name------
============================================================

00 0 00000a ff 01 00 00 LNX 0:SBL

01 a 00000a ff 01 ff 00 LNX 0:MIBIB

02 14 00002c ff 01 ff 00 LNX 0:EFS2

03 40 000008 ff 01 00 00 LNX 0:TZ

04 48 000004 ff 01 00 00 LNX 0:RPM

05 4c 000008 ff 01 00 00 LNX 0:aboot

06 54 000050 ff 01 00 00 LNX 0:boot

07 a4 000002 ff 01 00 00 LNX 0:SCRUB

08 a6 000134 ff 01 00 00 LNX 0:modem

09 1da 000004 ff 01 00 00 LNX 0:misc

10 1de 000050 ff 01 00 00 LNX 0:recovery

11 22e 000004 ff 01 00 00 LNX 0:fotacookie

12 232 0005ce ff 01 00 00 LNX 0:system
============================================================
Partition Table Version: 4

and the nand registers, you will need a couple of them to reload it

* 000 NAND_FLASH_CMD = 0008000b
* 004 NAND_ADDR0 = 02810000
* 008 NAND_ADDR1 = 00000000
* 00c NAND_CHIP_SELECT = 00000000
* 010 NANDC_EXEC_CMD = 00000000
* 014 NAND_FLASH_STATUS = 00003020
* 018 NANDC_BUFFER_STATUS = 00ff0200
* 020 NAND_DEV0_CFG0 = 295409c0
* 024 NAND_DEV0_CFG1 = 08065d5d
* 028 NAND_DEV0_ECC_CFG = 42040d10
* 040 NAND_FLASH_READ_ID = 2690ac2c
* 044 NAND_FLASH_READ_STATUS = 00000000
* 048 NAND_FLASH_READ_ID2 = 00000054
* 064 FLASH_MACRO1_REG = 00000000
* 070 FLASH_XFR_STEP1 = 00000000
* 074 FLASH_XFR_STEP2 = 00000000
* 078 FLASH_XFR_STEP3 = 00000000
* 07c FLASH_XFR_STEP4 = 00000000
* 080 FLASH_XFR_STEP5 = 00000000
* 084 FLASH_XFR_STEP6 = 00000000
* 088 FLASH_XFR_STEP7 = 00000000
* 0a0 FLASH_DEV_CMD0 = 00000000
* 0a4 FLASH_DEV_CMD1 = 00000000
* 0a8 FLASH_DEV_CMD2 = 00000000
* 0ac FLASH_DEV_CMD_VLD = 00000000
* 0d0 FLASH_DEV_CMD3 = 00000000
* 0d4 FLASH_DEV_CMD4 = 00000000
* 0d8 FLASH_DEV_CMD5 = 00000000
* 0dc FLASH_DEV_CMD6 = 00000000
* 0e8 NAND_ERASED_CW_DET_CFG = 00000022
* 0ec NAND_ERASED_CW_DET_ST = 00000082
* 0f0 EBI2_ECC_BUF_CFG = 00000203
-----------------------------------------------------

Posted: **Tue Feb 01, 2022 12:57 pm**

Here's the network log, if that helps.

Code: Select all

an 1 01:18:45 (none) reboot: [REBOOT]:[notice] - {mifios_sysevent}:Will now restart
Jan 1 01:18:49 (none) ansd: [ANS]:[notice] - {mifios_sysevent}: Generating Alert Notification shutdown, title , label
Jan 1 01:18:50 (none) halt: [HALT]:[notice] - {mifios_sysevent}:Will now halt
Jan 1 01:19:12 (none) rcS: [RCS]:[notice] - {mifios_sysevent}:Finished running startup script /etc/init.d/rcS
Jan 1 01:19:13 (none) init: [INIT]:[notice] - {mifios_sysevent}:Finished run level transition N 7
Jan 1 01:19:15 (none) ansd: [ANS]:[notice] - {mifios_sysevent}: Generating Alert Notification startup, title , label
Jan 1 01:19:21 (none) init: [INIT]:[notice] - {mifios_sysevent}:Finished run level transition 7 3
Jan 1 01:19:29 (none) dmdbd: [DMDB]:[notice] - DMDBDM: {mifios_sysevent}:New IP client: mac=02:23:fg:04:86:95, ifc=USB, type=DHCP, ip=192.168.1.2, host=DESKTOP-ANSIMUS
Jan 1 01:19:46 (none) ansd: [ANS]:[notice] - {mifios_sysevent}: Generating Alert Notification roaming, title notification_roaming_title, label notification_roaming_label
Jan 1 01:19:48 (none) ansd: [ANS]:[notice] - {mifios_sysevent}: Generating Alert Notification roaming, title notification_roaming_title, label notification_roaming_label
Jan 1 01:20:26 (none) ansd: [ANS]:[notice] - {mifios_sysevent}: Generating Alert Notification noService, title notification_no_service_title, label notification_no_service_label
Jan 1 00:00:21 (none) rcS: [RCS]:[notice] - {mifios_sysevent}:Finished running startup script /etc/init.d/rcS
Jan 1 00:00:22 (none) init: [INIT]:[notice] - {mifios_sysevent}:Finished run level transition N 7
Jan 1 00:00:24 (none) ansd: [ANS]:[notice] - {mifios_sysevent}: Generating Alert Notification startup, title , label
Jan 1 00:00:30 (none) init: [INIT]:[notice] - {mifios_sysevent}:Finished run level transition 7 3
Jan 1 00:00:38 (none) dmdbd: [DMDB]:[notice] - DMDBDM: {mifios_sysevent}:New IP client: mac=02:23:fg:04:86:95, ifc=USB, type=DHCP, ip=192.168.1.2, host=DESKTOP-ANSIMUS
Jan 1 00:00:55 (none) ansd: [ANS]:[notice] - {mifios_sysevent}: Generating Alert Notification roaming, title notification_roaming_title, label notification_roaming_label
Jan 1 00:00:22 (none) rcS: [RCS]:[notice] - {mifios_sysevent}:Finished running startup script /etc/init.d/rcS
Jan 1 00:00:22 (none) init: [INIT]:[notice] - {mifios_sysevent}:Finished run level transition N 7
Jan 1 00:00:25 (none) ansd: [ANS]:[notice] - {mifios_sysevent}: Generating Alert Notification startup, title , label
Jan 1 00:00:30 (none) init: [INIT]:[notice] - {mifios_sysevent}:Finished run level transition 7 3
Jan 1 00:00:48 (none) dmdbd: [DMDB]:[notice] - DMDBDM: {mifios_sysevent}:New IP client: mac=02:23:fg:04:86:95, ifc=USB, type=DHCP, ip=192.168.1.2, host=DESKTOP-ANSIMUS
Jan 1 00:00:55 (none) ansd: [ANS]:[notice] - {mifios_sysevent}: Generating Alert Notification roaming, title notification_roaming_title, label notification_roaming_label
Jan 1 00:00:21 (none) rcS: [RCS]:[notice] - {mifios_sysevent}:Finished running startup script /etc/init.d/rcS
Jan 1 00:00:22 (none) init: [INIT]:[notice] - {mifios_sysevent}:Finished run level transition N 7
Jan 1 00:00:25 (none) ansd: [ANS]:[notice] - {mifios_sysevent}: Generating Alert Notification startup, title , label
Jan 1 00:00:29 (none) init: [INIT]:[notice] - {mifios_sysevent}:Finished run level transition 7 3
Jan 1 00:00:55 (none) ansd: [ANS]:[notice] - {mifios_sysevent}: Generating Alert Notification roaming, title notification_roaming_title, label notification_roaming_label
Jan 1 00:02:18 (none) dmdbd: [DMDB]:[notice] - DMDBDM: {mifios_sysevent}:New IP client: mac=02:23:fg:04:86:95, ifc=USB, type=DHCP, ip=192.168.1.2, host=DESKTOP-ANSIMUS
Jan 1 00:31:18 (none) dmdbd: [DMDB]:[notice] - DMDBDM: {mifios_sysevent}:Removed IP client: mac=02:23:fg:04:86:95, ifc=USB, type=DHCP, ip=192.168.1.2, host=DESKTOP-ANSIMUS
Jan 1 00:00:22 (none) rcS: [RCS]:[notice] - {mifios_sysevent}:Finished running startup script /etc/init.d/rcS
Jan 1 00:00:22 (none) init: [INIT]:[notice] - {mifios_sysevent}:Finished run level transition N 7
Jan 1 00:00:25 (none) ansd: [ANS]:[notice] - {mifios_sysevent}: Generating Alert Notification startup, title , label
Jan 1 00:00:30 (none) init: [INIT]:[notice] - {mifios_sysevent}:Finished run level transition 7 3
Jan 1 00:00:56 (none) ansd: [ANS]:[notice] - {mifios_sysevent}: Generating Alert Notification roaming, title notification_roaming_title, label notification_roaming_label
Jan 1 00:00:21 (none) rcS: [RCS]:[notice] - {mifios_sysevent}:Finished running startup script /etc/init.d/rcS
Jan 1 00:00:22 (none) init: [INIT]:[notice] - {mifios_sysevent}:Finished run level transition N 7
Jan 1 00:00:24 (none) ansd: [ANS]:[notice] - {mifios_sysevent}: Generating Alert Notification startup, title , label
Jan 1 00:00:29 (none) init: [INIT]:[notice] - {mifios_sysevent}:Finished run level transition 7 3
Jan 1 00:00:55 (none) ansd: [ANS]:[notice] - {mifios_sysevent}: Generating Alert Notification roaming, title notification_roaming_title, label notification_roaming_label
Jan 1 00:03:38 (none) dmdbd: [DMDB]:[notice] - DMDBDM: {mifios_sysevent}:New IP client: mac=02:23:fg:04:86:95, ifc=USB, type=DHCP, ip=192.168.1.2, host=DESKTOP-ANSIMUS
Jan 1 00:00:21 (none) rcS: [RCS]:[notice] - {mifios_sysevent}:Finished running startup script /etc/init.d/rcS
Jan 1 00:00:22 (none) init: [INIT]:[notice] - {mifios_sysevent}:Finished run level transition N 7
Jan 1 00:00:24 (none) ansd: [ANS]:[notice] - {mifios_sysevent}: Generating Alert Notification startup, title , label
Jan 1 00:00:29 (none) init: [INIT]:[notice] - {mifios_sysevent}:Finished run level transition 7 3
Jan 1 00:00:55 (none) ansd: [ANS]:[notice] - {mifios_sysevent}: Generating Alert Notification roaming, title notification_roaming_title, label notification_roaming_label
Jan 1 00:00:22 (none) rcS: [RCS]:[notice] - {mifios_sysevent}:Finished running startup script /etc/init.d/rcS
Jan 1 00:00:22 (none) init: [INIT]:[notice] - {mifios_sysevent}:Finished run level transition N 7
Jan 1 00:00:24 (none) ansd: [ANS]:[notice] - {mifios_sysevent}: Generating Alert Notification startup, title , label
Jan 1 00:00:29 (none) init: [INIT]:[notice] - {mifios_sysevent}:Finished run level transition 7 3
Jan 1 00:00:55 (none) ansd: [ANS]:[notice] - {mifios_sysevent}: Generating Alert Notification roaming, title notification_roaming_title, label notification_roaming_label
Jan 1 00:01:18 (none) dmdbd: [DMDB]:[notice] - DMDBDM: {mifios_sysevent}:New IP client: mac=02:23:fg:04:86:95, ifc=USB, type=DHCP, ip=192.168.1.2, host=DESKTOP-ANSIMUS
Jan 1 00:00:22 (none) rcS: [RCS]:[notice] - {mifios_sysevent}:Finished running startup script /etc/init.d/rcS
Jan 1 00:00:22 (none) init: [INIT]:[notice] - {mifios_sysevent}:Finished run level transition N 7
Jan 1 00:00:25 (none) ansd: [ANS]:[notice] - {mifios_sysevent}: Generating Alert Notification startup, title , label
Jan 1 00:00:30 (none) init: [INIT]:[notice] - {mifios_sysevent}:Finished run level transition 7 3
Jan 1 00:00:56 (none) ansd: [ANS]:[notice] - {mifios_sysevent}: Generating Alert Notification roaming, title notification_roaming_title, label notification_roaming_label
Jan 1 00:01:18 (none) dmdbd: [DMDB]:[notice] - DMDBDM: {mifios_sysevent}:New IP client: mac=02:23:fg:04:86:95, ifc=USB, type=DHCP, ip=192.168.1.2, host=DESKTOP-ANSIMUS
Jan 1 00:00:22 (none) rcS: [RCS]:[notice] - {mifios_sysevent}:Finished running startup script /etc/init.d/rcS
Jan 1 00:00:22 (none) init: [INIT]:[notice] - {mifios_sysevent}:Finished run level transition N 7
Jan 1 00:00:25 (none) ansd: [ANS]:[notice] - {mifios_sysevent}: Generating Alert Notification startup, title , label
Jan 1 00:00:30 (none) init: [INIT]:[notice] - {mifios_sysevent}:Finished run level transition 7 3
Jan 1 00:00:56 (none) ansd: [ANS]:[notice] - {mifios_sysevent}: Generating Alert Notification simNone, title notification_sim_none_title, label notification_sim_none_label
Jan 1 00:00:56 (none) ansd: [ANS]:[notice] - {mifios_sysevent}: Generating Alert Notification roaming, title notification_roaming_title, label notification_roaming_label
Jan 1 00:00:21 (none) rcS: [RCS]:[notice] - {mifios_sysevent}:Finished running startup script /etc/init.d/rcS
Jan 1 00:00:22 (none) init: [INIT]:[notice] - {mifios_sysevent}:Finished run level transition N 7
Jan 1 00:00:24 (none) ansd: [ANS]:[notice] - {mifios_sysevent}: Generating Alert Notification startup, title , label
Jan 1 00:00:29 (none) init: [INIT]:[notice] - {mifios_sysevent}:Finished run level transition 7 3
Jan 1 00:00:55 (none) ansd: [ANS]:[notice] - {mifios_sysevent}: Generating Alert Notification roaming, title notification_roaming_title, label notification_roaming_label
Jan 1 00:01:08 (none) dmdbd: [DMDB]:[notice] - DMDBDM: {mifios_sysevent}:New IP client: mac=02:23:fg:04:86:95, ifc=USB, type=DHCP, ip=192.168.1.2, host=DESKTOP-ANSIMUS
Jan 1 00:01:34 (none) reboot: [REBOOT]:[notice] - {mifios_sysevent}:Will now restart
Jan 1 00:01:37 (none) ansd: [ANS]:[notice] - {mifios_sysevent}: Generating Alert Notification shutdown, title , label
Jan 1 00:01:38 (none) halt: [HALT]:[notice] - {mifios_sysevent}:Will now halt
Jan 1 00:02:01 (none) rcS: [RCS]:[notice] - {mifios_sysevent}:Finished running startup script /etc/init.d/rcS
Jan 1 00:02:02 (none) init: [INIT]:[notice] - {mifios_sysevent}:Finished run level transition N 7
Jan 1 00:02:05 (none) ansd: [ANS]:[notice] - {mifios_sysevent}: Generating Alert Notification startup, title , label
Feb 1 15:36:21 (none) ccm2d: [CCM]:[notice] - {mifios_sysevent}:TSYNC System time set to 2022/02/01 15:36:21
Feb 1 15:36:21 (none) ccm2d: [CCM]:[notice] - {mifios_sysevent}:TSYNC CCM updated system time from NETWORK
Feb 1 15:36:24 (none) init: [INIT]:[notice] - {mifios_sysevent}:Finished run level transition 7 3
Feb 1 15:36:32 (none) dmdbd: [DMDB]:[notice] - DMDBDM: {mifios_sysevent}:New IP client: mac=02:23:fg:04:86:95, ifc=USB, type=DHCP, ip=192.168.1.2, host=DESKTOP-ANSIMUS
Feb 1 15:36:49 (none) ansd: [ANS]:[notice] - {mifios_sysevent}: Generating Alert Notification roaming, title notification_roaming_title, label notification_roaming_label
Feb 1 15:36:50 (none) ansd: [ANS]:[notice] - {mifios_sysevent}: Generating Alert Notification roaming, title notification_roaming_title, label notification_roaming_label

Posted: **Wed Feb 02, 2022 7:07 am**

Here are the drivers for it.

Posted: **Wed Feb 02, 2022 10:12 am**

Thanks again, Rich. Unfortunately, when I use Device Manager to browse locally for driver files, it either tells me that (depending on which folder I browse to) the best driver is already installed (RNDIS device), or that there are no drivers for this device in that location.

Wait, the devices.ini file in the archive you sent doesn't show any Devic IDs similar to the USB800. I believe the USB800 has Device ID ending in b023.

Oh, I see the USBCCGP Hub Setup File (nwusbecgp.inf) file has an entry for it.

Still, the drivers don't seem to want to install through Device Manager.

Any suggestions?

Posted: **Thu Feb 03, 2022 5:25 am**

You have to force the drivers, so use the hdwr-id I posted to find out which driver class you are trying to load, for instance double click on the ! driver in the dev manager and select details, then in the propertys tab select hardware ids, then look at the class

Capture2.PNG

see the highlighted part that is the code for the driver class, you can see it is MI_03 now go look at my hardwr-id's I posted for you and you will see MI_03 is the diag port so now select update driver and then select ports, then navagate to where you have the drivers and select nwfacwinusb.inf or nwusbser.inf one of those will work for the diag port, and for MI_02 (modem) select nwusbemdm.inf now your drivers are loaded.

Posted: **Thu Feb 03, 2022 12:39 pm**

I followed those instructions precisely. I copied the full path from Explorer's URL bar
and pasted it into the correct place in the Browse.... dialog box.

However, when I tried to select the exact appropriate file, I got this message.

If I just select the right folder, I get an error stating that there are no appropriate driver files
found in that folder. Huh?

BTW, for me, that file was in another folder.

Hmm...did I get the folder structure wrong when I used 7-zip to extract the archive maybe?

Posted: **Fri Feb 04, 2022 10:42 am**

You must be using windows 10 o 11 I assume, those 2 os's have driver recognition problems constantly.
Maybe I can find time to pack them into an installer for you but I am far busy today

Posted: **Sat Feb 05, 2022 12:20 am**

rich:

Yes. I came to the conclusion today that maybe the drivers you posted didn't include support for Windows 10. Can you check (even if you don't provide the right ones)?

I don't want to continue on something if it's a wild goose chase.

When you talked about Win10 and driver problems, did you mean with this stick or just in general? Because I've been using Win10 since 2016 and haven't had a driver problem yet that appeared to be caused by Windows.

Thanks.

Posted: **Sat Feb 05, 2022 8:30 am**

You can use most any driver for that stick, the correct class of course, and I meant windows, the first thing a guy should do is disable driver signing check and put your os into test mode, that will help to alleviate some of the driver issues. Windows 7 was a fantastic os for developers as far as windows goes since it they have been trying to make windows 7 out of the new os's since their failures of 8 and 8.1.

Posted: **Sat Feb 05, 2022 9:15 am**

Rich Hathaway wrote: ↑Sat Feb 05, 2022 8:30 am Windows 7 was a fantastic os for developers as far as windows goes ....

I ran Windows 7 on my PC's until they were no longer supported, then reluctantly upgraded my work machines to Windows 10.

I do have a Windows 7 machine that is used strictly for flashing modems, tftp projects, and other tasks that Windows 10 does not like--or tries to manage and take control over. Have not tested Windows 11 yet.

Posted: **Sat Feb 05, 2022 1:38 pm**

You won't tell much difference in 10 AND 11, it's the same problematic junk your use to with win 10.
We have about 30 stations we use to load devices for our commercial jobs when we have them, all are win 7 with only a few exceptions that are win 8 and it only because a few Nokia programs I have written will only run on win 8 because of their Nokia dependency files I had to use.
Linux is king but custom tools don't sell very well without GUI so can't get rid of windows just yet.
Sorry, guess I kinda just hijacked this thread sorry to the O.P.

Posted: **Sat Feb 05, 2022 1:46 pm**

Here to the O.P. here, the correct drivers packed into a nice factory installer for you.

USB800_ALL_Drivers.rar

Posted: **Mon Feb 07, 2022 12:02 am**

Thanks Rich!
I'll try it as soon as I can.

Posted: **Wed Feb 16, 2022 6:45 pm**

I finally figured out that the device was carrier locked to AT&T. The Seller gave me an unlock code that worked. Now the web interface shows all screens. Novatel told me that I don't need to install drivers for the other devices at all if I just want to use the dongle in host mode.

However, I'm still not getting an IP address.

I believe this may be a cellular provider problem, so I'll call them as soon as I have time. You know that the call queues are like lately during Covid.

Posted: **Sun Apr 10, 2022 1:17 pm**

Okay, I'm back to trying to get this working again.

Here's the entry that keeps repeating in the log:
{mifios_wanevent}: Internet IPv4 call failed, handle:0 end_reason:1, verbose end_reason:208!!

And here's a screenshot of the Internet status:

Screenshot 2022-04-10 at 14-15-00 USB800.png

It appears maybe it's not getting an IP address?

Posted: **Sat Apr 23, 2022 7:33 pm**

SOLVED, mostly. I finally got this working. I did updates to the latest firmware
and software. I changed International Roaming to OFF. And now it works...
mostly.

The interface still shows 0.0.0.0 as the IP address. Data sent/received is
wildly inaccurate.

And most of all, I can't ping IP addresses on the Internet. I really dont' understand
what causes this last thing, when I can browse and do any type of application-level
activity I want.

Does anyone have any ideas?

Posted: **Sat Apr 23, 2022 8:46 pm**

Solved. (Mostly)

I'm not sure if it was the firmware/software update I did on this modem, or actions the carrier took. Since I was using the SIM card from my phone, Inseego told me to ask the carrier to reset the network settings, deactivate the SIM card on their network and reactivate it. They thought maybe my carrier network wouldn't allow a third device on the same SIM card, since that SIM had already been used on 1) my phone, and 2) my USB730L dongle.

However, by that point, I'd already updated the modem's software/firmware, as described below.

I believe it's the carrier actions above that fixed the problem.

FIRMWARE/SOFTWARE UPDATE
As with my other dongle, Inseego support sent me the latest update via email. Then you just go to the dongle's IP address for locatl updates (usually 192.168.1.1) in your web browser:

e.g.
192.168.1.1/sideload

That takes you to webpage where you can manually update firmware/software using a file Inseego will give you.

NOTE: For some reason, this USB800 took about 8 or 9 tries to get the update to work. The first time I got an error. The second time, nothing changed, and it kept taking me back to the same webpage. But eventually, on maybe the 9th try, the update worked. So, unlike with my USB730L, this one was stubborn, but it finally worked.

There are several downsides. First, the AT&T web interface still shows the WAN IP address as 0.0.0.0 . Second, The Internet sessions, are listed 0 hours/minutes/seconds. And finally, if I go to a command prompt and ping a host on the Internet, I get the error "request timed out".

Can anyone explain this?

Posted: **Sun Apr 24, 2022 9:36 am**

Check to see if you have manual DNS ticked in the UI it should be off, if u try that sim in another device do you get an ip, I have a couple that do that on vzw I call them ghosted sims, they never need any payment made they have been on for a couple years.

Posted: **Sun Apr 24, 2022 11:56 am**

I can't find any setting for DNS anywhere in AT&T's web interface. Am I missing it?

I can't remember if it showed an IP on my USB730L that I wrote about in my other thread here. I'd consider trying it, but then I may mess up the fact that the SIM is (mostly) working in this device cause I haven't used it in more than two devices (as per carrier advice above).

I recently installed Wireshark on this machine to learn some basics of how it works. Would a packet trace help figure things out?

Posted: **Sun Apr 24, 2022 2:06 pm**

dmesg it, that should tell what you need to know, there is IP control in the UI for the 730 stick, the 800 must have it in either a hidden menu or desktop app.
You can use this tool to dmesg it, I posted it in this forum somewhere a while back but can't remember where, it works thru the android port so make sure the driver is loaded and working for that port or this tool will fail.

dmesg tool.rar

Posted: **Sun Apr 24, 2022 3:08 pm**

I'm trying that, but getting "device not found" error from adb. Windows is recognizing the device just fine. I'm assuming the SIM card does not need to be installed while doing this, correct? Can this be fixed easily?

If not, I could run a command or two from a bootable Linux USB flash drive I have.

Posted: **Sun Apr 24, 2022 4:28 pm**

Look in your device manager for the adb port with a yellow ! but you have to have the diagnostic mode enabled first or the device will not give the port, do you know if you have enabled diag mode on it yet?
The hdwr id for it is
adb
USB\VID_1410&PID_B023&REV_0318&MI_04
USB\VID_1410&PID_B023&MI_04

Posted: **Sun Apr 24, 2022 6:36 pm**

In Device Manager, I have

First Yellow exclamation mark:
USB\VID_1410&PID_B023&REV_0318&MI_02
USB\VID_1410&PID_B023&MI_02

Second yellow exclamation mark:
USB\VID_1410&PID_B023&REV_0318&MI_03
USB\VID_1410&PID_B023&MI_03

In one of the hidden web interface pages, you can choose from End User mode, Debug Mode or Enterprise mode. Did you mean Debug mode?
Or did you mean you want it to expose the AT command interface?

If I change modes, is it simple to switch the mode back to whatever it is now?

Posted: **Mon Apr 25, 2022 7:36 am**

Yes that one is the lab test mode menu, u need to select debug, but there is another hidden menu as well, I cannot remember what the address is for it

Posted: **Mon Apr 25, 2022 9:09 am**

So wait, I'm confused. Do I just need to type "adb USB\VID_1410&PID_B023&REV_0318&MI_03" ?

and then it will let me run dmesg?

Or are you saying I need to do that on both sets of IDs I listed?

Posted: **Fri Apr 29, 2022 3:03 pm**

you don't need to type anything, you need to load the ADB driver, that hdwr id is so you can know which device you need to load it for, look in your device manager, depending on your pc config it will likely say inseego or usb800 or maybe android, then you can check the device id and match it up so you know that you are not trying to load the android driver for the modem or serial port and making your pc bluescreen every time you plug it in.

Posted: **Fri Apr 29, 2022 4:47 pm**

Can you be more specific? I have no idea what you mean by "load ADB driver". It's installed, but if you mean something else, then maybe spell it out for me.

E:\>adb devices -l
List of devices attached
0123456789ABCDEF device

E:\dmesg tool>"run this script"

E:\dmesg tool>adb shell su -c dmesg 1>dmesg.log
error: device not found

Posted: **Sat Apr 30, 2022 9:57 am**

Ok if your driver is loaded already then you need to add the hardware id to your ini file so the device can be recognized
or better yet here use this one it has most newer devices in it already. it goes in your C drive(if that's your letter ) then
so it would be something like this, this is the path to mine, adjust as needed for your pc.
C:\Users\Rich I9 gigabyte\.android
if the folder is not there then make it
after which run
adb kill-server or just restart your pc either is fine
after that your device should be in your path and recognized by adb as on your pc

Posted: **Sat Apr 30, 2022 9:08 pm**

Not to sound ungrateful, but somehow I think you're skipping steps that you always take for granted because you have the keyboard in front of you.

E:\dmesg tool>adb devices -l
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached

Posted: **Sun May 01, 2022 7:50 am**

Hogwild wrote: ↑Sat Apr 30, 2022 9:08 pm Not to sound ungrateful, but somehow I think you're skipping steps that you always take for granted because you have the keyboard in front of you.

Do you not have the android sdk installed on your pc or something? I guess I did just assume you did, if you dont you need it or at least one of the minimal sdk programs with platform tools.
Sorry just trying to help

Posted: **Sun May 01, 2022 1:31 pm**

I installed a minimal toolkit from xda-developers.com . I copied the .ini file you provided (thanks) to the Android and adb folders.

I think that worked and I have a valid dmesg.log file. Is there any PII in that dmesg.log file? Do I need to sanitize it or can I just post it as it is?

Posted: **Wed May 04, 2022 9:11 am**

Are you still there, Rich? I believe I finally have a valid dmesg.log file.

Posted: **Thu May 05, 2022 8:57 am**

I am here on occasion when I have time, been very busy the last lately, so you found your problem?

Posted: **Thu May 05, 2022 5:36 pm**

I have no idea. I really know next to nothing about this subject.

I appreciate your time in this.

Here's the dmesg.log. Any suggestions would be appreciated. Inseego was extremely helpful earlier, but I can't reach them now, probably because business customers are their first priority.

Posted: **Wed May 11, 2022 4:30 pm**

BUMP

Anyone? Does anyone know how to read and interpret the logs?

Posted: **Thu May 12, 2022 12:51 pm**

Don't know what I'm looking for. Looks like your device is in a debug configuration?

Posted: **Thu May 12, 2022 4:23 pm**

Hi:

Thanks for offering to help. I don't know either. The symptom was that the device works, but the Web interface doesn't show the proper IP address, subnet mask, or other specifics properly, as described above.

Any help you can provide would be greatly appreciated. I was in regular touch with Inseego, who was being very helpful. But now, I haven't heard back from them in over 2 weeks. Rich has obviously been super helpful, but I'm sure he's busy.

Posted: **Fri May 13, 2022 8:28 pm**

What modifications were done, if any? Summarize so I don't have to read this whole thread, please.

Posted: **Sat May 14, 2022 8:54 am**

I'm not sure what you mean by modifications. Hardware mods? Software mods?

There's no need to read the whole thread. The thread can be summarized as follows:

1. I couldn't get the device to get a WAN IP and work on the carrier.
2. I got the device to get a WAN IP and work on the carrier after a firmwae upgrade from
the vendor, and some other stuff.
3. However, the device's web interface still doesn't display the items mentioned above properly.

Posted: **Thu May 19, 2022 3:29 pm**

Didneywhorl wrote: ↑Fri May 13, 2022 8:28 pm What modifications were done, if any? Summarize so I don't have to read this whole thread, please.

Would it help if I posted the dmesg.log and/or debug logs? My gut feeling is that this device is only getting IPv6 connecitivity and not IPv4 and that may be one reason for the missing/incorrect items in the web interface.

Posted: **Fri May 20, 2022 8:19 am**

These devices are set to show values of the carrier they are locked to, for instance, the data counter, it does not count data itself instead it query's the carrier for data use, I dont know this for sure on this model but I assume the ip and such are in a similar fashion, thus it works on AT&T and does not work on koodo because it does not query the right address it is trying to get the info from AT&T, if you know the koodo address I am sure it can be exchanged for the AT&T one, I may be wrong but I believe this to be the case. Have you tried to get it thru ipconfig?

Posted: **Fri May 20, 2022 1:55 pm**

Heres' the ipconfig results while in ippt mode:

2022-05-20 ipconfig-in ippt mode-sanitized.jpg

Posted: **Mon May 23, 2022 10:54 pm**

Rich Hathaway wrote: ↑Fri May 20, 2022 8:19 am These devices are set to show values of the carrier they are locked to, for instance, the data counter, it does not count data itself instead it query's the carrier for data use, I dont know this for sure on this model but I assume the ip and such are in a similar fashion, thus it works on AT&T and does not work on koodo because it does not query the right address it is trying to get the info from AT&T, if you know the koodo address I am sure it can be exchanged for the AT&T one, I may be wrong but I believe this to be the case. Have you tried to get it thru ipconfig?

Let's assume you're right. AT&T advertises this as a "Global Modem" able to operate in dozens of different countries. You'd think they'd want the customer (often a business customer) to be able to view accurate information in the web interface.

Posted: **Tue May 24, 2022 8:32 am**

They list it as a global modem because they are a global company and want you to subscribe to AT&T global services in any country you may be going to they do not advertise it to be unlocked as it comes locked to AT&T, I was fooling with this device last week for someone else and found a way to unlock it easily now without the need to load custom firmware to it, that does not help you but you can look in /opt/nvtl/webui or pretty close to that path and you can look thru the filesystem to see that they indeed use a url to get some or maybe all of that info you desire, you could prob exchange some of those files for that of the usb730L to possibly get your wanted fields to show up, work and be accessible to you from the devices admin ui.

Posted: **Tue May 24, 2022 8:05 pm**

What do you mean by unlock it? Carrier lock? Mine's already carrier unlocked.

Can I just connect the modem to my USB port and telnet into it, or do I have to figure out how to use ADB or something like that?

Posted: **Wed May 25, 2022 7:55 am**

adb is available on this device and is very easy to use, telnet is closed but you can also get root access from the consol port but you will have to clear the root password to get in like I have here

root usb800.PNG

but there is no need to do all of that when adb is open and waiting for you with no need to do anything to get root access.

Posted: **Mon May 30, 2022 10:43 pm**

So, I need to crack the root password even if I use adb to connect? Any suggestions for doing that? Or can you share that pwd with me?

Posted: **Tue May 31, 2022 1:33 pm**

No, you do not need to use the consol port to get root, just use adb it is open and no pass needed, the password for root thru the consol port is dynamic, I can clear it and make it all 0's for you if you think you need it but really you don't need it, just use adb

Posted: **Wed Jun 01, 2022 4:16 pm**

Much obliged. BTW, I haven't forgotten about that offer I made you earlier. I'm still chasing the guy who has the equipment. I may be waiting for a while, but I promise I will keep trying.

Posted: **Wed Jun 01, 2022 5:25 pm**

No worries

Posted: **Mon Aug 08, 2022 9:45 pm**

Rich:

With respect to what you mentioned above:

Are there better solutions?

1. Is it worth flashing it with different firmware? Is this the same modem as the USB8 for Verizon, just with slightly different firmware/web interface?

2. If I tried to attempt what you mentioned above, wouldn't I need root access to be able to write those html files to the filesystem?

Posted: **Tue Aug 09, 2022 7:31 am**

Hogwild wrote: ↑Mon Aug 08, 2022 9:45 pm Rich:

2. If I tried to attempt what you mentioned above, wouldn't I need root access to be able to write those HTML files to the filesystem?

Yes, you already have root via the ADB port. if you are hung up about using the ADB port, hit me up on skype and
I will zero your root pass for you so u can get in it that way, for me ADB is much easier.
I have not seen the Verizon variant yet but just looked up the specs for it and yes it seems to be the same SDx20 and
linux/os2, I will have to get my hands on one of these, vzw does not even have pics up on their site for it yet so it must be a pretty new offering from them and until you mentioned it, I did not even know it existed as a vzw branded device.
do you have one?
I am sure the web UI could be exchanged between the 2 devices, be careful if you do that to check and make sure of each of the files attributes/permissions after loading and before you reboot it or you may be ending up with a boot looped device.

Posted: **Sat Aug 13, 2022 9:36 am**

Hi Rich:

Thanks for that generous offer. I may take you up on it later. First, I typed the wrong model number above. The Verizon model is actually the USB8L. I'm guessing you've seen one of those/laid hands on it?

Next, an update: I finally got a callback from Inseego yesterday about my USB800. The tech. was very helpful and confirmed what I had suspected, that the modem, for some reason, was getting not getting an IPv4 address, only an IPv6 address on the network. He told me that the reason the web interface showed invalid info. (IP, Subnet, data transferred etc) was because that screen depends on IPv4 statistics. No IPv4 connection means no valid numbers. I believe what he said.

So the question becomes... why? He stepped me through checking the PDP setting, and it was set to dual stack. So he had no idea what to do after that. He suggested I talk with the carrier again.

Posted: **Sat Aug 13, 2022 2:30 pm**

Both Tmobile and Verizon have been showing a push to IPV6 only. It may be hardware related, but it may also be network provisioning.

Posted: **Sun Aug 21, 2022 7:31 pm**

Except I'm in Canada, so using neither of those carriers. I'd contact my carrier, but their techs. seem to know zero about this subject.

EDIT: Okay, maybe I misunderstood what you wrote, Didneywhorl. Did you mean maybe IPv4 is disabled in firmware or something like that? Inseego swears it's not on the USB800. And other people in the U.S seem to report getting an IPv4 address in the web interface while on other carriers.

This is kind of baffling.

Posted: **Tue Sep 13, 2022 6:16 pm**

Hmm..I can't seem to connect to the modem via adb now. What am I doing wrong?

- USB800 modem drivers are still installed.
- I used the adb.ini file that rich provided, which includes the correct Vendor ID for my device.
- If I type "adb devices -l" I get no results.

What am I missing here? It worked before.

Posted: **Tue Sep 13, 2022 11:40 pm**

Check your device manager to see if the ADB device is present there, it likely is.
ADB gets "left on" so to speak by a lot of programs and in this case you need to run the command

adb kill-server

or just force stop the ADB process in your task manager
then if present it will be recognized again by ADB
If it is not present in your device manager then you can factory reset the device and try again.

Posted: **Wed Sep 14, 2022 11:52 am**

Here's my Device Manager when I have Ethernet disabled. I have to disable Ethernet in order to enable the USB800 or they conflict, which is quite a pain.

I don't see any ADB entry. Under what category should I see it?

Does "Enable AT commnad port" in the web interface need to be checked? I'm assuming yes? The screenshot below is with AT command port enabled.

No, I do not have the Verizon version of the USB8. Sorry, I thought you had meant the USB730L.

Posted: **Wed Sep 14, 2022 2:37 pm**

That is prob it there in the other devices tab (usb800)
look at the hardware id, if it is

USB\VID_1410&PID_B023&REV_0318&MI_04
USB\VID_1410&PID_B023&MI_04

than that is it and that means you just need to load a driver for it.

Posted: **Wed Sep 14, 2022 2:43 pm**

That's what I'm saying. Driver is still installed from months ago. Device still works. But adb won't connect to it.

Posted: **Wed Sep 14, 2022 2:49 pm**

right click it and select uninstall then right click anything else in there and select scan for hardware changes and see if it will reload the driver for you, if it doesnt you just need to force the driver, windows machines are like this, especially 10 and most especially 11 <-------horrible OS for working with devices and ports.

Posted: **Wed Sep 14, 2022 3:24 pm**

The modem works. I can upload and download data, so I think the driver is working. Also, the menus in Device Manager show the Diagnostic interface as functioning properly.

Posted: **Wed Sep 14, 2022 3:47 pm**

I thought you were looking for the ADB port?
If you are looking for the ADB port do what I said above and check the hdwr-id for that usb800 in the others tab if it is MI_04
then it is the adb pport then you know all you need to do is force the driver and the port will be working again.

Posted: **Wed Sep 14, 2022 4:30 pm**

There's no "others" tab, so not sure what you mean.

I uninstalled and reinstalled the driver. Here are screenshots from the entries under Device Manager's
1. Network Adapter category and;

2. Modem category

Posted: **Wed Sep 14, 2022 5:00 pm**

Look in your screenshot you posted (other devices) tab with the ? next to it that is the one you are after

Posted: **Wed Sep 14, 2022 5:20 pm**

Hmm... The Other devices category has disappeared again. It doesn't always appear. Any idea why?

Could it be that I now have VMware player installed? It seems to do "interesting" things to my network adapter settings sometimes.

Posted: **Wed Sep 14, 2022 6:00 pm**

No as long as you are not using a virtual machine and you are using the same windows as your screenshot with the same device plugged into the same port it should all be the same

Posted: **Wed Sep 14, 2022 6:06 pm**

Well, I guess that part of it is flaky. BTW, driver updates dont' seem to exist for these things, do they? The driver that I intalled, is it not for the modem part?

This is becoming a pain. Every time I need to try anything, I have to disable Ethernet, do what I need. Save screenshots. Disable the dongle. Enable Ethernet post back my results, etc. I dont suppose there's any way around that?

Posted: **Wed Sep 14, 2022 6:17 pm**

Why dont you just unplug it when you need other web, these devices are desinged to have their RNDIS ports take priority when inserted. there were no drivers for this model other than the gps driver which does no good so we have to use drivers from other models is why they behave like this.
I modified drivers to have the correct hardware id's but the prob with sharing them is windows requires driver signing and even though on some builds you can use test mode to bypass it from windows 8 and beyond you cannot install an unsigned driver without a good amount of modding first.
forcing drivers is really easy once you have done it a time or 2

Wireless Joint

Novatel/AT&T usb800 doesn't get IP address

Novatel/AT&T usb800 doesn't get IP address

Re: Novatel/AT&T usb800 - Drivers don't seem to install

Re: Novatel/AT&T usb800 - Drivers don't seem to install

Re: Novatel/AT&T usb800 - Drivers don't seem to install

Re: Novatel/AT&T usb800 - Drivers don't seem to install

Re: Novatel/AT&T usb800 - Drivers don't seem to install

Re: Novatel/AT&T usb800 - Drivers don't seem to install

Re: Novatel/AT&T usb800 - Drivers don't seem to install

Re: Novatel/AT&T usb800 - Drivers don't seem to install

Re: Novatel/AT&T usb800 - Drivers don't seem to install

Re: Novatel/AT&T usb800 - Drivers don't seem to install

Re: Novatel/AT&T usb800 - Drivers don't seem to install

Re: Novatel/AT&T usb800 - Drivers don't seem to install

Re: Novatel/AT&T usb800 - Drivers don't seem to install

Re: Novatel/AT&T usb800 - Drivers don't seem to install

Re: Novatel/AT&T usb800 - Drivers don't seem to install

Re: Novatel/AT&T usb800 - Drivers don't seem to install

Re: Novatel/AT&T usb800 - Drivers don't seem to install

Re: Novatel/AT&T usb800 - Drivers don't seem to install

Re: Novatel/AT&T usb800 - Drivers don't seem to install

Re: Novatel/AT&T usb800 - Drivers don't seem to install

Re: Novatel/AT&T usb800 doesn't get IP address

Re: Novatel/AT&T usb800 doesn't get IP address

Re: SOLVED-Novatel/AT&T usb800 doesn't get IP address

Re: SOLVED-Novatel/AT&T usb800 doesn't get IP address

Re: SOLVED-Novatel/AT&T usb800 doesn't get IP address

Re: SOLVED-Novatel/AT&T usb800 doesn't get IP address

Re: SOLVED-Novatel/AT&T usb800 doesn't get IP address

Re: SOLVED-Novatel/AT&T usb800 doesn't get IP address

Re: SOLVED-Novatel/AT&T usb800 doesn't get IP address

Re: SOLVED-Novatel/AT&T usb800 doesn't get IP address

Re: SOLVED-Novatel/AT&T usb800 doesn't get IP address

Re: SOLVED-Novatel/AT&T usb800 doesn't get IP address

Re: SOLVED-Novatel/AT&T usb800 doesn't get IP address

Re: SOLVED-Novatel/AT&T usb800 doesn't get IP address

Re: SOLVED-Novatel/AT&T usb800 doesn't get IP address

Re: SOLVED-Novatel/AT&T usb800 doesn't get IP address

Re: SOLVED-Novatel/AT&T usb800 doesn't get IP address

Re: SOLVED-Novatel/AT&T usb800 doesn't get IP address

Re: SOLVED-Novatel/AT&T usb800 doesn't get IP address

Re: Novatel/AT&T usb800 doesn't get IP address

Re: Novatel/AT&T usb800 doesn't get IP address

Re: Novatel/AT&T usb800 doesn't get IP address

Re: Novatel/AT&T usb800 doesn't get IP address

Re: Novatel/AT&T usb800 doesn't get IP address

Re: Novatel/AT&T usb800 doesn't get IP address

Re: Novatel/AT&T usb800 doesn't get IP address

Re: Novatel/AT&T usb800 doesn't get IP address

Re: Novatel/AT&T usb800 doesn't get IP address

Re: Novatel/AT&T usb800 doesn't get IP address

Re: Novatel/AT&T usb800 doesn't get IP address

Re: Novatel/AT&T usb800 doesn't get IP address

Re: Novatel/AT&T usb800 doesn't get IP address

Re: Novatel/AT&T usb800 doesn't get IP address

Re: Novatel/AT&T usb800 doesn't get IP address

Re: Novatel/AT&T usb800 doesn't get IP address

Re: Novatel/AT&T usb800 doesn't get IP address

Re: Novatel/AT&T usb800 doesn't get IP address

Re: Novatel/AT&T usb800 doesn't get IP address

Re: Novatel/AT&T usb800 doesn't get IP address

Re: Novatel/AT&T usb800 doesn't get IP address

Re: Novatel/AT&T usb800 doesn't get IP address

Re: Novatel/AT&T usb800 doesn't get IP address

Re: Novatel/AT&T usb800 doesn't get IP address

Re: Novatel/AT&T usb800 doesn't get IP address

Re: Novatel/AT&T usb800 doesn't get IP address

Re: Novatel/AT&T usb800 doesn't get IP address

Re: Novatel/AT&T usb800 doesn't get IP address

Re: Novatel/AT&T usb800 doesn't get IP address

Re: Novatel/AT&T usb800 doesn't get IP address

Re: Novatel/AT&T usb800 doesn't get IP address

Re: Novatel/AT&T usb800 doesn't get IP address

Re: Novatel/AT&T usb800 doesn't get IP address

Re: Novatel/AT&T usb800 doesn't get IP address

Re: Novatel/AT&T usb800 doesn't get IP address