Re: Unable to connect to OWA and OMA

"frbas" <> wrote in message
news:...
>
> I am using a Windows Server 2003 with Exchange 2003 installed on it. We
> recently had some problems with IIS and Exchange. For a while were we
> unable to send and receive with Outlook and couldn't connect to OWA or
> OMA. I was able to fix the issue with outlook, the SMTP server wasn't
> properly associated with Exchange. We are still unable to access OWA or
> OMA I have tried both of these solutions:
>
> http://www.msexchange.org/tutorials/...tallation.html
>
> http://www.msexchange.org/tutorials/...ange-2003.html
>
> Neither one of them worked. You can ping the server and it responds. I
> seems like the servers is routing the requests for the OWA and OMA to
> the proper places in the server. Can anyone please help me?
>

This is better posted in the Exchange newsgroups.

However, have you tested your config at the Microsoft Exchange test site?

Microsoft Exchange Server Remote Connectivity AnalyzerSelect the test you
want to run: ... Exchange Remote Connectivity Analyzer has encountered an
error. The entire error report is listed below: Show Report ...
https://www.testexchangeconnectivity.com/

I don't know what happened to cause all the problems. Let us know what
caused the problems, or if you don;t know what caused them, post the
symptons as well as any Event log errors, if Exchange is installed on a DC,
if there is more than one NIC on the machine, (an unedited ipconfig /all
would be extremely helpful), we can diagnose why it *possibly* occured and
make suggestions and recommendations to fix it.

Or maybe simply reinstalling Exchange with the /disasterrecovery switch may
do the trick.

For your covenience, I cross-posted to microsoft.public.exchange.admin -
just check back in the general newsgroup for replies, but for the future,
Exchange questions are better posted to the Exchange newsgroups. Since you
are using Techarena, you will have to figure out where the Exchange section
is.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCTS Exchange, MCSE, MCSA 2003 & 2000, MCSA Messaging
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.

Thank, I didn't realize I was posting to a news group. I am now going
directly to the news group.

I don't know exactly what caused the issue, but I tried to install MS CRM on
to the exchange server. That messed the IIS settings. I I tried reinstalling
exchange and IIS but that didn't solve it. Honestly I tried so many things
to fix the issues, I don't know which one actaully fixed it. The last thing
I did, was revert to an older IIS web site, and renamed it Default Web Site
and that then fixed the issue with outlook. Now the only issues it with OWA
and OMA. Neither one of them will connect. I ran the tool you sent, below
are the reports from it. We have two servers, Windows 2003 working as DC and
a Windows 2003 running Exchange. I never changed any network settings
directly, while trying to fix any of the issues.

Thanks for the help.

I ran three of them, here is the reports from them.



Microsoft Exchange ActiveSync Connectivity Tests
Exchange ActiveSync with AutoDiscover:

Testing Exchange ActiveSync using the Autodiscover Service to obtain
Settings
Failed to test Exchange ActiveSync using the Autodiscover Service to
obtain Settings
Test Steps

Attempting AutoDiscover and Exchange Activesync Test (if requested)
Failed to test AutoDiscover for Exchange Activesync
Test Steps

Attempting each method of contacting the AutoDiscover Service
Failed to contact the AutoDiscover service successfully by any method
Test Steps

Attempting to test potential AutoDiscover URL
https://aspentechaz.com/AutoDiscover/AutoDiscover.xml
Failed testing this potential AutoDiscover URL
Test Steps

Attempting to Resolve the host name aspentechaz.com in DNS.
Host successfully Resolved
Additional Details
IP(s) returned: 216.119.81.119
Testing TCP Port 443 on host aspentechaz.com to ensure it is
listening/open.
The port was opened successfully.
Testing SSL Certificate for validity.
The SSL Certificate failed one or more certificate validation checks.

