Can't mail enable
Posted on 2004-09-22
I'm attempting to install an exchange server as a replacement for our current SLMail server. The SLMail server is running in a NT4 domain. I have installed two new DCs and created an Active Directory domain (on the same subnet). The new AD domain will be the target domain for the migration. The plan is to migrate the SLMail from the old NT4 domain to the new AD domain that I have recently created. Upgrading is not an option, because management wants to keep the current domain in production and the target domain is to have a new name.
The NT4 domain did not have DNS, WINS or DHCP installed locally. The PDC was pointing to an external source for DNS. I've recently installed DNS and WINS locally in the NT4 domain in order to perform NetBIOS and DNS name resolution for the migration. It appears that local DNS and WINS are working correctly in the NT domain.
In the target AD domain I have also installed WINS (and obviously DNS). I have also established a trust relationship to-and-from both domains. Name resolution in the target domain seems to be in good working order as well. (the event logs are happy)
Exchange has been installed in the target domain on a member server named "Mail." I've run forest and domain preps, but when viewing the advanced features in ADUC, it does not appear that the schema was extended to include the Exchange tabs for user accounts.
Also - I cannot use the Internet Mail Wizard to mail enable users. It passes the prereq test. I want this server to be able to send and recieve email, but it errors with a "To send Internet email, the selected server cannot be a bridgehead server." id no c103b530.
In this small network environment and we are not yet utilizing DMZ topology, so there is only one firewall and it is the gateway. Both domains are using the same gateway, and the exchange server is not a clustered server. Exchange is installed on only one server in the new AD domain.
How do I get around this bridgehead error message to mail enable my users? Any direction regarding this issue would be greatly appreciated.