<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" 
  xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
  xmlns:admin="http://webns.net/mvcb/"
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">

<channel>
<title>Ravings of an Intermittent Fool - The Microsoft Exchange Server computer is not available</title>
<link>http://people.etango.com/~markm/archives/2004/05/21/the_microsoft_exchange_server_computer_is_not_available.html</link>
<description>Comments on the entry "The Microsoft Exchange Server computer is not available"</description>
<dc:language>en-us</dc:language>
<dc:creator>mark.mascolino@gmail.com</dc:creator>
<dc:date>2004-05-21T12:14:59-05:00</dc:date>
<admin:generatorAgent rdf:resource="http://www.movabletype.org/?v=3.33" />
<sy:updatePeriod>hourly</sy:updatePeriod>
<sy:updateFrequency>1</sy:updateFrequency>
<sy:updateBase>2000-01-01T12:00+00:00</sy:updateBase>

<item>
<title>The Microsoft Exchange Server computer is not available</title>
<link>http://people.etango.com/~markm/archives/2004/05/21/the_microsoft_exchange_server_computer_is_not_available.html</link>
<description>I got this error message today when firing up MS Outlook:
Cannot start Microsoft Outlook.  The Microsoft Exchange Server computer is not available.  Either their are network problems or the Microsoft Exchange Server computer is down for maintenance.
I&apos;m not sure what I like more, the passing of the buck to the network or the total lack of acknowledgement that the Exchange server could have crashed.</description>
<guid isPermaLink="false">231@http://people.etango.com/~markm/</guid>
<dc:date>2004-05-21T12:14:59-05:00</dc:date>
</item>


<item>
<title>Ron Witte comments on The Microsoft Exchange Server computer is not available</title>
<link>http://people.etango.com/~markm/archives/2004/05/21/the_microsoft_exchange_server_computer_is_not_available.html#001192</link>
<description>I got this same message today. Can you by any chance tell me how you resolved this issue? Any help would be much appreciated.

Thanks in advance,

Ron</description>
<guid isPermaLink="false">1192@231@http://people.etango.com/~markm/</guid>
<dc:date>2004-10-27T16:21:33-05:00</dc:date>
</item>
<item>
<title>Paul Hewitt comments on The Microsoft Exchange Server computer is not available</title>
<link>http://people.etango.com/~markm/archives/2004/05/21/the_microsoft_exchange_server_computer_is_not_available.html#014858</link>
<description>I changed to broadband recently and now when I click on Microsoft Outlook I get a Microsoft Exchange Server not available notice and can only get my email by going onto web access to BT Yahoo outlook.
Any suggestions or solutions? PLEASE!

Paul</description>
<guid isPermaLink="false">14858@231@http://people.etango.com/~markm/</guid>
<dc:date>2006-04-19T21:26:46-05:00</dc:date>
</item>
<item>
<title>Han Holtslag comments on The Microsoft Exchange Server computer is not available</title>
<link>http://people.etango.com/~markm/archives/2004/05/21/the_microsoft_exchange_server_computer_is_not_available.html#174169</link>
<description>The answer is very simple and frustrating,
set the DNS server of your client to the DNS server of your Exchange server.

The domain resolution wil work then. 
The outlook client is looking for a servername.doemainname.local and the normal DNS server does not know about the local domain. A ping wil work bur is useless in this situation

have fun ...
</description>
<guid isPermaLink="false">174169@231@http://people.etango.com/~markm/</guid>
<dc:date>2008-08-29T16:26:35-05:00</dc:date>
</item>
<item>
<title>Sasha comments on The Microsoft Exchange Server computer is not available</title>
<link>http://people.etango.com/~markm/archives/2004/05/21/the_microsoft_exchange_server_computer_is_not_available.html#181781</link>
<description>I have the same Problem, can&apos;t connect to microsoft exchange... what the deux?</description>
<guid isPermaLink="false">181781@231@http://people.etango.com/~markm/</guid>
<dc:date>2008-11-06T01:26:37-05:00</dc:date>
</item>


</channel>
</rss>