Exchange 2003
I am having some trouble with my newly built exchange 2003 server. I am unable to connect to it from the workstations in the domain. Im a sys admin for a community college. We are doing a domain migration. Ive got the workstations working with everything except the exchange server. I just builtthe exchange servertoday. I can ping by name, connect to shares, I can telnet to port 25 and get: 220 conted2.acns.stchas.edu Microsoft ESMTP MAIL Service, Version: 6.0.3790.3959ready at Tue, 7 Aug 2007 16:18:13 -0500 (not worried about names as they are all internal without outside access) I followed the setup directions exactly as it was shown from the checklist on the setup cd. We are using server 2003 and exchange 2003. The error message i get from the workstations vary but all have "The connection to microsoft Exchange is unavailable". It will not work from any computer I have tried so far, either with office 2003 or 2007. Previously we used a 2000 server and exchange 2000 without any problems. If there is any other info that anyone may need I will try and provide it. Any help is appreciated.
August 8th, 2007 12:31am

Jayhof, What is the current domain configuration of the two exchange servers? When attempting to connect are you use a new account that was created in the same domain as the exchange server with a mailbox on the new exchange 2003 server? Have you attempted to connect to the exchange server using OWA? http://servername/exchange Are there any relevant messages reported in the event logs of the new exchange 2003 server? Thanks
Free Windows Admin Tool Kit Click here and download it now
August 8th, 2007 5:29am

Currently they are 2 seperate mixed mode domains.2 seperate servers thatcan't even be able to communicate with each other. Using seperate dns anduser acounts etc. The exchange server is in mixed mode as well. We basically only have the old domain up to service a few rooms with logons and printers until we can get them changed over to the new domain. Yes a new acount that was created before exchange was installed to the new domain, there ae 36 user acounts that we use for outlook classes. For the domain tasks on the user acount all I can do is Remove exchange attributes. OWA is not working, it did not create a virtual dir in IIS. So it gets the page not found error. I also noticed this morning that when looking at the default properties within Internet message formats, a error message comes up saying : Element not found. Facility: Win32 ID no: c0070490 Exchange System Manager There are no errors in the event viewer. I willclearit just to verify. I beleive that exchange did not install correctly. I followed the directions, ran the tools to verify that dns and AD worked correctly, ran domainprep and forestprep, and installed all updates. I did not install the exchange message and collaborating tools or the exchange 5.5 interface. Everything else was to of been installed. I guess now im going to need some documentation on how to correctly un-install exchange without it doing strange things to AD, then try re-installing it. Thank you again for you help.
August 8th, 2007 4:27pm

I got it working. It seems that was a few things. First off I had installed the asp.net framework before IIS had been installed. So thats why it wouldnt work with OWA. Second the installer allowed me to install exchange with out the messageing and collaborating services. Which im assuming now is required for correct functionality. But after doing a fix for the asp.net and un-installing then re-installing exchange It seems that everything is working now. I can send emails to the different users acounts so I am happy. Thank you again for your help.
Free Windows Admin Tool Kit Click here and download it now
August 8th, 2007 7:10pm

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

Other recent topics Other recent topics