Hi hope you can help. We sold our client NOD32 after installing it on a 30day trial but only rolling out to about 25 computers. The server we installed nod on was an HP DL380G4 and was re-installed two weeks before we installed NOD32 with Windows 2003 64bit SP2. Everything went fine and worked but after a day or two the server started to give problems 2 or 3 times a day. The screen was either black or just blue (not the blue screen of death). We could ping the server but couldn’t connect to it in any way. After a reboot everything was fine and there was nothing unusual in the logs. I tried HP firmware upgrades, Windows updates etc... but the problem continued. We then moved the Nod Admin console to another server, which was a domain controller as well as the WSUS server. This was an HPDL320 with Server 2003 Sp2 32bit. The move went well and all the computers moved across very easily. After a day or two the same problems as the previous server started happening. I changed the update times (frequency that the computers connect to remote admin) from 5 minutes to 30 minutes as I thought maybe the server couldn’t handle the traffic from 150pc’s. Next I moved it to a brand new HPML110 server Windows2003 SP2 32 bit which was also a domain controller and guess what it wasn’t long and same problem. I enabled logging on the HP5304 switch to monitor the traffic and the traffic was not excessive and no different prior to the server being non responsive. Well on Tuesday I installed another brand new ML110 server which is a standalone server Windows2003 32bit not a domain controller specifically for NOD32 and its doing the same thing. I can ping it but can’t connect to it and it now has to be hard reset to get it functional again. Remote restarts i.e shutdown /r /m \\computer /f don’t work.