Conflict with Verizon Pantech UM175 USB Modem

My Verizon Pantech UM175 USB Modem on Windows XP SP2 does not work when ESET Smart Security is loaded. I have updated to beta 4.0.68 and the problem continues. I am thinking there is TCP/IP shim conflict. It is critical that I get this working (and result in a possible company roll out).

 

Hello YaddaMinski,

Can you please elaborate in detail on what you mean when saying it "does not work"? Also, can you install the latest version of v3.0 to see if the issue remains.

Thank you,
Richard

 

Using Verizon VZAccess Manager 6.8.1. It tests the UM175 OK. The Wizard configures the UM175 OK. Then when finalizing set up, VZAccess Manager throws the error "Unable to create a new connection - Error 711".

This was the same problem with ESET Smart Security V3. I upgraded to beta V4 to get my Cisco VPN client to work (doesn't work with ESET V3).

My 'Local Area Connection 2' is listed as 'PANTECH UM175 WWAN Driver'.

 

Hello,

Please switch to interactive mode and adjust your protocol filtering.

1. Open the main program window by clicking the ESET icon next to the system clock or by clicking Start -> All Programs -> ESET -> ESET Smart Security.
   
2. Press the F5 key to display the Advanced Setup window.
   
3. From the Advanced Setup tree, click Personal Firewall and then select Interactive mode from the Filtering mode drop-down menu.
   
4. Then click Protocol Filtering.
   
5. Select the Applications marked as Internet browsers or e-mail clients option.
   
6. From the Advanced Setup tree, click Antivirus and antispyware -> Web access protection -> HTTP -> Web browsers and make sure that only the applications you want scanned with the Internet filter are selected. Typically only real web browsers (iexplorer.exe, firefox.exe, etc.) will need to be selected. Repeat this step for email clients (outlook.exe, thunderbird.exe, etc.) by clicking POP3 -> Email Clients.
   
7. Click OK to save your changes.

Also, Check with Verizon for the files that need access through the firewall.

Thank you,
Richard

 

I am reporting back that the problem was not ESET but Windows itself. A telecom service kept bombing and could only be resolved by wiping drive and reloading Windoze XP SP3 fresh. Now everything works OK for the time being. ESET still gets my thumbs up.