First Time Exchange 2003 Installation - Issue sending emails internally.
Hello All, I have been tasked to setup a Windows 2003 Server running Exchange Server 2003. This is my first time using and setting up Exchange and I have a few questions. The Windows 2003 Server I setup is brand new and is running Exchange Server 2003, I have installed it with relative ease. I have setup the domain (This server is also the domain controller). I also followed steps from this website: http://www.christensen-software.com/support/config_exchange_2003.htm However when I try and send emails via it the emails don't seem to get through (Even if i send to local users). You can see below how I am sending them (with email address blanked out): 220 xerver.blank.co.uk Microsoft ESMTP MAIL Service, Version: 6.0.3790.3959 ready at Fri, 6 Mar 2009 17:05:13 +0000 helo 250 xerver.blank.co.uk Hello [192.168.1.245] mail from: roosb@blank.co.uk 501 5.5.4 Invalid Address helo 250 xerver.blank.co.uk Hello [192.168.1.245] mail from: rossb@blank.co.uk 250 2.1.0 rossb@blank.co.uk....Sender OK rcpt to: administrator@blank.co.uk (This being the local account) 250 2.1.5 administrator@blank.co.uk data 354 Start mail input; end with <CRLF>.<CRLF> test! . 250 2.6.0 <EXCH-VLQSIP52vK5i4K0000000b@xerver.blank.co.uk> Queued mail for delive ry any help would be appreciated!
March 6th, 2009 8:17pm

Hi,Please check the queue's in Exchange if the mail is in there. From the logging you have posted I can see the message is accepted for delivery so it should get delivered.This can be checked by opening the Exchange System Manager and the expand the First Storage Group and servers. Expand the server and check the option queues.Another recommendation is to run the Exchange Best Practice Analyzer, this will check your Exchange environment and will give you some tips on what you can do to solve issues/enhance your Exchange environment.Regards,Johanblog: www.johanveldhuis.nl
Free Windows Admin Tool Kit Click here and download it now
March 7th, 2009 12:13am

I have checked the queues and they are empty.One thing I did check was the mailboxes as per the Exchange. If you look at my screenshot:www.wosixe.com/mailbox.GIFYou will notice that there are items there. If i check the mailboxes via Outlooks Web Access they show nothing. My next step is to hook up Outlook and see whats going on.Do you know of a reason why OWA would not show emails? Is there another way I can check mailboxes without connecting Outlook or OWA?Thanks for the mention regarding the Exchange Best Practise Analyzer. I have installed and run this and it returned a few issues, but only two 'critical issues' which were to do with the fact that my server doesnt have a DNS entry in my DNS server and that I am running this in a VMware session. Nether of them I dont think should effect the sending of mail internally.
March 7th, 2009 3:33pm

you can check the mailbox statistics to see what is in the mailbox.Regarding your issue though, if this is Exchange 2003 check your RUS and make sure your email address policies are being applied. It nearly sounds like email addresses are not being applied at all.BP
Free Windows Admin Tool Kit Click here and download it now
March 9th, 2009 4:54pm

Dear stuaz, You should know we dont support this case, which you install Microsoft software on third party virtualization software. Support policy for Microsoft software running in non-Microsoft hardware virtualization software http://support.microsoft.com/kb/897615/en-us Exchange server running under VMware http://technet.microsoft.com/en-us/library/aa996993.aspx However, I would like to provide some information for your reference: 1. Did you receive NDR? 2. Check whether Exchange-related services started, such as information store? 3. Enable message tracking and track the message: Related articles: Delivery status notifications in Exchange Server and in Small Business Server http://support.microsoft.com/kb/284204/en-us XADM: Using the Message Tracking Center to Track a Message http://support.microsoft.com/kb/262162/en-us How to troubleshoot for Exchange Server 2003 transport issues http://support.microsoft.com/kb/821910/en-us mail flow troubleshooter: http://www.microsoft.com/downloads/details.aspx?familyid=4BDC1D6B-DE34-4F1C-AEBA-FED1256CAF9A&displaylang=en Thanks for your cooperation and understanding. Regards, Rock Wang Rock Wang MSFT
March 10th, 2009 5:10am

Hi Stuaz,There are many things which need to be checked.....Make sure that you DNS is working correctly, Forward and Reverse.Have created a proper email address policy for your organization.How you are testing mail routing? even if oyu don't configure any thing in exchange and create a users, local mail routing should work (using MAPI client or web access).The communication you have mentioned is smtp session which comes in picture when you are configuring SMTP & POP clients or your exchange is sending mails to smart host or directly to internet. Please let me know how you are sending mails to internet directly or through smart host.Then you need to create a smtp connector, which will define that how mails will route to internet which is not local (Your internet domain) and based on the configuration mails will be routed.Abhishek
Free Windows Admin Tool Kit Click here and download it now
March 12th, 2009 9:02am

Hello there, thanks for your response. I have a little update: While I can send and receive mail fine via OWA, and I have managed to at least get outlook to recognise server, upon opening it I get a message stating: "Cannot start Microsoft Outlook. Cannot open the Outlook window. The set of folders cannot be opened. The attempt to log onto Microsoft Exchange has failed" The server is up and running, and I can ping and RDP onto it fine. This happens with more than one user accounts - and even newly created ones.
March 12th, 2009 8:03pm

Dear stuaz, You can try to perform the following steps to fix the issue: 1. Did you use Exchange account or POP3 account in Outlook? 2. Delete Outlook profile and recreate a new one, and check the effect. 3. Recreate a new Outlook profile on another computer, check the result, 4. Restart Exchange server and make sure all Exchange-related services start, and check the effect. 5. Check whether there is a firewall between the client and Exchange server, if so, disable the firewall and check the effect. 6. Install Portqry.exe on the client, then run the following command, send the result into the forum: portqry -n mymailsrv -p udp -e 135 Note: replace mymailsrv with your Exchange server name. How to Use Portqry.exe to Troubleshoot Microsoft Exchange Server Connectivity Issues http://support.microsoft.com/kb/310298/en-us Regards, Rock WangRock Wang MSFT
Free Windows Admin Tool Kit Click here and download it now
March 13th, 2009 10:44am

Dear All can you please let me know step by step if we want to replace the exchange server 2003?
September 27th, 2010 11:42am

Dear Johan can you please let me know step by step how replace the exchange server 2003 which is runningout the warrenty?
Free Windows Admin Tool Kit Click here and download it now
September 27th, 2010 11:45am

Hi, Have a look at this article: http://www.simple-talk.com/sysadmin/exchange/upgrade-exchange-2003-to-exchange-2010/ Regards, JohanExchange-blog: www.johanveldhuis.nl
September 27th, 2010 11:48am

Dear Johan can you please let me know step by step how replace the exchange server 2003 which is runningout the warrenty? Hi, You need to introduce new exchange 2003 server in existing exchange organization. Move mail boxes and OAB generation process to new Server. Keep it running for 24-48 hours after the moving OAB to new server. Uninstall old exchange server. For exchange 2003 process is quite simple and easy. Abhishek
Free Windows Admin Tool Kit Click here and download it now
May 9th, 2011 6:51am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics