Possible Trend SMB 3.0 CSM problem on SBS2003



Hello everyone,
I have had the worst time this week with our servers. It appears that the installation of the Trend Micro 3.0 CSM install may be to blame.


A little background information. Last weekend I installed SBS SP1, ISA 2004, and SQL 2000 SP4. I also upgraded the Trend Micro from 2.0 to 3.0 (note to self, upgrade one thing at time to see which one screws things up). Our server had just been upgraded two weeks before using the Swing It procedure from a SBS 2000 box that was having hardware failures. Everything had been fine up until the patches this past weekend. Monday morning no one can log in to exchange, terminal server, database server is slow, etc. Called Microsoft PSS. Tech has no luck troubleshooting anything and to be honest I was never able to get a hold of him again (Didn't return emails, did not call as scheduled, etc). So in panic mode I start to uninstall ISA server 2004, Group Policy Management Console Etc. System would work fine for some users and not for others. But none of those appeared to fix the problem. Finally today I noticed while scanning through the service on the server that there is a Trend Micro Personal Firewall service installed on all of the servers. Stop the service and networking appears to be back to normal.

I thought when I did the install that I configured Trend to not use the personal firewall. All of our machines now have the Trend Micro personal firewall installed. If you are having problems with your system you might check to see if this is the case. I am no SBS2003 networking expert but and this about drove me crazy. Please let me know if anyone else has seen behavior like this.

Mark
.



Relevant Pages

  • Re: New Event Log Errors!
    ... Somehow along those lines I'd also installed the Certificate Authority ... Did you apply the last Server Pack for SBS Server? ... Please install Windows Support Tools on the win2k3 sp1 problematic ... Microsoft is providing this information only as a convenience to you: ...
    (microsoft.public.windows.server.sbs)
  • Re: Possible Trend SMB 3.0 CSM problem on SBS2003
    ... and it did NOT enable the firewall. ... > installation of the Trend Micro 3.0 CSM install may be to blame. ... Our server had just been upgraded two weeks before using the Swing It ... > through the service on the server that there is a Trend Micro Personal ...
    (microsoft.public.windows.server.sbs)
  • Re: IPSEC Services Not Starting -Port Issue-
    ... Also when you are presented with a patch you expect it to have been tested thoroghly BEFORE being released so you shouldn't have to 'wait for others to install ' I appreaciate Microsoft has to accomadate many configurations but the IPSEC issue is very basic. ... As far as Trend Micro goes, It installed the firewall protocols on all workstations and server adapters even though i did not have it enabled, before upgrading to the latest version. ... installs some sort of a Firewall service, even if it's told not to.... ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot activate SBS 2003 SP2
    ... everywhere and sitting on the case of the server is the old board - balanced ... slip stream SBS you would have had it ages ago. ... My main reason for slipstreaming the install is because I cannot get ... updates that need to be applied if one is to have a succesful outcome ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot activate SBS 2003 SP2
    ... the old array was a raid 5 that should not have become so rooted but the twit who built the server did not actually enable the spare drive to act as a spare!! ... The problem is SBS is unique and I've rarely if ever seen it work. ... The server has been chugging away in a small business environment for several years and I have administered it for them for about a year making sure that the updates were installed and their mailboxes were managed etc etc. ... My main reason for slipstreaming the install is because I cannot get the original 2003 server install to cope with the new hardware and it falls over part way into the install - BSOD bit. ...
    (microsoft.public.windows.server.sbs)