I guess my statement wasn't clear. I meant is it possible to disable
non-HTTP protocol support. If it can be enabled/disabled perhaps that is
what my issue is. I don't see anything obvious though.

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-14-10 12:46 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

"Outlook Anywhere" is the new name for "RPC over HTTP".

 

You asked: "Is it actually possible to disable that protocol on the
server end?"

 

I told you how.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Friday, May 14, 2010 11:43 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

I guess I don't understand why you suggest to disable Outlook Anywhere.
That is working as expected, but we need non-HTTP connections to work as
well.

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-14-10 12:39 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

Where did I say that? If I said that, I was wrong. :-P

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Friday, May 14, 2010 11:30 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

Are you saying that if Outlook Anywhere is enabled then regular non-HTTP
connections aren't going to work?

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-14-10 12:27 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

Oh. Duh. You can just "Disable-OutlookAnywhere".

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: Friday, May 14, 2010 11:24 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

I guess you could rename the RPC virtual directory on the server. I'm
not sure that's a supported thing to do though.

 

The supported way to do that would be "Set-CASMailbox
-MAPIBlockOutlookRpcHttp $true"

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Friday, May 14, 2010 10:44 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

Yikes. I see what you mean. It will take me a while to figure out the
proper command to use.

 

I've actually made some progress this morning. As it turns out, it
appears that RPC over HTTP does work properly. Authentication can
sometimes take a lot longer that I would expect, but otherwise it
functions as expected. Unfortunately I still can't get regular non-HTTP
connections to work. If I switch from a configuration using RPC over
HTTP and turn that setting off, loading Outlook immediately says it
can't connect to the server and gives you that standard Retry/work
offline/cancel error. Is it actually possible to disable that protocol
on the server end? The problem has to be a configuration mistake on the
Exchange server. 

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-13-10 7:53 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

If testexchangeconnectivity and test-outlookconnectivity  work then you
ARE making it all the way to the exchange server.

 

Then only other thing I can think of is using rpc-ping. That's not for
the weak.. :-P

 

Check out the articles about it on support.microsoft.com.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Thursday, May 13, 2010 4:49 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

That was a stupid mistake on my part. The POP3/IMAP errors were red
herrings and have nothing to do with the Outlook connectivity issues.
It's definitely baffling though. What event logging categories might be
helpful in determining what's going on? I took a look at them and
nothing really jumped out. I want to see if the attempt to connect is
actually making it all the way to the Exchange server.

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-13-10 11:43 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

Are you enabling ssl/tls on those connections? Or did you turn it off at
the server?

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Thursday, May 13, 2010 10:41 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

I tried the management tools from a notebook and the
test-exchangeconnectivity checks are successful. The
Get-ExchangeCertificate on the server shows IP.WS on the SAN Cert, so I
guess that's correct as well. 

 

When I try setting up Windows Mail in POP3 mode, I get the error:

 

Account: 'exchange2.acadiau.ca', Server: 'exchange2.acadiau.ca',
Protocol: POP3, Server Response: '-ERR Command is not valid in this
state.', Port: 110, Secure(SSL): No, Server Error: 0x800CCC90, Error
Number: 0x800CCC91

 

With an IMAP connection, I get the error "The server has rejected your
login. Please verify that the username and password are correct."

 

I tried setting the event logging for POP3 and IMAP to highest, but I'm
not getting any authentication errors listed. What event service
controls logging for authentication requests? I didn't see anything
obvious in the list of possible event categories. Maybe it will have a
better explanation of why the server is rejecting the logins.

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-13-10 10:34 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

Doesn't matter whether you delete it or not. "Most" people run with the
default cert for SMTP and a SAN cert for everything else. If you run a
Get-ExchangeCertificate, you need a "W", and a "S" on valid
certificates. The others ("I", "P") are secondary to the first two.

 

I'm kinda at a loss. You might try those same tests from a workstation
that has the management tools installed, instead of from the Exchange
Server itself.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Thursday, May 13, 2010 9:29 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

When installing the UC cert, should the original Microsoft cert be
deleted? I still think this issue is somehow related to a certificate
problem...

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: May-12-10 2:52 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

I also tried 

 

Test-OutlookConnectivity -Protocol:TCP
-GetDefaultsFromAutoDiscover:$true

 

and it worked as well...

 

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: May-12-10 2:14 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

I tried these two commands, to verify RPC and HTTP connectivity:

 

Test-OutlookConnectivity -RpcProxyTestType:Internal -RpcTestType:Server

Test-OutlookConnectivity -Protocol:Http
-GetDefaultsFromAutoDiscover:$true

 

Both completed without errors. I tried an Outlook session configured
using Outlook Anywhere and Outlook just keeps prompting for username and
password. For some reason Outlook doesn't like the credentials even
though they are valid. I'm very puzzled...

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-12-10 12:47 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

In Exchange Management Shell, on the Exchange Server, run the
Test-OutlookConnectivity cmdlet. Read the help first, so you know what
to expect.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Wednesday, May 12, 2010 11:01 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

I ran the tests at textexchangeconnectivity.com and they all pass except
for the first one, Exchange ActiveSync. If I tell it to ignore the
certificate validity check, then it also work. The detailed error is:

 

"Host name acadiau.ca does not match any name found on the server
certificate e=r...@acadiau.ca, CN=www.acadiau.ca, OU=Technology
Services, O=Acadia University, L=Wolfville, S=Nova Scotia, C=CA"

 

It would imply that it expected to find acadiau.ca or www.acadiau.ca in
the cert, but I'm not sure why it's using those entries. My UC cert has
three entries and they appear to work properly for the other tests, and
in OWA. We never had a cert on Exchange 2003, but the UC cert I got from
Digicert seem to install properly. I don't reference www.acadiau.ca
anywhere as far as I know.

 

The problem I'm encountering is that Outlook (any version) won't connect
to the server. As I started troubleshooting, I've also discovered that
POP3 and MAPI connections fail as well. The only way I can connect to
the server is using OWA or through my iPod Touch. I'm pretty sure this
whole problem occurred when I installed the UC cert, although I'm not
100% sure. I had been using OWA for my testing so I didn't notice when
Outlook broke. I suspect it's going to be another one of those
situations where I need to check some box some place. It's just not
obvious what needs to be done.

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-12-10 9:24 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

Are you attempting to connect directly (i.e., MAPI) or while using
AutoDiscover/OutlookAnywhere?

 

What does testexchangeconnectivity.com say?

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Tuesday, May 11, 2010 8:20 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

I've tried Outlook 2007 and 2010 under XP, Vista, and Windows 7....

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-11-10 8:31 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

What version of Outlook?

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Tuesday, May 11, 2010 7:21 PM
To: MS-Exchange Admin Issues
Subject: Outlook won't connect to Exch2010

 

We've encountered yet one more problem on our new Exchange 2010 server.
When the server install was first completed, one of the first things I
did was create a test account and connected to it using Outlook. It
worked as expected. OWA also worked fine, as did access to the account
from an iPod Touch. When Outlook tries to verify the user account, it
says it can't connect to the Exchange server. One thing I've done since
the install was completed was install a UC certificate and it works as
expected with OWA. Being paranoid I removed the UC cert and assigned
services back to the default Exchange cert, but that didn't help. At
this point I'm not even sure if it's a certificate problem. 

 

I tried setting up Windows Mail using both POP3 and IMAP protocols, and
both of those protocols failed as well. The error message indicates that
the server is rejecting the username/password but since I know I'm using
the right credentials there's obviously something else happening. What
would allow OWA to work but break everything else?

 

Reply via email to