Tell me more about this issue and how to resolve it
Additional Details
A network error occurred while communicating with remote host:
Exception Details:
Message: Authentication failed because the remote party has closed the
transport stream.
Type: System.IO.IOException
Stack Trace:
at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32
readBytes, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer,
AsyncProtocolRequest asyncRequest)
at
System.Net.Security.SslState.CheckCompletionBefore NextReceive(ProtocolToken
message, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count,
AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ForceAuthentication(B oolean receiveFirst,
Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessAuthentication (LazyAsyncResult
lazyResult)
at System.Net.Security.SslStream.AuthenticateAsClient (String targetHost,
X509CertificateCollection clientCertificates, SslProtocols
enabledSslProtocols, Boolean checkCertificateRevocation)
at System.Net.Security.SslStream.AuthenticateAsClient (String targetHost)
at
Microsoft.Exchange.Tools.ExRca.Tests.SSLCertificat eTest.PerformTestReally()
Attempting to test potential AutoDiscover URL
https://autodiscover.aspentechaz.com...toDiscover.xml
Failed testing this potential AutoDiscover URL
Test Steps

Attempting to Resolve the host name autodiscover.aspentechaz.com in DNS.
Host successfully Resolved
Additional Details
IP(s) returned: 216.119.81.119
Testing TCP Port 443 on host autodiscover.aspentechaz.com to ensure it is
listening/open.
The port was opened successfully.
Testing SSL Certificate for validity.
The SSL Certificate failed one or more certificate validation checks.

Tell me more about this issue and how to resolve it
Additional Details
A network error occurred while communicating with remote host:
Exception Details:
Message: Authentication failed because the remote party has closed the
transport stream.
Type: System.IO.IOException
Stack Trace:
at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32
readBytes, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer,
AsyncProtocolRequest asyncRequest)
at
System.Net.Security.SslState.CheckCompletionBefore NextReceive(ProtocolToken
message, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count,
AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ForceAuthentication(B oolean receiveFirst,
Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessAuthentication (LazyAsyncResult
lazyResult)
at System.Net.Security.SslStream.AuthenticateAsClient (String targetHost,
X509CertificateCollection clientCertificates, SslProtocols
enabledSslProtocols, Boolean checkCertificateRevocation)
at System.Net.Security.SslStream.AuthenticateAsClient (String targetHost)
at
Microsoft.Exchange.Tools.ExRca.Tests.SSLCertificat eTest.PerformTestReally()
Attempting to contact the AutoDiscover service using the HTTP redirect
method.
Failed to contact AutoDiscover using the HTTP Redirect method
Test Steps

Attempting to Resolve the host name autodiscover.aspentechaz.com in DNS.
Host successfully Resolved
Additional Details
IP(s) returned: 216.119.81.119
Testing TCP Port 80 on host autodiscover.aspentechaz.com to ensure it is
listening/open.
The port was opened successfully.
Checking Host autodiscover.aspentechaz.com for an HTTP redirect to
AutoDiscover
Failed to get an HTTP redirect response for AutoDiscover
Additional Details
A Web Exception occured because an HTTP 404 - NotFound response was
received from IIS6
Attempting to contact the AutoDiscover service using the DNS SRV redirect
method.
Failed to contact AutoDiscover using the DNS SRV redirect method.
Test Steps

Attempting to locate SRV record _autodiscover._tcp.aspentechaz.com in DNS.
Failed to find AutoDiscover SRV record in DNS.






Microsoft Exchange ActiveSync Connectivity Tests
Exchange ActiveSync

Testing Exchange Activesync for host
https://mail.aspentechaz.com/Microso...er-Activesync/
Exchange Activesync test Failed
Test Steps

Attempting to Resolve the host name mail.aspentechaz.com in DNS.
Host successfully Resolved
Additional Details
IP(s) returned: 207.155.232.100
Testing TCP Port 443 on host mail.aspentechaz.com to ensure it is
listening/open.
The specified port is either blocked, not listening, or not producing the
expected response.

Tell me more about this issue and how to resolve it
Additional Details
A network error occurred while communicating with remote host:
Exception Details:
Message: No connection could be made because the target machine actively
refused it 207.155.232.100:443
Type: System.Net.Sockets.SocketException
Stack Trace:
at System.Net.Sockets.TcpClient.Connect(String hostname, Int32 port)
at Microsoft.Exchange.Tools.ExRca.Tests.TcpPortTest.P erformTestReally()







Microsoft Exchange Web Services Connectivity Tests
ActiveSync Provider AutoDiscover

Attempting AutoDiscover and Exchange Activesync Test (if requested)
Failed to test AutoDiscover for Exchange Activesync
Test Steps

Attempting each method of contacting the AutoDiscover Service
Failed to contact the AutoDiscover service successfully by any method
Test Steps

Attempting to test potential AutoDiscover URL
https://aspentechaz.com/AutoDiscover/AutoDiscover.xml
Failed testing this potential AutoDiscover URL
Test Steps

Attempting to Resolve the host name aspentechaz.com in DNS.
Host successfully Resolved
Additional Details
IP(s) returned: 216.119.81.119
Testing TCP Port 443 on host aspentechaz.com to ensure it is
listening/open.
The port was opened successfully.
Testing SSL Certificate for validity.
The SSL Certificate failed one or more certificate validation checks.

Tell me more about this issue and how to resolve it
Additional Details
A network error occurred while communicating with remote host:
Exception Details:
Message: Authentication failed because the remote party has closed the
transport stream.
Type: System.IO.IOException
Stack Trace:
at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32
readBytes, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer,
AsyncProtocolRequest asyncRequest)
at
System.Net.Security.SslState.CheckCompletionBefore NextReceive(ProtocolToken
message, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count,
AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ForceAuthentication(B oolean receiveFirst,
Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessAuthentication (LazyAsyncResult
lazyResult)
at System.Net.Security.SslStream.AuthenticateAsClient (String targetHost,
X509CertificateCollection clientCertificates, SslProtocols
enabledSslProtocols, Boolean checkCertificateRevocation)
at System.Net.Security.SslStream.AuthenticateAsClient (String targetHost)
at
Microsoft.Exchange.Tools.ExRca.Tests.SSLCertificat eTest.PerformTestReally()
Attempting to test potential AutoDiscover URL
https://autodiscover.aspentechaz.com...toDiscover.xml
Failed testing this potential AutoDiscover URL
Test Steps

Attempting to Resolve the host name autodiscover.aspentechaz.com in DNS.
Host successfully Resolved
Additional Details
IP(s) returned: 216.119.81.119
Testing TCP Port 443 on host autodiscover.aspentechaz.com to ensure it is
listening/open.
The port was opened successfully.
Testing SSL Certificate for validity.
The SSL Certificate failed one or more certificate validation checks.

Tell me more about this issue and how to resolve it
Additional Details
A network error occurred while communicating with remote host:
Exception Details:
Message: Authentication failed because the remote party has closed the
transport stream.
Type: System.IO.IOException
Stack Trace:
at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32
readBytes, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer,
AsyncProtocolRequest asyncRequest)
at
System.Net.Security.SslState.CheckCompletionBefore NextReceive(ProtocolToken
message, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count,
AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ForceAuthentication(B oolean receiveFirst,
Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessAuthentication (LazyAsyncResult
lazyResult)
at System.Net.Security.SslStream.AuthenticateAsClient (String targetHost,
X509CertificateCollection clientCertificates, SslProtocols
enabledSslProtocols, Boolean checkCertificateRevocation)
at System.Net.Security.SslStream.AuthenticateAsClient (String targetHost)
at
Microsoft.Exchange.Tools.ExRca.Tests.SSLCertificat eTest.PerformTestReally()
Attempting to contact the AutoDiscover service using the HTTP redirect
method.
Failed to contact AutoDiscover using the HTTP Redirect method
Test Steps

Attempting to Resolve the host name autodiscover.aspentechaz.com in DNS.
Host successfully Resolved
Additional Details
IP(s) returned: 216.119.81.119
Testing TCP Port 80 on host autodiscover.aspentechaz.com to ensure it is
listening/open.
The port was opened successfully.
Checking Host autodiscover.aspentechaz.com for an HTTP redirect to
AutoDiscover
Failed to get an HTTP redirect response for AutoDiscover
Additional Details
A Web Exception occured because an HTTP 404 - NotFound response was
received from IIS6
Attempting to contact the AutoDiscover service using the DNS SRV redirect
method.
Failed to contact AutoDiscover using the DNS SRV redirect method.
Test Steps

Attempting to locate SRV record _autodiscover._tcp.aspentechaz.com in DNS.
Failed to find AutoDiscover SRV record in DNS.





"Ace Fekay [MCT]" <> wrote in message
news:...
> "frbas" <> wrote in message
> news:...
>>
>> I am using a Windows Server 2003 with Exchange 2003 installed on it. We
>> recently had some problems with IIS and Exchange. For a while were we
>> unable to send and receive with Outlook and couldn't connect to OWA or
>> OMA. I was able to fix the issue with outlook, the SMTP server wasn't
>> properly associated with Exchange. We are still unable to access OWA or
>> OMA I have tried both of these solutions:
>>
>> http://www.msexchange.org/tutorials/...tallation.html
>>
>> http://www.msexchange.org/tutorials/...ange-2003.html
>>
>> Neither one of them worked. You can ping the server and it responds. I
>> seems like the servers is routing the requests for the OWA and OMA to
>> the proper places in the server. Can anyone please help me?
>>
>
> This is better posted in the Exchange newsgroups.
>
> However, have you tested your config at the Microsoft Exchange test site?
>
> Microsoft Exchange Server Remote Connectivity AnalyzerSelect the test you
> want to run: ... Exchange Remote Connectivity Analyzer has encountered an
> error. The entire error report is listed below: Show Report ...
> https://www.testexchangeconnectivity.com/
>
> I don't know what happened to cause all the problems. Let us know what
> caused the problems, or if you don;t know what caused them, post the
> symptons as well as any Event log errors, if Exchange is installed on a
> DC, if there is more than one NIC on the machine, (an unedited ipconfig
> /all would be extremely helpful), we can diagnose why it *possibly*
> occured and make suggestions and recommendations to fix it.
>
> Or maybe simply reinstalling Exchange with the /disasterrecovery switch
> may do the trick.
>
> For your covenience, I cross-posted to microsoft.public.exchange.admin -
> just check back in the general newsgroup for replies, but for the future,
> Exchange questions are better posted to the Exchange newsgroups. Since you
> are using Techarena, you will have to figure out where the Exchange
> section is.
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Please reply back to the newsgroup or forum for collaboration benefit
> among responding engineers, and to help others benefit from your
> resolution.
>
> Ace Fekay, MCT, MCTS Exchange, MCSE, MCSA 2003 & 2000, MCSA Messaging
> Microsoft Certified Trainer
>
> For urgent issues, please contact Microsoft PSS directly. Please check
> http://support.microsoft.com for regional support phone numbers.
>

"frbas" <> wrote in message
news:8E1BCF76-4578-418B-8DFC-...
> Thank, I didn't realize I was posting to a news group. I am now going
> directly to the news group.
>
> I don't know exactly what caused the issue, but I tried to install MS CRM
> on to the exchange server. That messed the IIS settings. I I tried
> reinstalling exchange and IIS but that didn't solve it. Honestly I tried
> so many things to fix the issues, I don't know which one actaully fixed
> it. The last thing I did, was revert to an older IIS web site, and renamed
> it Default Web Site and that then fixed the issue with outlook. Now the
> only issues it with OWA and OMA. Neither one of them will connect. I ran
> the tool you sent, below are the reports from it. We have two servers,
> Windows 2003 working as DC and a Windows 2003 running Exchange. I never
> changed any network settings directly, while trying to fix any of the
> issues.
>
> Thanks for the help.
>
> I ran three of them, here is the reports from them.
>
>
>
> Microsoft Exchange ActiveSync Connectivity Tests
> Exchange ActiveSync with AutoDiscover:
>
> Testing Exchange ActiveSync using the Autodiscover Service to obtain
> Settings
> Failed to test Exchange ActiveSync using the Autodiscover Service to
> obtain Settings
> Test Steps
>
> Attempting AutoDiscover and Exchange Activesync Test (if requested)
> Failed to test AutoDiscover for Exchange Activesync
> Test Steps
>
> Attempting each method of contacting the AutoDiscover Service
> Failed to contact the AutoDiscover service successfully by any method
> Test Steps
>
> Attempting to test potential AutoDiscover URL
> https://aspentechaz.com/AutoDiscover/AutoDiscover.xml
> Failed testing this potential AutoDiscover URL
> Test Steps
>
> Attempting to Resolve the host name aspentechaz.com in DNS.
> Host successfully Resolved
> Additional Details
> IP(s) returned: 216.119.81.119
> Testing TCP Port 443 on host aspentechaz.com to ensure it is
> listening/open.
> The port was opened successfully.
> Testing SSL Certificate for validity.
> The SSL Certificate failed one or more certificate validation checks.
>
> Tell me more about this issue and how to resolve it
> Additional Details
> A network error occurred while communicating with remote host:
> Exception Details:
> Message: Authentication failed because the remote party has closed the
> transport stream.
> Type: System.IO.IOException
> Stack Trace:
> at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32
> readBytes, AsyncProtocolRequest asyncRequest)
> at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer,
> AsyncProtocolRequest asyncRequest)
> at
> System.Net.Security.SslState.CheckCompletionBefore NextReceive(ProtocolToken
> message, AsyncProtocolRequest asyncRequest)
> at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32
> count, AsyncProtocolRequest asyncRequest)
> at System.Net.Security.SslState.ForceAuthentication(B oolean receiveFirst,
> Byte[] buffer, AsyncProtocolRequest asyncRequest)
> at System.Net.Security.SslState.ProcessAuthentication (LazyAsyncResult
> lazyResult)
> at System.Net.Security.SslStream.AuthenticateAsClient (String targetHost,
> X509CertificateCollection clientCertificates, SslProtocols
> enabledSslProtocols, Boolean checkCertificateRevocation)
> at System.Net.Security.SslStream.AuthenticateAsClient (String targetHost)
> at
> Microsoft.Exchange.Tools.ExRca.Tests.SSLCertificat eTest.PerformTestReally()
> Attempting to test potential AutoDiscover URL
> https://autodiscover.aspentechaz.com...toDiscover.xml
> Failed testing this potential AutoDiscover URL
> Test Steps
>
> Attempting to Resolve the host name autodiscover.aspentechaz.com in DNS.
> Host successfully Resolved
> Additional Details
> IP(s) returned: 216.119.81.119
> Testing TCP Port 443 on host autodiscover.aspentechaz.com to ensure it is
> listening/open.
> The port was opened successfully.
> Testing SSL Certificate for validity.
> The SSL Certificate failed one or more certificate validation checks.
>
> Tell me more about this issue and how to resolve it
> Additional Details
> A network error occurred while communicating with remote host:
> Exception Details:
> Message: Authentication failed because the remote party has closed the
> transport stream.
> Type: System.IO.IOException
> Stack Trace:
> at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32
> readBytes, AsyncProtocolRequest asyncRequest)
> at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer,
> AsyncProtocolRequest asyncRequest)
> at
> System.Net.Security.SslState.CheckCompletionBefore NextReceive(ProtocolToken
> message, AsyncProtocolRequest asyncRequest)
> at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32
> count, AsyncProtocolRequest asyncRequest)
> at System.Net.Security.SslState.ForceAuthentication(B oolean receiveFirst,
> Byte[] buffer, AsyncProtocolRequest asyncRequest)
> at System.Net.Security.SslState.ProcessAuthentication (LazyAsyncResult
> lazyResult)
> at System.Net.Security.SslStream.AuthenticateAsClient (String targetHost,
> X509CertificateCollection clientCertificates, SslProtocols
> enabledSslProtocols, Boolean checkCertificateRevocation)
> at System.Net.Security.SslStream.AuthenticateAsClient (String targetHost)
> at
> Microsoft.Exchange.Tools.ExRca.Tests.SSLCertificat eTest.PerformTestReally()
> Attempting to contact the AutoDiscover service using the HTTP redirect
> method.
> Failed to contact AutoDiscover using the HTTP Redirect method
> Test Steps
>
> Attempting to Resolve the host name autodiscover.aspentechaz.com in DNS.
> Host successfully Resolved
> Additional Details
> IP(s) returned: 216.119.81.119
> Testing TCP Port 80 on host autodiscover.aspentechaz.com to ensure it is
> listening/open.
> The port was opened successfully.
> Checking Host autodiscover.aspentechaz.com for an HTTP redirect to
> AutoDiscover
> Failed to get an HTTP redirect response for AutoDiscover
> Additional Details
> A Web Exception occured because an HTTP 404 - NotFound response was
> received from IIS6
> Attempting to contact the AutoDiscover service using the DNS SRV redirect
> method.
> Failed to contact AutoDiscover using the DNS SRV redirect method.
> Test Steps
>
> Attempting to locate SRV record _autodiscover._tcp.aspentechaz.com in DNS.
> Failed to find AutoDiscover SRV record in DNS.
>
>
>
>
>
>
> Microsoft Exchange ActiveSync Connectivity Tests
> Exchange ActiveSync
>
> Testing Exchange Activesync for host
> https://mail.aspentechaz.com/Microso...er-Activesync/
> Exchange Activesync test Failed
> Test Steps
>
> Attempting to Resolve the host name mail.aspentechaz.com in DNS.
> Host successfully Resolved
> Additional Details
> IP(s) returned: 207.155.232.100
> Testing TCP Port 443 on host mail.aspentechaz.com to ensure it is
> listening/open.
> The specified port is either blocked, not listening, or not producing the
> expected response.
>
> Tell me more about this issue and how to resolve it
> Additional Details
> A network error occurred while communicating with remote host:
> Exception Details:
> Message: No connection could be made because the target machine actively
> refused it 207.155.232.100:443
> Type: System.Net.Sockets.SocketException
> Stack Trace:
> at System.Net.Sockets.TcpClient.Connect(String hostname, Int32 port)
> at Microsoft.Exchange.Tools.ExRca.Tests.TcpPortTest.P erformTestReally()
>
>
>
>
>
>
>
> Microsoft Exchange Web Services Connectivity Tests
> ActiveSync Provider AutoDiscover
>
> Attempting AutoDiscover and Exchange Activesync Test (if requested)
> Failed to test AutoDiscover for Exchange Activesync
> Test Steps
>
> Attempting each method of contacting the AutoDiscover Service
> Failed to contact the AutoDiscover service successfully by any method
> Test Steps
>
> Attempting to test potential AutoDiscover URL
> https://aspentechaz.com/AutoDiscover/AutoDiscover.xml
> Failed testing this potential AutoDiscover URL
> Test Steps
>
> Attempting to Resolve the host name aspentechaz.com in DNS.
> Host successfully Resolved
> Additional Details
> IP(s) returned: 216.119.81.119
> Testing TCP Port 443 on host aspentechaz.com to ensure it is
> listening/open.
> The port was opened successfully.
> Testing SSL Certificate for validity.
> The SSL Certificate failed one or more certificate validation checks.
>
> Tell me more about this issue and how to resolve it
> Additional Details
> A network error occurred while communicating with remote host:
> Exception Details:
> Message: Authentication failed because the remote party has closed the
> transport stream.
> Type: System.IO.IOException
> Stack Trace:
> at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32
> readBytes, AsyncProtocolRequest asyncRequest)
> at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer,
> AsyncProtocolRequest asyncRequest)
> at
> System.Net.Security.SslState.CheckCompletionBefore NextReceive(ProtocolToken
> message, AsyncProtocolRequest asyncRequest)
> at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32
> count, AsyncProtocolRequest asyncRequest)
> at System.Net.Security.SslState.ForceAuthentication(B oolean receiveFirst,
> Byte[] buffer, AsyncProtocolRequest asyncRequest)
> at System.Net.Security.SslState.ProcessAuthentication (LazyAsyncResult
> lazyResult)
> at System.Net.Security.SslStream.AuthenticateAsClient (String targetHost,
> X509CertificateCollection clientCertificates, SslProtocols
> enabledSslProtocols, Boolean checkCertificateRevocation)
> at System.Net.Security.SslStream.AuthenticateAsClient (String targetHost)
> at
> Microsoft.Exchange.Tools.ExRca.Tests.SSLCertificat eTest.PerformTestReally()
> Attempting to test potential AutoDiscover URL
> https://autodiscover.aspentechaz.com...toDiscover.xml
> Failed testing this potential AutoDiscover URL
> Test Steps
>
> Attempting to Resolve the host name autodiscover.aspentechaz.com in DNS.
> Host successfully Resolved
> Additional Details
> IP(s) returned: 216.119.81.119
> Testing TCP Port 443 on host autodiscover.aspentechaz.com to ensure it is
> listening/open.
> The port was opened successfully.
> Testing SSL Certificate for validity.
> The SSL Certificate failed one or more certificate validation checks.
>
> Tell me more about this issue and how to resolve it
> Additional Details
> A network error occurred while communicating with remote host:
> Exception Details:
> Message: Authentication failed because the remote party has closed the
> transport stream.
> Type: System.IO.IOException
> Stack Trace:
> at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32
> readBytes, AsyncProtocolRequest asyncRequest)
> at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer,
> AsyncProtocolRequest asyncRequest)
> at
> System.Net.Security.SslState.CheckCompletionBefore NextReceive(ProtocolToken
> message, AsyncProtocolRequest asyncRequest)
> at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32
> count, AsyncProtocolRequest asyncRequest)
> at System.Net.Security.SslState.ForceAuthentication(B oolean receiveFirst,
> Byte[] buffer, AsyncProtocolRequest asyncRequest)
> at System.Net.Security.SslState.ProcessAuthentication (LazyAsyncResult
> lazyResult)
> at System.Net.Security.SslStream.AuthenticateAsClient (String targetHost,
> X509CertificateCollection clientCertificates, SslProtocols
> enabledSslProtocols, Boolean checkCertificateRevocation)
> at System.Net.Security.SslStream.AuthenticateAsClient (String targetHost)
> at
> Microsoft.Exchange.Tools.ExRca.Tests.SSLCertificat eTest.PerformTestReally()
> Attempting to contact the AutoDiscover service using the HTTP redirect
> method.
> Failed to contact AutoDiscover using the HTTP Redirect method
> Test Steps
>
> Attempting to Resolve the host name autodiscover.aspentechaz.com in DNS.
> Host successfully Resolved
> Additional Details
> IP(s) returned: 216.119.81.119
> Testing TCP Port 80 on host autodiscover.aspentechaz.com to ensure it is
> listening/open.
> The port was opened successfully.
> Checking Host autodiscover.aspentechaz.com for an HTTP redirect to
> AutoDiscover
> Failed to get an HTTP redirect response for AutoDiscover
> Additional Details
> A Web Exception occured because an HTTP 404 - NotFound response was
> received from IIS6
> Attempting to contact the AutoDiscover service using the DNS SRV redirect
> method.
> Failed to contact AutoDiscover using the DNS SRV redirect method.
> Test Steps
>
> Attempting to locate SRV record _autodiscover._tcp.aspentechaz.com in DNS.
> Failed to find AutoDiscover SRV record in DNS.
>
>
>


