asked on

Problem in DC and Exchange after migration

Hello Experts,

I have a Windows 2003 SP2 Enterprise server with Exchange 2003 SP2 serving about 10 users only.

I was trying to migrate to Windows Server 2012 Essentials. After I setup the new server and did the migration, I found that Essentials 2012 doesn't support Exchange as 2011 does. Then I demoted the new 2012 and removed it from the domain and re-formated it to install the Windows 2008 R2 on it.

Their are two problems now:

1. Emails are no longer working.
2. I receive an error when a new computer tries to join the domain saying to check DNS settings. DNS settings are correct and the old DC is acting well as a DNS server for forwarding DNS requests to the outside.

I have a backup of the old DC 2003 but I will lose some data if I restore it.

What shall I do now?

SOLUTION

Simon Butler (Sembee)

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Muhajreen

ASKER

Thank you.

Yes I have restarted the server.

I have transfered the 5 FSMO roles back to the old DC before demoting the new one.

How to check if it's a global catalog?

Simon Butler (Sembee)

This is how to check:
http://technet.microsoft.com/en-us/library/cc786686(v=ws.10).aspx

Simon.

Muhajreen

ASKER

I found it wasn't a global catalog.

I have checked the check box of (global catalog) and restarted the server. After that, the problem is still there.

In the Active directory sites, in Servers, I found the demoted server is still there but contains nothing. Shall I delete it?

Simon Butler (Sembee)

You can remove it if there is nothing under it.
What did you restart? The domain controller or the Exchange server?

Simon.

Muhajreen

ASKER

I have restarted the machine. The same is DC and Exchange.

Muhajreen

ASKER

Note: This information is intended for a network administrator. If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\Windows\debug\dcdiag.txt.

The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain "ourdomain.com":

The error was: "This operation returned because the timeout period expired."
(error code 0x000005B4 ERROR_TIMEOUT)

The query was for the SRV record for _ldap._tcp.dc._msdcs.ourdomain.com

The DNS servers used by this computer for name resolution are not responding. This computer is configured to use DNS servers with the following IP addresses:

192.168.100.10

Verify that this computer is connected to the network, that these are the correct DNS server IP addresses, and that at least one of the DNS servers is running.

Simon Butler (Sembee)

That error means what it says.
Is the DNS server service running on the server?
Is the IP address shown correct? Check the server's IP address is correct.

Simon.

SOLUTION

Sandesh Dubey

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Muhajreen

ASKER

dcdiag /q has no output s follows:

C:\Documents and Settings\me>dcdiag /q

C:\Documents and Settings\me>repadmin /replsum
Replication Summary Start Time: 2013-06-24 18:04:36

Beginning data collection for replication summary, this may take awhile:
....

Source DC largest delta fails/total %% error

Destination DC largest delta fails/total %% error
Assertion

Server's IP address is correct and DNS is working.

What about IPv6 ? Shall it be available in the old dc after the new one may has used that?

Sandesh Dubey

The health of DC look good from the output.As old DC is Win2003 IPV6 is not required.Can you post the ipconfig /all details of DC and problematic client computer.

Have a look at this KB too:http://support.microsoft.com/kb/331072

Muhajreen

ASKER

DC:

Windows IP Configuration

Host Name . . . . . . . . . . . . : dc
Primary Dns Suffix . . . . . . . : ourdomain.com
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : ourdomain.com

Ethernet adapter Internal:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Embedded Broadcom NetXtreme 5721 PCI-E Gi
gabit NIC
Physical Address. . . . . . . . . : 00-1B-78-D2-3C-47
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.100.10
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.100.12
DNS Servers . . . . . . . . . . . : 127.0.0.1

Client:

C:\Users\Administrator>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : WIN-0UA4T5JDBB0
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Virtual Machine Bus Network Ada
pter
Physical Address. . . . . . . . . : 00-15-5D-64-0E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::541:90d9:4595:63cd%12(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.100.16(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.100.12
DHCPv6 IAID . . . . . . . . . . . : 251663709
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-59-FA-62-00-15-5D-64-0E-01

DNS Servers . . . . . . . . . . . : 192.168.100.10
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{3FCDF93B-FC17-4A1D-A202-E3B2DFA2F7C7}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 9:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Teredo Tunneling Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

zackmccracken

is the dns server listening on the 100.10 ip?
check the settings within the dns server, properties of your server and interfaces tab

are you using a physical server or vm's ?

ASKER CERTIFIED SOLUTION

Muhajreen

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Muhajreen

ASKER

Finally everything is working fine without Hyper-V