Dave
Sat Sep 18 13:04:48 CDT 2004
That would be a good thing to check. I don't know anything about SMB
signing in particular, but I made a related reg edit in response to a
different problem I was having and things went downhill rapidly. Luckily I
had kept track of what I changed, and putting it back solved the new
problems.
Den - have you tried uninstalling the patch? Also, I believe that MS
provides free phone support for patch-related incidents at 1-800-PCSAFETY
(it's at least worth a try). If Exchange is not running, do an offline
backup of your databases to a workstation on your network - even if you have
to reinstall, you should be able to restore the old databases when the
server's back up and running.
"Jim Behning" <jimbehningmvp@atl.mindspring.com> wrote in message
news:6c2nk0h3mt7sbdkc2e4r88f22jjqhs3p26@4ax.com...
> 839499? I have a server that refuses to hang on to the edits in the
> article. Nothing AD relatedworks well when that happens.
>
> "Den" <anonymous@discussions.microsoft.com> wrote:
>
>>There's a whole rash of errors across the board.
>>ntdsutil uncovered a few which are now cured, whereas
>>nltest suggests that the RPC is corrupt.
>>
>>The event logs keep talking about inetinfo and rpc, and
>>the fact that Exchange fails to start. I suspect that
>>the rpc somehow got corrupted during the hotfix and has
>>taken the rest of the system with it.
>>
>>I've rebooted a couple of times with no luck, so I
>>figure 'format c:, d:\setup' etc. is the way to go; if
>>nothing else, it's been an informative couple of days.
>>It's not that big a deal; apart from the waste of time
>>all I'll lose is the Exchange part of the system, which
>>needed a clear-out anyway.
>>
>>Thanks for the response Dave, I appreciate it.
>>
>>>-----Original Message-----
>>>I hate to ask this, but are there any other symptoms
>>besides the logged
>>>error? I'm wondering if this is just a timing thing
>>where the AD couldn't
>>>contact the GC because the server was starting up and it
>>didn't respond in
>>>time because it's otherwise busy. I've had global
>>catalog errors from time
>>>to time, but by the time I discovered them the system
>>had recovered from
>>>whatever problem it had.
>>>
>>>Unfortunately, nothing much comes up in a TechNet search
>>of "8430" or
>>>"3200c45." Did you try rebooting to see if the error
>>popped up again? I
>>>view the format/reinstall option as a very last resort
>>after every other
>>>thing has failed. I wouldn't even consider it without
>>having called
>>>Microsoft PSS to run the problem by them. At the worst,
>>maybe they can
>>>suggest how to preserve the server's data before a
>>reinstall. (On that
>>>topic, can you stop Exchange and copy your databases out
>>to a workstation,
>>>along with your user data, etc? I'd try to save the
>>data before moving on
>>>to the AD problem).
>
> Jim B. SBS MVP
> remove the mvp to send email