Your public mail record, mail.aspentechaz.com, does not respond when trying
to connect using https://mail.aspentechaz.com/exchange. That of course, I am
assuming is your Exchange OWA URL unless you had altered it. That definitely
indicates IIS is not listening, at least not externally. Can you connect to
that URL from the inside, or even using
https://exchangeServerInternalNetBIOSname/exchange?

Trying to install CRM on an Exchange server was not a good idea. Apparently
CRM altered the Default Website. Do you have a backup of the Inetpub folder,
as well as the system32\inetsrv folder prior to trying to install CRM? That
would be the easiest to fix it.

Have you tried using setup /disasterrecovery when reinstalling it?

Due to the fact that it's not responding, indicates the default website may
no longer be setup to listen to 80 or 443, which of course CRM probably did
that. You will need to check the default website properties, General tab,
next to the IP address there is an Advanced button. Is it set to listen to
80 and 443? If so, what is the hostheader set to?

Under Directory Sercurity tab, Authentication, is Anonymous, Basic and
Integrated Windows set?

When you go into the ESM, Server, protocols, HTTP, virtual server
properties, what do you see set as authentication? The way Exchange works,
you would set the authentication here, and the DS2MB function takes that
data and updates the Metabase from the Configuration Container in AD (where
Exchange configuration is stored).

Otherwise, you may need a consultant to come in that is familiar with
Exchange to reset IIS and Exchange, or another alternative, is to call
Microsoft PSS and have them reset it for you. The charge, last I checked was
USD $255.00, and they will do what they need to do and whatever time it
takes, to fix it.

Ace

On Sun, 30 Aug 2009 12:19:22 -0700, "frbas"
<> wrote:

>Thank, I didn't realize I was posting to a news group. I am now going
>directly to the news group.
>
>I don't know exactly what caused the issue, but I tried to install MS CRM on
>to the exchange server. That messed the IIS settings. I I tried reinstalling
>exchange and IIS but that didn't solve it. Honestly I tried so many things
>to fix the issues, I don't know which one actaully fixed it. The last thing
>I did, was revert to an older IIS web site, and renamed it Default Web Site
>and that then fixed the issue with outlook. Now the only issues it with OWA
>and OMA. Neither one of them will connect. I ran the tool you sent, below
>are the reports from it. We have two servers, Windows 2003 working as DC and
>a Windows 2003 running Exchange. I never changed any network settings
>directly, while trying to fix any of the issues.

Have you tried this KB?
http://support.microsoft.com/kb/320202
---
Rich Matheisen
MCSE+I, Exchange MVP

Perfect, that fixed OWA. IIS wasn't assigned to the internal IP address and
it wasn't listening on the ports. Still email on mobile phones are not
working at this point. Where would I go for that? Thanks for all the help.

"Ace Fekay [MCT]" <> wrote in message
news:...
> "frbas" <> wrote in message
> news:8E1BCF76-4578-418B-8DFC-...
>> Thank, I didn't realize I was posting to a news group. I am now going
>> directly to the news group.
>>
>> I don't know exactly what caused the issue, but I tried to install MS CRM
>> on to the exchange server. That messed the IIS settings. I I tried
>> reinstalling exchange and IIS but that didn't solve it. Honestly I tried
>> so many things to fix the issues, I don't know which one actaully fixed
>> it. The last thing I did, was revert to an older IIS web site, and
>> renamed it Default Web Site and that then fixed the issue with outlook.
>> Now the only issues it with OWA and OMA. Neither one of them will
>> connect. I ran the tool you sent, below are the reports from it. We have
>> two servers, Windows 2003 working as DC and a Windows 2003 running
>> Exchange. I never changed any network settings directly, while trying to
>> fix any of the issues.
>>
>> Thanks for the help.
>>
>> I ran three of them, here is the reports from them.
>>
>>
>>
>> Microsoft Exchange ActiveSync Connectivity Tests
>> Exchange ActiveSync with AutoDiscover:
>>
>> Testing Exchange ActiveSync using the Autodiscover Service to obtain
>> Settings
>> Failed to test Exchange ActiveSync using the Autodiscover Service to
>> obtain Settings
>> Test Steps
>>
>> Attempting AutoDiscover and Exchange Activesync Test (if requested)
>> Failed to test AutoDiscover for Exchange Activesync
>> Test Steps
>>
>> Attempting each method of contacting the AutoDiscover Service
>> Failed to contact the AutoDiscover service successfully by any method
>> Test Steps
>>
>> Attempting to test potential AutoDiscover URL
>> https://aspentechaz.com/AutoDiscover/AutoDiscover.xml
>> Failed testing this potential AutoDiscover URL
>> Test Steps
>>
>> Attempting to Resolve the host name aspentechaz.com in DNS.
>> Host successfully Resolved
>> Additional Details
>> IP(s) returned: 216.119.81.119
>> Testing TCP Port 443 on host aspentechaz.com to ensure it is
>> listening/open.
>> The port was opened successfully.
>> Testing SSL Certificate for validity.
>> The SSL Certificate failed one or more certificate validation checks.
>>
>> Tell me more about this issue and how to resolve it
>> Additional Details
>> A network error occurred while communicating with remote host:
>> Exception Details:
>> Message: Authentication failed because the remote party has closed the
>> transport stream.
>> Type: System.IO.IOException
>> Stack Trace:
>> at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32
>> readBytes, AsyncProtocolRequest asyncRequest)
>> at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer,
>> AsyncProtocolRequest asyncRequest)
>> at
>> System.Net.Security.SslState.CheckCompletionBefore NextReceive(ProtocolToken
>> message, AsyncProtocolRequest asyncRequest)
>> at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32
>> count, AsyncProtocolRequest asyncRequest)
>> at System.Net.Security.SslState.ForceAuthentication(B oolean receiveFirst,
>> Byte[] buffer, AsyncProtocolRequest asyncRequest)
>> at System.Net.Security.SslState.ProcessAuthentication (LazyAsyncResult
>> lazyResult)
>> at System.Net.Security.SslStream.AuthenticateAsClient (String targetHost,
>> X509CertificateCollection clientCertificates, SslProtocols
>> enabledSslProtocols, Boolean checkCertificateRevocation)
>> at System.Net.Security.SslStream.AuthenticateAsClient (String targetHost)
>> at
>> Microsoft.Exchange.Tools.ExRca.Tests.SSLCertificat eTest.PerformTestReally()
>> Attempting to test potential AutoDiscover URL
>> https://autodiscover.aspentechaz.com...toDiscover.xml
>> Failed testing this potential AutoDiscover URL
>> Test Steps
>>
>> Attempting to Resolve the host name autodiscover.aspentechaz.com in DNS.
>> Host successfully Resolved
>> Additional Details
>> IP(s) returned: 216.119.81.119
>> Testing TCP Port 443 on host autodiscover.aspentechaz.com to ensure it is
>> listening/open.
>> The port was opened successfully.
>> Testing SSL Certificate for validity.
>> The SSL Certificate failed one or more certificate validation checks.
>>
>> Tell me more about this issue and how to resolve it
>> Additional Details
>> A network error occurred while communicating with remote host:
>> Exception Details:
>> Message: Authentication failed because the remote party has closed the
>> transport stream.
>> Type: System.IO.IOException
>> Stack Trace:
>> at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32
>> readBytes, AsyncProtocolRequest asyncRequest)
>> at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer,
>> AsyncProtocolRequest asyncRequest)
>> at
>> System.Net.Security.SslState.CheckCompletionBefore NextReceive(ProtocolToken
>> message, AsyncProtocolRequest asyncRequest)
>> at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32
>> count, AsyncProtocolRequest asyncRequest)
>> at System.Net.Security.SslState.ForceAuthentication(B oolean receiveFirst,
>> Byte[] buffer, AsyncProtocolRequest asyncRequest)
>> at System.Net.Security.SslState.ProcessAuthentication (LazyAsyncResult
>> lazyResult)
>> at System.Net.Security.SslStream.AuthenticateAsClient (String targetHost,
>> X509CertificateCollection clientCertificates, SslProtocols
>> enabledSslProtocols, Boolean checkCertificateRevocation)
>> at System.Net.Security.SslStream.AuthenticateAsClient (String targetHost)
>> at
>> Microsoft.Exchange.Tools.ExRca.Tests.SSLCertificat eTest.PerformTestReally()
>> Attempting to contact the AutoDiscover service using the HTTP redirect
>> method.
>> Failed to contact AutoDiscover using the HTTP Redirect method
>> Test Steps
>>
>> Attempting to Resolve the host name autodiscover.aspentechaz.com in DNS.
>> Host successfully Resolved
>> Additional Details
>> IP(s) returned: 216.119.81.119
>> Testing TCP Port 80 on host autodiscover.aspentechaz.com to ensure it is
>> listening/open.
>> The port was opened successfully.
>> Checking Host autodiscover.aspentechaz.com for an HTTP redirect to
>> AutoDiscover
>> Failed to get an HTTP redirect response for AutoDiscover
>> Additional Details
>> A Web Exception occured because an HTTP 404 - NotFound response was
>> received from IIS6
>> Attempting to contact the AutoDiscover service using the DNS SRV redirect
>> method.
>> Failed to contact AutoDiscover using the DNS SRV redirect method.
>> Test Steps
>>
>> Attempting to locate SRV record _autodiscover._tcp.aspentechaz.com in
>> DNS.
>> Failed to find AutoDiscover SRV record in DNS.
>>
>>
>>
>>
>>
>>
>> Microsoft Exchange ActiveSync Connectivity Tests
>> Exchange ActiveSync
>>
>> Testing Exchange Activesync for host
>> https://mail.aspentechaz.com/Microso...er-Activesync/
>> Exchange Activesync test Failed
>> Test Steps
>>
>> Attempting to Resolve the host name mail.aspentechaz.com in DNS.
>> Host successfully Resolved
>> Additional Details
>> IP(s) returned: 207.155.232.100
>> Testing TCP Port 443 on host mail.aspentechaz.com to ensure it is
>> listening/open.
>> The specified port is either blocked, not listening, or not producing
>> the expected response.
>>
>> Tell me more about this issue and how to resolve it
>> Additional Details
>> A network error occurred while communicating with remote host:
>> Exception Details:
>> Message: No connection could be made because the target machine actively
>> refused it 207.155.232.100:443
>> Type: System.Net.Sockets.SocketException
>> Stack Trace:
>> at System.Net.Sockets.TcpClient.Connect(String hostname, Int32 port)
>> at Microsoft.Exchange.Tools.ExRca.Tests.TcpPortTest.P erformTestReally()
>>
>>
>>
>>
>>
>>
>>
>> Microsoft Exchange Web Services Connectivity Tests
>> ActiveSync Provider AutoDiscover
>>
>> Attempting AutoDiscover and Exchange Activesync Test (if requested)
>> Failed to test AutoDiscover for Exchange Activesync
>> Test Steps
>>
>> Attempting each method of contacting the AutoDiscover Service
>> Failed to contact the AutoDiscover service successfully by any method
>> Test Steps
>>
>> Attempting to test potential AutoDiscover URL
>> https://aspentechaz.com/AutoDiscover/AutoDiscover.xml
>> Failed testing this potential AutoDiscover URL
>> Test Steps
>>
>> Attempting to Resolve the host name aspentechaz.com in DNS.
>> Host successfully Resolved
>> Additional Details
>> IP(s) returned: 216.119.81.119
>> Testing TCP Port 443 on host aspentechaz.com to ensure it is
>> listening/open.
>> The port was opened successfully.
>> Testing SSL Certificate for validity.
>> The SSL Certificate failed one or more certificate validation checks.
>>
>> Tell me more about this issue and how to resolve it
>> Additional Details
>> A network error occurred while communicating with remote host:
>> Exception Details:
>> Message: Authentication failed because the remote party has closed the
>> transport stream.
>> Type: System.IO.IOException
>> Stack Trace:
>> at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32
>> readBytes, AsyncProtocolRequest asyncRequest)
>> at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer,
>> AsyncProtocolRequest asyncRequest)
>> at
>> System.Net.Security.SslState.CheckCompletionBefore NextReceive(ProtocolToken
>> message, AsyncProtocolRequest asyncRequest)
>> at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32
>> count, AsyncProtocolRequest asyncRequest)
>> at System.Net.Security.SslState.ForceAuthentication(B oolean receiveFirst,
>> Byte[] buffer, AsyncProtocolRequest asyncRequest)
>> at System.Net.Security.SslState.ProcessAuthentication (LazyAsyncResult
>> lazyResult)
>> at System.Net.Security.SslStream.AuthenticateAsClient (String targetHost,
>> X509CertificateCollection clientCertificates, SslProtocols
>> enabledSslProtocols, Boolean checkCertificateRevocation)
>> at System.Net.Security.SslStream.AuthenticateAsClient (String targetHost)
>> at
>> Microsoft.Exchange.Tools.ExRca.Tests.SSLCertificat eTest.PerformTestReally()
>> Attempting to test potential AutoDiscover URL
>> https://autodiscover.aspentechaz.com...toDiscover.xml
>> Failed testing this potential AutoDiscover URL
>> Test Steps
>>
>> Attempting to Resolve the host name autodiscover.aspentechaz.com in DNS.
>> Host successfully Resolved
>> Additional Details
>> IP(s) returned: 216.119.81.119
>> Testing TCP Port 443 on host autodiscover.aspentechaz.com to ensure it is
>> listening/open.
>> The port was opened successfully.
>> Testing SSL Certificate for validity.
>> The SSL Certificate failed one or more certificate validation checks.
>>
>> Tell me more about this issue and how to resolve it
>> Additional Details
>> A network error occurred while communicating with remote host:
>> Exception Details:
>> Message: Authentication failed because the remote party has closed the
>> transport stream.
>> Type: System.IO.IOException
>> Stack Trace:
>> at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32
>> readBytes, AsyncProtocolRequest asyncRequest)
>> at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer,
>> AsyncProtocolRequest asyncRequest)
>> at
>> System.Net.Security.SslState.CheckCompletionBefore NextReceive(ProtocolToken
>> message, AsyncProtocolRequest asyncRequest)
>> at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32
>> count, AsyncProtocolRequest asyncRequest)
>> at System.Net.Security.SslState.ForceAuthentication(B oolean receiveFirst,
>> Byte[] buffer, AsyncProtocolRequest asyncRequest)
>> at System.Net.Security.SslState.ProcessAuthentication (LazyAsyncResult
>> lazyResult)
>> at System.Net.Security.SslStream.AuthenticateAsClient (String targetHost,
>> X509CertificateCollection clientCertificates, SslProtocols
>> enabledSslProtocols, Boolean checkCertificateRevocation)
>> at System.Net.Security.SslStream.AuthenticateAsClient (String targetHost)
>> at
>> Microsoft.Exchange.Tools.ExRca.Tests.SSLCertificat eTest.PerformTestReally()
>> Attempting to contact the AutoDiscover service using the HTTP redirect
>> method.
>> Failed to contact AutoDiscover using the HTTP Redirect method
>> Test Steps
>>
>> Attempting to Resolve the host name autodiscover.aspentechaz.com in DNS.
>> Host successfully Resolved
>> Additional Details
>> IP(s) returned: 216.119.81.119
>> Testing TCP Port 80 on host autodiscover.aspentechaz.com to ensure it is
>> listening/open.
>> The port was opened successfully.
>> Checking Host autodiscover.aspentechaz.com for an HTTP redirect to
>> AutoDiscover
>> Failed to get an HTTP redirect response for AutoDiscover
>> Additional Details
>> A Web Exception occured because an HTTP 404 - NotFound response was
>> received from IIS6
>> Attempting to contact the AutoDiscover service using the DNS SRV redirect
>> method.
>> Failed to contact AutoDiscover using the DNS SRV redirect method.
>> Test Steps
>>
>> Attempting to locate SRV record _autodiscover._tcp.aspentechaz.com in
>> DNS.
>> Failed to find AutoDiscover SRV record in DNS.
>>
>>
>>
>
>
> Your public mail record, mail.aspentechaz.com, does not respond when
> trying to connect using https://mail.aspentechaz.com/exchange. That of
> course, I am assuming is your Exchange OWA URL unless you had altered it.
> That definitely indicates IIS is not listening, at least not externally.
> Can you connect to that URL from the inside, or even using
> https://exchangeServerInternalNetBIOSname/exchange?
>
> Trying to install CRM on an Exchange server was not a good idea.
> Apparently CRM altered the Default Website. Do you have a backup of the
> Inetpub folder, as well as the system32\inetsrv folder prior to trying to
> install CRM? That would be the easiest to fix it.
>
> Have you tried using setup /disasterrecovery when reinstalling it?
>
> Due to the fact that it's not responding, indicates the default website
> may no longer be setup to listen to 80 or 443, which of course CRM
> probably did that. You will need to check the default website properties,
> General tab, next to the IP address there is an Advanced button. Is it set
> to listen to 80 and 443? If so, what is the hostheader set to?
>
> Under Directory Sercurity tab, Authentication, is Anonymous, Basic and
> Integrated Windows set?
>
> When you go into the ESM, Server, protocols, HTTP, virtual server
> properties, what do you see set as authentication? The way Exchange works,
> you would set the authentication here, and the DS2MB function takes that
> data and updates the Metabase from the Configuration Container in AD
> (where Exchange configuration is stored).
>
> Otherwise, you may need a consultant to come in that is familiar with
> Exchange to reset IIS and Exchange, or another alternative, is to call
> Microsoft PSS and have them reset it for you. The charge, last I checked
> was USD $255.00, and they will do what they need to do and whatever time
> it takes, to fix it.
>
> Ace
>
>
>

"frbas" <> wrote in message
news:4AB70EF2-4C72-48F0-B4D3-...
> Perfect, that fixed OWA. IIS wasn't assigned to the internal IP address
> and it wasn't listening on the ports. Still email on mobile phones are not
> working at this point. Where would I go for that? Thanks for all the help.

What errors are you now getting with mobile connectivity?

Ace

I have a Palm Pre, so i wasn't getting any error messages. I was just
getting nothing. I check with a co-worker who has am HTC with Windows
Mobile. He was getting error 0x85010014, "ActiveSync encountered a problem
on the server." There was also some errors in the Event Viewer which pointed
me towartd KB 817379. So I am currently making a backup of the server and
then I will attempt it solution.


I will report back when it is done. Thanks for all your help so far.


"Ace Fekay [MCT]" <> wrote in message
news:...
> "frbas" <> wrote in message
> news:4AB70EF2-4C72-48F0-B4D3-...
>> Perfect, that fixed OWA. IIS wasn't assigned to the internal IP address
>> and it wasn't listening on the ports. Still email on mobile phones are
>> not working at this point. Where would I go for that? Thanks for all the
>> help.
>
> What errors are you now getting with mobile connectivity?
>
> Ace
>
>

Ok, so that KB fixed the issue. But devices configured to use SSL aren't
working. Do I just need to configure SSL on IIS or is there a specific SSL I
need to configure?


