Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

DC removed from domain without dcpromo

Status
Not open for further replies.

julianf

IS-IT--Management
Nov 26, 2001
184
ZA
Hi,

We have a WAN environment. One of the sites was decommisioned about 6 months ago. WE brought the exchange server back to the main site. This was placed onto the network to host the mail for the users that were at the remote site. We did not place the remote site's DC back onto the network. This DC has been offline for 6 months. I did not dcpromo the dc off the domain.

After 6 months, we have experienced a problem on exchange at the main site. I created a new user with a mailbox. I can log on as the new user and open his mailbox. I can send mail to internal users, but the new user cannot receive any e-mails from internal or external. I checked the users properties and noticed that it has not created the usualy default e-mail addresses. I.e. user@domain.com; x400..etc.

Active directory in conjuction with the recipient update service usually automatically creates these e-mail addresses under the new user. It is no longer happening. I created a few more test accounts (from both local exchange servers), but to no avail.

The only change that has happened recently was when we migrated another remote site into their own domain. We therefore went into the main exchange server and modified the recipient update service and recipient policy. (We basically removed the entries for the remote site that was migrated)

I suspect that the problem we are experiencing is to do with the changes that were made to the RUS this week. My colleagues believe that the problem is to do with the DC that has been offline for 6 months. I have placed the DC back onto the network, but it is horribly out of date with regards to DNS and AD. I am not even sure if replciation will occur to bring it back up to speed, since it has been offline for so long.

Any suggestions?
 
Update:

It appears as if the token for the problematic DC has expired on the domain due to it being offline for so long. Through a manual process we have enabled it to communicate with AD again. We are now in the process of removing it from the domain via dcpromo. Hopefully once this is done, we will be able to re-create the RUS and fix the problem.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top