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 gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Local systems can almost (but not quite!) connect to Exchange

Status
Not open for further replies.

RileyL

IS-IT--Management
Mar 18, 2007
1
US
I'm the very new, very inexperienced net admin for a small high school, and our Exchange server (set up by someone else (now gone) two years ago) was recently fried, losing everything on it. We have backups of the mail stores, but not the actual configuration that was making mail work. So now I'm trying to set up another machine to handle mail. So far, it receives incoming email (I can tell from the "Tracking" tool in the server manager), but I cannot for the life of me get Outlook to connect to it. OWA is also broken. All services report that they are running as expected.

The network topography:

We have DSL coming into an ISA server that acts as a firewall, domain controller, and dns server. That's connected to our internal network, which eventually gets to a machine called "Intranet," which, before the crash, was just a file server, the DHCP server, and a secondary DC. This is the machine onto which I've tried to install Exchange Server 2003 w/ SP2. Both servers are running Windows Server 2003 SP2.

So, it seems like there's no problem actually reaching the exchange server. DHCP is still working fine across the network, and as I said, incoming mail is clearly getting to it. I have had to do a lot of hacking at the Active Directory to get it to forget about the old server, and I fear that I've screwed something up (or neglected to change something from the old server to the new server). Do I have to set something somewhere saying, "Hey, here's my exchange server, please connect to it?"

When I try to connect with Outlook: it CAN connect enough to resolve my name. That is, when I'm adding a new email account to Outlook, it asks for the exchange server and the user name, and it successfully validates the user name. However, after it gets to that point, it complains that it isn't connected to the exchange server and asks me how I could possibly expect it to work when it isn't connected to the exchange server!

When I try to connect to OWA (from inside): HTTP Error 401.1 - Unauthorized: Access is denied due to invalid credentials.


I experimented briefly with configuring "Intranet" as a front-end server, but then had to change it back to get the RUS stuff working.


Does anyone have any ideas about what I can do, or just check? I've been working on this for three days now and my brain is pretty burnt out. Thanks!
 
Is DNS configured for private or public addresses on the ISA box? I wondering if perhaps it is resolving to the public IP address of the Exchange server, and your clients are having to try and come through the firewall to access the server. Just ping the server name and see what address comes back.

Ben Christian
MCSE, MCSA:Messaging
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top