Thanks



"frbas" <> wrote in message
news:0065F089-8317-4E62-BF96-...
>I have a Palm Pre, so i wasn't getting any error messages. I was just
>getting nothing. I check with a co-worker who has am HTC with Windows
>Mobile. He was getting error 0x85010014, "ActiveSync encountered a problem
>on the server." There was also some errors in the Event Viewer which
>pointed me towartd KB 817379. So I am currently making a backup of the
>server and then I will attempt it solution.
>
>
> I will report back when it is done. Thanks for all your help so far.
>
>
> "Ace Fekay [MCT]" <> wrote in message
> news:...
>> "frbas" <> wrote in message
>> news:4AB70EF2-4C72-48F0-B4D3-...
>>> Perfect, that fixed OWA. IIS wasn't assigned to the internal IP address
>>> and it wasn't listening on the ports. Still email on mobile phones are
>>> not working at this point. Where would I go for that? Thanks for all the
>>> help.
>>
>> What errors are you now getting with mobile connectivity?
>>
>> Ace
>>
>>
>

Looks like the SSL is still partialy configured. When trying to access
https://domain.com/exchange I get this error from FireFox.

Secure Connection Failed

An error occurred during a connection to mail.aspentechaz.com.

SSL received a record that exceeded the maximum permissible length.

(Error code: ssl_error_rx_record_too_long)


How would I go about fixing this issue?

"frbas" <> wrote in message
news:0A8F1816-657F-4449-BE93-...
> Ok, so that KB fixed the issue. But devices configured to use SSL aren't
> working. Do I just need to configure SSL on IIS or is there a specific SSL
> I need to configure?
>
>
> Thanks
>
>
>
> "frbas" <> wrote in message
> news:0065F089-8317-4E62-BF96-...
>>I have a Palm Pre, so i wasn't getting any error messages. I was just
>>getting nothing. I check with a co-worker who has am HTC with Windows
>>Mobile. He was getting error 0x85010014, "ActiveSync encountered a problem
>>on the server." There was also some errors in the Event Viewer which
>>pointed me towartd KB 817379. So I am currently making a backup of the
>>server and then I will attempt it solution.
>>
>>
>> I will report back when it is done. Thanks for all your help so far.
>>
>>
>> "Ace Fekay [MCT]" <> wrote in message
>> news:...
>>> "frbas" <> wrote in message
>>> news:4AB70EF2-4C72-48F0-B4D3-...
>>>> Perfect, that fixed OWA. IIS wasn't assigned to the internal IP address
>>>> and it wasn't listening on the ports. Still email on mobile phones are
>>>> not working at this point. Where would I go for that? Thanks for all
>>>> the help.
>>>
>>> What errors are you now getting with mobile connectivity?
>>>
>>> Ace
>>>
>>>
>>
>

"frbas" <> wrote in message
news:4A7C912F-4FD5-4E6F-8507-...
> Looks like the SSL is still partialy configured. When trying to access
> https://domain.com/exchange I get this error from FireFox.
>
> Secure Connection Failed
>
> An error occurred during a connection to mail.aspentechaz.com.
>
> SSL received a record that exceeded the maximum permissible length.
>
> (Error code: ssl_error_rx_record_too_long)
>
>
> How would I go about fixing this issue?

Do you have a public or private certificate installed?

According to this, that error you're getting is based on a flawed
implementation of SSL.
https://support.comodo.com/index.php...articleid=1196

Or it's a firefox beta:
http://itknowledgeexchange.techtarge...h-firefox-3b5/

I imagine it works fine with IE. :-)

(Reminds me of one of the things as to why I don't use Firefox.)


Ace