Installing NOD32 kills my Wireless connectivity

AlexManics · 23 May 2006 at 15:34

I have just downloaded a highly reccommended AntiVirus program for trial named "NOD32" but after it has installed and restarted Windows, I am no longer able to connect to the internet via wireless (to my ADSL router.)

Windows shows my connection as "Limited or no Connectivity"

Any help appreciated.
__________________
XPS M170 ¦ 2.13Ghz ¦ 2GB Samsung ¦ GeForce 7800 GTX ¦ 100GB 5400 HD ¦ NEC 8X DVD+-RW ¦ Win XP Pro¦ Dell 2405W Monitor

no_1_dave · 23 May 2006 at 17:25

Thats not a Nod32 problem.
I get that error when there's something wrong with my wireless connection. Try rebooting your router and maybe your pc again...

AlexManics · 23 May 2006 at 17:53

I'm pretty certain it's something to do with the Nod32 software because when I uninstall it and reboot, my wireless works perfectly again.

xb8browney · 23 May 2006 at 18:24

My sister’s computer is running nod32 and she is connected wirelessly with no problems

AlexManics · 23 May 2006 at 19:10

Ok this is getting weirder.
I've now installed Nod32 on my other computer, a desktop PC and get exactly the same problem!
But my desktop is connected with ethernet cable to my Netgear router, not wirelessly.

I downloaded a 30 day trial from the www.eset.com web site.
If I disable IMON (the one that monitors internet traffic) it works.
I wonder if Spyware Doctor could be the problem?

The Deuce · 23 May 2006 at 21:23

i use NOD on all 3 of my computers on a wireless set up and no probs at all

AlexManics · 24 May 2006 at 13:06

After some help from Eset technical support, the problem is still unresolved, but interestingly this is what they had to say:

Hello,

You can struggle with this, or you can go NOD32 Control Center (down by the clock) > IMON > Quit. Now a reboot is necessary.

The next version of NOD32 will be sans IMON. It's being totally eliminated from the program for this very reason.

In 1992, when NOD32 was introduced, very few programs operated at the winsock level. Today, in addition to Google and Microsoft, 100's of other developers are creating software in this manner. That would be fine, except for the fact that any app that operates here, needs the top spot in the stack, and only one program can have it.

As it is now, it can't be enabled at all, on a server.

IMON was just the first layer of defense, a supplement. The strengths of NOD32 are AMON, which scans every file that performs an action, as it performs that action, and the advanced heuristics which is stopping 90+ % of all new threats, before a definition is even written.

By quitting IMON now, you'll not only allow both programs to operate together, but you'll also lose no coverage.

Thank you,
Eset Tech Support

gpuerrilla · 25 May 2006 at 08:17

An interesting read.