2008 to 2012 Domain Migration - Exchange Issues
Small home network. Server is a HP ML150 running ESXi 5.0.
Brought up a 2012 R2 vm box [DC2], turned it into a DC following the technet articles. Then I demoted my 2008 R2 DC vm [DC1]. All physical PCs work fine (log in/out, DHCP, DNS,...) and each can get to my 2012 R2 file/print server [FS2]. (also a vm)
The issue is with my Exchange 2010 on 2008 R2 [MAIL]. (also a vm)
Following the upgraded DC, mail had become inaccessible, login failures.
On the server, services show:
MS Exch. Address Book Starting
MS Exch. EdgeSync Stopping
MS Exch. Information Store Stopping
MS Exch. POP3 Stopping
MS Exch. RPC Client Access Starting
...
Also, when I try to go into "Network and Sharing Center", it hangs for a LONG time, but does eventually go in.
Verified all the DNS entries on the server are correct. (both point at DC2's IP, only)
IPCONFIG's are attached for the DC2 and MAIL servers.
MAIL.PNG
DC2.PNG
Brought up a 2012 R2 vm box [DC2], turned it into a DC following the technet articles. Then I demoted my 2008 R2 DC vm [DC1]. All physical PCs work fine (log in/out, DHCP, DNS,...) and each can get to my 2012 R2 file/print server [FS2]. (also a vm)
The issue is with my Exchange 2010 on 2008 R2 [MAIL]. (also a vm)
Following the upgraded DC, mail had become inaccessible, login failures.
On the server, services show:
MS Exch. Address Book Starting
MS Exch. EdgeSync Stopping
MS Exch. Information Store Stopping
MS Exch. POP3 Stopping
MS Exch. RPC Client Access Starting
...
Also, when I try to go into "Network and Sharing Center", it hangs for a LONG time, but does eventually go in.
Verified all the DNS entries on the server are correct. (both point at DC2's IP, only)
IPCONFIG's are attached for the DC2 and MAIL servers.
MAIL.PNG
DC2.PNG
Is your exchange 2010 with SP3 roll up 5? Windows Server 2012 R2 Active Directory environments, requires exchange 2010 with SP3 roll-up 5.
Zac.
Zac.
ASKER
Cliff Galiher: There were a bunch of "dead" static entries in DNS for _ldap pointing to DC1. Deleted. (DC2 was also listed in each case)
Still no joy. ;-(
Still no joy. ;-(
ASKER
Zacharia Kurian: I dont believe so. All I can find (Exchange Management Console can't connect) is version 14.00.0722.000 in the Help/About.
ASKER
Thinking I am getting closer though. Got a red "X" on the network icon in the system tray.
Network Sharing and Control panel hangs for a LONG time (10-20min) before opening, pic attached.
However, as seen in the earlier pic, all settings are good.
I can also ping all internal servers, router, and outbound.
Odd...
MAILx.PNG
Network Sharing and Control panel hangs for a LONG time (10-20min) before opening, pic attached.
However, as seen in the earlier pic, all settings are good.
I can also ping all internal servers, router, and outbound.
Odd...
MAILx.PNG
ASKER
Cliff Galiher: I also did try the IPCONFIG /flushdns, still no love.
Think there is something I am missing in the network settings, but damned if I can find it.
Router 172.30.100.1
Subnet 255.255.255.1
DNS 172.30.100.5 (for DC2 that I entered) and 127.0.0.1 (automatically entered when I left the second DNS blank)
Think there is something I am missing in the network settings, but damned if I can find it.
Router 172.30.100.1
Subnet 255.255.255.1
DNS 172.30.100.5 (for DC2 that I entered) and 127.0.0.1 (automatically entered when I left the second DNS blank)
Did you reboot the exchange server after cleaning up th old DNS records?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Cliff Galiher: Yes, was able to shut down nicely and reboot. Still getting spinning blue circle on the network indicator for 15min and then a red X.
The only time you'll get a red x is when the network card thinks there is no network at all. Even a single cable to a switch will show a yellow alert instead of red. Your issue isn't currently with exchange, but is a core networking failure. Physical or bad driver or similar.
ASKER
Yeah, the new VMXNET3 card is doing the same thing. Ugh.
Seems I am going to need to find how to migrate the Exchange database to a new server without them being able to communicate...
Seems I am going to need to find how to migrate the Exchange database to a new server without them being able to communicate...
Is the red x relatively new? It was not a symptom you listed in your original question and knowing when that started occurring could help.
ASKER
Never mind, the drivers just hadn't installed. I have a "good" network icon and network behavior now!
Going to reboot and see if the Exchange Services start... brb.
Going to reboot and see if the Exchange Services start... brb.
ASKER
The red X was only new because it didn't appear until 20min after reboot. The spinning circle was all I saw at first.
:-)
:-)
ASKER
I've requested that this question be closed as follows:
Accepted answer: 0 points for kitmax's comment #a40729051
for the following reason:
Was the root problem to my original issue.
Accepted answer: 0 points for kitmax's comment #a40729051
for the following reason:
Was the root problem to my original issue.
ASKER
Fixed my original issue, but now after updates started flowing again, I get stuck at "Applying settings..." which looks to be a common issue. Love you MS.
Think this VM is hosed, and I want to get to 2012 R2 anyway, so I'll start working on how to migrate MS-Exchange without the old server "viable". (I can mount the drive in the other VM and access the database I am sure.
Thanks to everyone who replied, all were good and helpful suggestions. These forums rock!
Think this VM is hosed, and I want to get to 2012 R2 anyway, so I'll start working on how to migrate MS-Exchange without the old server "viable". (I can mount the drive in the other VM and access the database I am sure.
Thanks to everyone who replied, all were good and helpful suggestions. These forums rock!
If that doesn't work, did you go through the DNS server and remove the records for the old DC? Demoting a DC does *not* automatically do this, so your exchange server could still be attempting to connect to its "preferred" DC and services are timing out.