Re: IPSEC Services Not Starting -Port Issue-
- From: "Cliff Galiher" <cgaliher@xxxxxxxxx>
- Date: Thu, 21 Aug 2008 17:40:19 -0600
WARNING: Going off topic again:
Teneo,
You are, of course, entitled to your opinion. As is everyone. I have said repeatedly that I don't not think Microsoft is blameless in this. But what I am also saying is that I don't know why we are bringing it up again?!? My entire purpose for the last post to stephen was to put his mind at rest that we (or at least I) did not sweep anything under the rug. I just wanted to explain that a difference of opinion doesn't mean that he was ignored...but that the discussion had run its course and now we had to deal with what was in front of us...specifically the OP's request for help on *resolving* an issue.
Now for my generic rant...so please, do not think I'm talking about you (Teneo or Stephen) specifically, I just want to explain why I replied the way I did in a general fashion because I've seen this behavior increasing recently.
<rant>
Many of us here volunteer our time to make this newsgroup a useful place...and there are situations that arise from time to time that you just learn to take in stride. And as such, there will be differences of opinion. Sometimes, just sometimes, you might even find yourself in the minority with your opinion. But you can't start shouting louder simply because you feel lonely. That accomplishes nothing.
It bothers me when somebody has a negative opinion and continually uses other threads to vocalize their opinion. We *know* it already! We've read it in the first three threads you complained in. So what I'm asking is, before you click "reply," does your post help the OP resolve their issue. In this case, saying "MS shouldve tested the patch" does *not* help the poster resolve their IPSec issue. The patch is out, it *does* break other services, and a registry edit *is* required.
If I post that I think a server has been compromised because of the description of the problem, don't hit "reply" and start telling me I'm wrong about surfing on a server. Or, if you do, you had damn well better have an alternative solution for the original poster; otherwise it was an unnecessary post and a mindless attack...and one I will take note of. :)
I am a big boy and perfectly capable of taking criticism. So if you give advice in a thread you don't agree with, please, contradict me. I *invite* it. I'm willing to learn! But just attacking my advice and then failing to give an alternative of your own is no longer helpful. It slows down the process, does not help the poster resolve their issues, and makes these threads more difficult to search.
</rant>
Now back to our regularly scheduled problem solving.
-Cliff
"Teneo" <not@xxxxxxxx> wrote in message news:uZdGOD%23AJHA.1980@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxxThe 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@xxxxxxxxxxxxxxxxI'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!
.
- References:
- Re: IPSEC Services Not Starting -Port Issue-
- From: SuperGumby [SBS MVP]
- Re: IPSEC Services Not Starting -Port Issue-
- From: Teneo
- Re: IPSEC Services Not Starting -Port Issue-
- Prev by Date: Re: IPSEC Services Not Starting -Port Issue-
- Next by Date: Re: Virtulization on SBS-EBS2008
- Previous by thread: Re: IPSEC Services Not Starting -Port Issue-
- Next by thread: Users getting booted from network when another logs on?
- Index(es):
Relevant Pages
|
