Lots of times, sad to say it, have I seen horrible things happen to the Outlook Anywhere, Exchange webmail, and smartphone connection capability of SBS 2003. Microsoft telephone techs have huge lists of settings to check. Unfortunately, so far as I have been able to ascertain, we don’t. Today something interesting happened which seemed worth keeping. Here’s the scenario:
- Outlook Anywhere didn’t work to the newest clients running Outlook 2003, but did work to three or four of the older ones. Many things were tried. It became a working theory, that the server was behind some of the clients in critical updates, perhaps some involved in authentication between clients and Exchange.
- Found that the SBS 2003 server needed lots of updates, including several to Exchange. Installed all of them except the .NET and IE 8.
- After the updates, Exchange and the related services didn’t work at all. Rebooted. No change.
- Restarted Exchange services. Exchange began working to Outlook clients. No webmail, Outlook Anywhere, or smartphones.
- All three of the above, depend on IIS for data transfer. Studied IIS.
- “Default Web Site” was not running, all the others were. “Default Web Site” contains all of the things we need, including “Exchange”, “Exweb”, “OMA”, and others. ## Checked all of them, made sure that all IPs were permitted access.
- Tried to turn on “Default Web Site”. It said there was an IP conflict with one or more of the others.
- Turned off all of the others.
- Turned on “Default Web Site”. Worked that time.
- Tested. Webmail and the others still not working.
- Restarted IIS. Bits of Exchange and other things restarted along with it.
- Tested. Still didn’t work.
- Decided to lay things down, get some help elsewhere, possibly a call to Microsoft.
- Five minutes later, received a call. Everything working!!!