I'm trying to install Exchange 2007 with SP3 on a Windows 2008 Enterprise R2 server that's also acting as an AD domain controller (yes, start flaming me, I know what's best practice but I don't have a choice, short on funds). During the installation of the Hub Transport Role, the install fails with an error that it cannot start the Microsoft Exchange Transport service. The specific error within the event log is "Microsoft Exchange couldn't read the Receive connector configuration. The service will be stopped." Preceding this error was MSExchange ADAccess error 2101, "Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=4944). The configuration domain controller specified in a call to SetConfigDCName (server1.domain.local) is unreachable. Exchange Active Directory Provider will select the configuration domain controller from the list of available domain controllers." This is odd because I'm using the server itself as the domain controller and I have it configured within the correct site with the local subnet. There are 2 other remote domain controllers configured with their own site and subnet as well. Any ideas? thanks.

On Sun, 11 Jul 2010 21:28:24 +0000, ronnieshih wrote: > > >I'm trying to install Exchange 2007 with SP3 on a Windows 2008 Enterprise R2 server that's also acting as an AD domain controller (yes, start flaming me, I know what's best practice but I don't have a choice, short on funds). During the installation of the Hub Transport Role, the install fails with an error that it cannot start the Microsoft Exchange Transport service. The specific error within the event log is "Microsoft Exchange couldn't read the Receive connector configuration. The service will be stopped." Preceding this error was MSExchange ADAccess error 2101, "Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=4944). The configuration domain controller specified in a call to SetConfigDCName (server1.domain.local) is unreachable. Exchange Active Directory Provider will select the configuration domain controller from the list of available domain controllers." > >This is odd because I'm using the server itself as the domain controller and I have it configured within the correct site with the local subnet. There are 2 other remote domain controllers configured with their own site and subnet as well. > >Any ideas? thanks. Did you disable IPv6? If you did, enable it and reboot the machine. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Just before you replied, I did find the solution that's exactly what you described! I resolved the issue by checking back the IPv6 option in TCP/IP properties of the NIC. thanks!