I don't know what happened. I'm very much a "newbie" at Microsoft Server administration. I'm an old UN*X guy and am used to configuration scripts and the like. I have a ton of issues at present with my MS Windows 2003 SBS server, but Exchange 2003 happens to be one of them. I am running Office 2007 Enterprise (which, of course, includes Outlook 2007) on my Windows Vista x64 computer as the mail client. I am running Office 2004 for Mac (using Entourage 2004 for the Mac OS X mail client). I had backed up several of my old "profiles" from Linux servers and just manual copy backup to grab my individual pst files (rge for Entourage) and store them on my backup drive. I was in the middle of working with Outlook 2007 on my Vista machine and opening the individual pst files and copying the mail/calendar/etc to the Exchange 2003 server. As was going well until I opened one Outlook.pst file, copied everything over and then got a warning about something about the synchronization with the exchange server would be interrupted when I tried to close the Outlook.pst file (folder in Outlook). I waited a while thinking it might still be syncing to the Exchange Server, but after a while it still gave me the same error. I closed the file (folder) and found out that it disconnected me from my Exchange Server. I tried to reconnect manually, but it didn't work. The strange thing was that Entourage 2004 (Mac OSX) was not being tampered with at all and it too lost it's connection to the Exchange Server2k3. However, my wife's email account is fine. That computer is running Windows XP Pro (32-bit) and is also running Microsoft 2007 Enterprise edition. Her connection to the exchange server is fine. I haven't tried my account on that box yet. I haven't tampered with that box either. Any ideas? There is another issue that is more Server 2003 SBS SP1 related, but may give a clue. I can connect to the server from the intranet using http://[server name]. However, it tries to bring up http://companyweb and I get a DNS error. Never had a problem before the Exchange server issue (at least, I don't think so).