Re: IPSEC Services Not Starting -Port Issue-
- From: "Teneo" <not@xxxxxxxx>
- Date: Thu, 21 Aug 2008 23:53:59 +0100
I agree with stephen... microsoft should have done MORE! I watch the blogs,
visit this forum but even I missed the IPSEC issue and 10 servers next
morning no network. This was nearly 4 weeks after the patch, ample time with
microsoft resources to issue a fix the fix.
Not all 'admins' know of this blog... many admins are now self taught users
as Microsoft wants, pushing the product saying it is easy to install your
self.
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.
Also you could be one of the few who installed BEFORE even the blogs (
microsoft ) knew about the issue.
"Susan Bradley" <sbradcpa@xxxxxxxxxxx> wrote in message
news:%235CcKAwAJHA.4172@xxxxxxxxxxxxxxxxxxxxxxx
The problem is how do they know you are an SBS owner?
http://blogs.technet.com/sbs
ALWAYS watch that blog.
And as far as a new fix, it won't be immediate as it has to go through
testing and ensure that there aren't more issues.
Steve wrote:
I really appreciate all of the responses!!! What would i do without this
forum?
When MS discovered that there were flaws with the updates, they should
have immediately issued another fix, or at least send out notifications
to affected users...
Oh well. 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. I figured it was the
culprit, and the server worked once i removed it. I have Trend Micro
support chewing on this one as well. "SuperGumby [SBS MVP]" wrote:
I agree with the others that it is _more likely_ the patches from MS
than Trend, however, should it prove otherwise you can prove the Trend
side of things by'unbinding' the firewall service from the NIC(s, but it
should only be necessary on your internal) and restarting
"Steve" <Steve@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:FD4CE731-645B-4033-9CB5-FE628CA6C09E@xxxxxxxxxxxxxxxx
I've been successfully running a Small Business Server 2003 with 25
Clients.
I recently updated the Trend Micro SMB product to their latest Worry
Free
solution. It ran fine for a few days, then MS submitted updates that
required
the server to restart. I came in the next morning to find the entire
network
down, everybody going crazy because they couldn't work, etc.
What had happened was that the new version of Trend-Micro provides &
installs some sort of a Firewall service, even if it's told not to....
The problem was that the IPSEC services would not start because a
required
port was being used by another program or service.
I did not have time to mess around, un-installed trend micro, re-booted
and
all is up and running now. I left the mail scan portion of trend micro
on the
system, which works.
I would like to re-install the trend micro product, but how would i
prevent
these types of issues from re-ocurring? I do not have a backup server,
nor a
test environment to mess around in, do not want to experiment on the
production server. Any suggestions would be appreciated. Thanks!
.
- Follow-Ups:
- Re: IPSEC Services Not Starting -Port Issue-
- From: Cliff Galiher
- Re: IPSEC Services Not Starting -Port Issue-
- From: Susan Bradley
- Re: IPSEC Services Not Starting -Port Issue-
- References:
- Re: IPSEC Services Not Starting -Port Issue-
- From: SuperGumby [SBS MVP]
- Re: IPSEC Services Not Starting -Port Issue-
- Prev by Date: Re: iPhone 3G won't sync with SBS 2003
- Next by Date: Re: IPSEC Services Not Starting -Port Issue-
- Previous by thread: Re: IPSEC Services Not Starting -Port Issue-
- Next by thread: Re: IPSEC Services Not Starting -Port Issue-
- Index(es):
Relevant Pages
|
