Re: Jacked up Exchange server!!!

  • From: "Marvin Cummings" <marvc@xxxxxxxxxxxxx>
  • To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
  • Date: Thu, 25 Apr 2002 11:55:59 -0400

Yeah overkill indeed, but desperate times calls for desperate measures. I
couldn't narrow what part of my DNS settings were causing the problem and
attempting to remove exchange from AD was proving to be too tedious. Trust
me, now I know.

-----Original Message-----
From: Alfonso Lopez de Ayala [mailto:alopezdeayala@xxxxxxxxxxxx]
Sent: Thursday, April 25, 2002 11:23 AM
To: [ExchangeList]
Subject: [exchangelist] Re: Jacked up Exchange server!!!

Wow... seems overkill... and why exactly do you need to uninstall
Exchange to fix DNS?  I have always been able to fix DNS problems by
itself... manually uninstalling Exchange (especially with all the LDAP
stuff to manually remove in Active Directory) is a pain in the neck.  I
thought that different services are fixed separately... no need to
reinstall one so that another works... only need to configure both right
to interact with each other. No?

-----Original Message-----
From: Matt Dillingham [mailto:mdilling@xxxxxxxxx]
Sent: Thursday, April 25, 2002 7:17 AM
To: [ExchangeList]
Subject: [exchangelist] Re: Jacked up Exchange server!!!


i think that i know what your problem is if:

- you are running your own MS DNS server (probably on the domain
- the exchange machine is on a different hardware from the DC.
- you have only one domain controller. (probably)

i am pretty sure that this problem is an effect of not having DNS setup
100% correct.  the exchange server and active directory domain
controller cannot find each other, which is what is causing the problem.
Clients can still resolve names, ect, but if you look more closely, it
isnt entirely working (with regard to AD). there is a DNS tool in the 2K
server reskit that will help you to confirm this (unfortunately, i dont
recall its name right now).

if this is actually the case, to fix it you will need to manually
uninstall the exchange installation (Q260378), fix DNS, (putting in
another DC to test is a good idea since i believe that another DC wont
install either without DNS being fixed), and then reinstall exchange
(being sure to run domain prep, ect.).  everything should work fine
then. ..assuming that this is actually the problem.

anyway, hope this helps.  good luck!

 Matt Dillingham                        Systems Administrator II
           University of Michigan, Bioinformatics

Marvin Cummings wrote:
> Exchange 2000 Server Newbie...
> I have reason to believe that my exchange server install is completely
> screwed up and need to know if there's anyway to resolve this without
> to rebuild my entire network??
> 1. From what I can tell the exchange service isn't starting.
> 2. If i go to my AD users & computers console I see what appears to be
an OU
> for Microsoft Exchange System Objects, but its not a folder, it looks
> though its not associated with anything.
> 3. If i attempt to start the mailbox management process via the System
> Manager, I get an error that the Microsoft Exchange System Attendant
> is unavailable.
>         ID no: c1031668
> This is the 2nd time I've un-inistalled and re-installed this exchange
> server. Can anyone shed some light onto this otherwise dismal
> :-<
> ------------------------------------------------------

You are currently subscribed to this Discussion List as:
To unsubscribe send a blank email to

You are currently subscribed to this Discussion List as:
To unsubscribe send a blank email to

Other related posts: