Help!
I'm unable to add a new TCP/IP MTA Transport stack in
exchange 2000 service manager. When I right click on the
MTA container I don't have the option of add a new stack
of any kind. Any Ideas?
Many Thanks
Richard
2. Exchange 2000 MTA Service did not Start
Hi, Exchange 2000 MTA Service did not start . This failed to give an error. The problem persists. There are no specific events being logged in the Event Viewer. Does anyone have an idea as to what could be the reason. Ankur.
4. Information Store and MTA stacks not starting on Exchange 2000
5. MTA Stacks won't start on exchange 2000 cluster
6. Missing MTA and SA in Exchange 2000
Hi All, Can anyone help for the following problems 1.MTA service is visible in Services on a exchange 2000 with SP3 server running Windows 2000 SP3. 2.MicrosoftSA service is also not visible in Services Because of these 2 reasons Exchange server is unable to process mails Pls advice matter urgent-- Regards Arun
7. Exchange 2000 won't start the 'MTA Stack Service'
8. Exchange 2000 Server as MTA for Multiple Domains
Is it possible to have Exchange 2000 Server integrated with existing Active Directory and process mail for two domains? The existing domain name is win.company.net, using a single domain controller. The exchange server is a member of this domain, named server1.win.company.net. The exchange server's Recipient Policies allow it to process mail for the domains, win.company.net and company.com. (Both "company" names are the same). The exchange server is currently only used on the internal network an is used for internal mail, calendaring and internal public folders. External mail is processed on a Linux platform that uses the company.com domain name and the Outlook clients pull mail from both sources. Management would like to get rid of the two server configuration and prefers Exchange. Could we simply install another NIC in the Exchange Server; place this new interface in the DMZ; name that interface server1.company.com, assign it a public address and route all SMTP traffic to that hostname via a hole in the firewall which only allows SMTP traffic to that host and still retain both the internal functionality we currently have, and receive mail from both company.com and win.company.net, without tearing down the current Active Directory infrastructure, renaming and rebuilding it?