Exchange 2007 broke the server

Hi,
I installed Exchange 2007 on a 2003 R2 server. Subsequently logging in
to the server took a long time and it turns out that GPOs were not
applied since a domain controller could not be found. Web browsing from
the server also did not work. Exchange event log reported that it could
not access AD. After several days chasing DNS issues I have uninstalled
Exchange 2007 (a major undertaking) and the server is back to normal. No
other servers or clients had any AD problems at any time. Has anyone
experienced this and found a solution? I need to install Exchange 2007
on this server but not if it breaks things.

Thanks,

Mark
Tue Nov 13 00:38:26 PST 2007

On Mon, 12 Nov 2007 09:46:33 -0600, Jim <nospam@any.time> wrote:

>Hi,
>I installed Exchange 2007 on a 2003 R2 server. Subsequently logging in
>to the server took a long time and it turns out that GPOs were not
>applied since a domain controller could not be found. Web browsing from
>the server also did not work. Exchange event log reported that it could
>not access AD. After several days chasing DNS issues I have uninstalled
>Exchange 2007 (a major undertaking) and the server is back to normal. No
>other servers or clients had any AD problems at any time. Has anyone
>experienced this and found a solution? I need to install Exchange 2007
>on this server but not if it breaks things.
>
>Thanks,

Never seen a simple installation of Exchange 2007 do that to a server.
Was this box the (a) DC or a member? It wasn't quite clear from the
message and it shouldn't make a difference but it's good to ask as DNS
problems were involved.
Did you stop and disable all the Exchange services and do a reboot to
see if it was the existence of Exchange or that the box didn't like
the Exchange services running?

Jim
Tue Nov 13 07:28:15 PST 2007

It's a member server. Spent a lot of time chasing DNS issues including
completely deleting and recreating my zones. Not sure that I did try
disabling all of the Exchange services. I'm still chasing one possible
issue where a DC tries to look up 127.0.0.1 on a forwarder (below) so
it could still be DNS, but no other servers or clients have any problem
and uninstalling Exchange fixed it immediately.

When I run the Exchange installer again now I immediately get an event
2152 "An remote procedure call (RPC) request to the Microsoft Exchange
Active Directory Topology service failed with error 1753 (Error 6d9
from HrGetServersForRole). Make sure that the Remote Procedure Call
(RPC) service is running. In addition, make sure that the network ports
that are used by RPC are not blocked by a firewall."

DCDIAG /test:dns
DNS server: 208.67.220.220 (<name unavailable>)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the
1.0.0.127.in-addr.arpa. failed on the DNS server 208.67.220.220
--



Mark Arnold [MVP] wrote:

> On Mon, 12 Nov 2007 09:46:33 -0600, Jim <nospam@any.time> wrote:
>
> > Hi,
> > I installed Exchange 2007 on a 2003 R2 server. Subsequently logging
> > in to the server took a long time and it turns out that GPOs were
> > not applied since a domain controller could not be found. Web
> > browsing from the server also did not work. Exchange event log
> > reported that it could not access AD. After several days chasing
> > DNS issues I have uninstalled Exchange 2007 (a major undertaking)
> > and the server is back to normal. No other servers or clients had
> > any AD problems at any time. Has anyone experienced this and found
> > a solution? I need to install Exchange 2007 on this server but not
> > if it breaks things.
> >
> > Thanks,
>
> Never seen a simple installation of Exchange 2007 do that to a server.
> Was this box the (a) DC or a member? It wasn't quite clear from the
> message and it shouldn't make a difference but it's good to ask as DNS
> problems were involved.
> Did you stop and disable all the Exchange services and do a reboot to
> see if it was the existence of Exchange or that the box didn't like
> the Exchange services running?