Win 2003 sbs lagging after installing nod

Hi,got a small problem concerning nod on 2003 sbs OS,after a clean install of the 2003 server i installed nod32(amon and imon disabled)but after restart i had a bunch of services that failed to start and the server was lagging as hell.I have never installed it on a 2003 sbs before but we have it installed on 2000 and 2003 servers with no problems(except AMON).Anyone else experienced this before?
Thanx

 

Hello,
could you confirm that the IMON icon was actually GRAY and NOT RED?

 

Yes i double checked the settings coz it didnz make sense that it was lagging since i never got this problem before.The server was updated with the latest fixes and has a sharepoint installed(dunno if it matters)

 

Not experienced it in over 20 SBS setups. Main thing to focus on..that your two Exchange data directories are excluded in AMON...although you do have AMON disabled..so that should be moot. And it wouldn't cause your SBS box to lag either even if you didn't exlude them.

With SBS..when you setup http updates..you need to change the default port...notice that the default port NOD32 uses for http updates to clients is the same as Sharepoint.

Did you run all your Windows Updates on the SBS box before installing NOD? Wondering if it's MDAC related.

Is your SBS box multi-homed? Or single NIC?

 

I did not pay attention on ports for updates but that could be why it had problems,now i remember that the update did not go trough(just kept getting updating...).Will try changing the port.Thanx for the help.

Oh sorry did not answer it's single NIC,and yes i'we installed all the updates before installing nod

 

I have Nod32 running on my SBS2003 server with no problems.

Maybe a silly question, but you installed ndntenxs rather than ndntenst I suppose?

 

Yes i did and the question is not silly at all,i am known to be impulsive sometimes

 

You mention that you installed Nod32 after the fresh Win2003 installation. Do you mean imediately after the Win2003 part of the SBS2003 installation or after the full SBS2003 installation & reboot? Are you using the SBS2003 Standard or Premium version?

Are you using Remote Admin Server & console on the same server?

Are you using regular defalt Nod32 settings or are you using customised or even Blackspear's settings?

 

After i finished the installation and applied all the fixes i rebooted the server.No the administration console is installed on another computer in the domain,only the update folder is on the server.The setting are default since the problem manifested itself immediatlly after the restart upon installing nod.The sbs is standard edition.Today i will see if the problem is related to update port and the fact that sharepoint uses the same,will post if that solved the problem(or not).

 

What do you have for event viewer errors?

 

Just done a fresh install of SBS2003 myself w/ NOD32 2.51.8 - No problems here. Make sure you read through the SBS manual. If you don't have it, PM me and I'll send it you. I was sent it by ESET Sales when I became an Enterprise customer.

 

Looks like the problem was with sharepoint port,when i changed the lan update port everything passed with no problems.Thanx for the help.

 

I'm glad your issue is solved. I didn't experience that problem the first time I installed NOD on SBS2K3...the only way I found it..was that clients were giving errors on trying to update. Since they were looking at the default port, 8081, on the IP of the SBS box..and Sharepoint ran on that port..they ended up getting a user authentication challenge from Windows. I kept scratching my head.."http updates does not require a user/pass"...so I opened up Windows Explorer..type in the servers IP:8081...got the Windows authentication challenge..logged in..and sure enough...I was staring at Sharepoint instead of the NOD update files. LOL.