PDA

View Full Version : Nod32 with Windows 2003 Server


dwood
February 25th, 2005, 04:17 AM
One of our Windows 2003 Servers would randomly lockup and even tho it looked like it was working correctly wouldn't respond to any client connections and had to be rebooted.

I happened to do a Windows update last night on my Windows XP pro pc with SP2 and happened to notice this one update.

{QUOTE-> Update for Windows XP (KB887742). This update addresses an issue that could cause your system to stop responding if certain firewall or antivirus programs are installed. You can help resolve this issue by installing this HTTP.sys update from Microsoft. After you install this item, you may have to restart your computer. <-QUOTE}

I then happened to follow the Microsoft link to the related article http://support.microsoft.com/kb/887742 and found that it also affects Windows 2003 Server. But as normal Mircosoft haven't got a fix for it yet!.

I think this could be the cause to why some people and this one server of ours that randomly dies.

Anyone else got any thoughts?, does Eset know about this?

Dan

Blackspear
February 25th, 2005, 04:24 AM
Do you have IMON disabled?

There is a thread HERE (http://www.wilderssecurity.com/showthread.php?t=43669) on using Nod32 on a 2003 Server.

Hope this helps...

Cheers ;D

dwood
February 25th, 2005, 04:34 AM
Blackspear,

Yeah I had IMON disabled, we don't use it here even on our client PCs. It would proberbly cause to many problems.

I've already look through most of the threads for Windows 2003 Server and most of then said disable IMON which we had already done. I just happened to see that update last night a thought I might be related.

Cheers,

Dan

Blackspear
February 25th, 2005, 04:40 AM
Can you send an email to support@nod32.com with a link back to this thread.

We would also appreciate if you can keep us in the loop as to your progress, as we all learn this way...

Cheers ;D

dwood
February 25th, 2005, 04:49 AM
Blackspear,

I have sent an e-mail to Eset, if I get anything back I shall keep everyone informed.

Hopefully Microsoft will release a fix for this soon!!

Cheers,

Dan