1

I had a test Exchange 2007 system in Microsoft VPC which I had converted to VMware ESXi format. However when I powered on the machine it was automatically using the default VLAN which is connected to the live network. Because running under VMware effectively changed the "hardware" of the machine, this resulted in a change of the network adapter so I lost the static IPs and it picked up a new IP from the live network. I can only imagine that this screwed up DNS, AD and Exchange.

So I created a new VLAN which holds a 'local only' network, configured IP as before but now Exchange cannot start. I keep getting 1053 errors (service cannot start in a timely fashion). I see nothing relevant in the event viewer. I have a gut feeling it is a DNS problem, but the settings looks fine to me.

Can anyone help?

3
  • 1
    Which Exchange service is it that cannot start?
    – Sam Cogan
    Commented Jan 15, 2010 at 11:18
  • Does the Exchange server have connecticvity to the same network that the DC is on, or is Exchange installed on the DC?
    – joeqwerty
    Commented Jan 15, 2010 at 14:31
  • I can start AD Topology, Information Store, Service Host and System Attendant. All the other Automatic services won't start, including Transport. Error 1053. Exchange is not on the DC and both machines can see each other.
    – Fred
    Commented Jan 15, 2010 at 14:47

1 Answer 1

0

Exchange must be able to see the Active Directory to which it's organization is installed.

If you have a different domain in this localized environment, you'll have to prepare this domain:

setup /PrepareAD [/OrganizationName: ]

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .