Outlook 2007 RPC over HTTPS issue

[jachin84]

Hi all,
Our organisation uses Outlook 2007 with RPC over HTTPS (Outlook Anywhere) and it doesn't seem to work with Windows 7.

I have Windows 7 Beta 1 (Build 7000) and Outlook 2007 sp1 with all hotfixes. I've read in several places to use NTLM however this is not an options for us.

Has anyone identified the issue or know of a workaround??

 

[daemian]

this seems to be a pretty popular solution. I am having the same problem, but it works when I am onsite. I will try this solution when i get home

Several of us at the office have been trying out the new Windows 7 - It’s been a positive experience so far and quite a bit faster than Vista. One problem popped up on all the machines - When we tried to configure Outlook 2007 to connect to our hosted exchange server (using the prf file so we knew it was configured right) it would continuously prompt for the password.
This appears to be the result of the way hosted exchange systems require the use of a full email as the username to differentiate between client domains. Windows 7 doesn’t care for this and the connection fails. It may take a bit of doing but if you find your domain name and username from your provider and enter it as follows:
Domain\Username
You’ll find it functions perfectly. The domain is not the domain name from your email it is something else - In our case I had to hit our server configuration and used the settings for configuring mobile activesync on my windows mobile device. Our provider happens to use a special username to differentiate it’s users. Once we found that we were happily reading emails again.

Outlook RPC over HTTPS doesn’t work in Windows 7 | JEREMYROE.NET

 

[daemian]

fyi - worked great for me

 

[jachin84]

None of these options appear to work for me. I've noticed that the issue seems limited to Windows 7 x64. I have two machines running 32bit and they can connect perfectly to exchange. Strange....

 

[SnapCount]

I had the same problem, all the fixes that are suppose to work didnt

Finally got it to work by getting the server to create a ssl certificate and manually putting it into the Trusted root certificate section in the certificate manager

 

[jachin84]

Ok ignore my previous comment about x64. I've narrowed my problem to Vodafone Mobile Connect. It is used for wireless 3g and installing it seems to break certain rpc traffic. Grr!!!

 

[ChrisDTC]

I had the same problem, all the fixes that are suppose to work didnt

Finally got it to work by getting the server to create a ssl certificate and manually putting it into the Trusted root certificate section in the certificate manager

Could you please provide steps on how you did this. I am having the same Outlook 07 problem on 64 bit 7 beta and none of the other fixes have worked for me.

 

[treyr]

Folks, I have the same issue, tried all the workarounds and still cannot connect use outlook rpc over https.
Tried Domain login
Tried loading ssl certificate
Tried Basic Authentication
Nothing seems to work, unless I am VPN'd in...
I am running Build 7100 32 bit...
Anymore suggestions are very much appreciated...

 

[neop26]

What certs are u guys using? The work around this what I had to do was get a XP box. Log onto your OWA access get the certificate (most cases self signed ones) Copy it into a USB bring it over to 7 install the certificate under root and then try to connect to ur exchange... let me know how it goes..hope it helps.

 

[treyr]

It is a geotrust cert...works fine with my Vista clients... I installed it under root and it did not improve my situation... I am fairly certain it is not the cert...when I change the msstd: definition to something other than the site name, it complains...but when I change it back, it does not...something else, more sinister, is going on here...It is odd to me that there are so many other folks that have gotten this to work...

 

[neop26]

ok did u try set it up for the first time inside the domain itself or is the system outside the domain/network all the time. If so then there could be issues with it getting authenticated with the DC for some reason.

go to Control Panel
Click Mail
Delete all existing profiles(from previous testing)
Setup new profile and click properties.
Enter Username email address and everything else and let Outlook configure the whole thing? Does it get completed.

If not go to Manual setup and go and setup the server name and stuff. Go to the exchange over http setup and keep both the proxy and url as the server name itself..

for eg: exchsrv01.domainname.com then on ur DNS(External / ISP) setup exchsrv01.domainname.com to your external IP address.

 

[treyr]

neop26...
Interesting that you brought that up... I joined the domain over a VPN, while setting up Windows 7 from home. You think if I create a new profile at work and then try outlook anywhere from outside the network, it may work?

 

[neop26]

Ah I like the style u joined the system over VPN WAN. nice work.

Hmmm usually
1. When inside the domain and logged in as a domain user the first time you start up outlook 07 the autodiscover feature kicks in and sorts out all the configration and stuff. This also includes all the setting for Outlookanywhere as well. So all the setting that the exchange puts onto the outlook account settings should in theory work from WAN as well.

2. But I am on holiday for a week and away from home where my exchange server is sitting and last week got the rc. Installed it and wanted my mails coming in there as well. So started the setup in outlook but was failing because of the cert(no sense in 400$ cert for 1 user hehehe) so I use self signed luckily though got my other xp lap with outlook all ready and working..got the cert outa there installed it onto root. Then did control panel mail new outlook profile started confiuring it just like how it is on my xp....and wola it started working....

standard configration of exchange actually nothing complicated.

 

[ppp]

I guarantee this is an ISP or Cert problem. It has nothing to do with Windows 7. Nothing at all.

 

[treyr]

I guess that is possible, however, it works fine for all of our Vista and XP clients...is 7 more particular about certs?

 

[ppp]

I guess that is possible, however, it works fine for all of our Vista and XP clients...is 7 more particular about certs?

Maybe. I've seen weird things happen with Win7 + Outlook 2010 + certs that does NOT happen with Vista/XP+ 2010, and doesn't happen with Win7+Outlook2007. Essentially if the certs aren't JUST RIGHT, the more "new" stuff you have the more convoluted things get. XP + Outlook 2003 is pretty darn tolerant.

 

[Aheaton]

I have solved this

Please see my post @:

http://www.sevenforums.com/software/3790-outlook-07-exchange-server-not-working.html

 

[bibiodo]

Are there any more updates about this subject....

I came across the same issue last week.

Any help is appreciated.

Tsjompie

 

[RonEnzo]

Is there any news about this issue? We got the same problems with a windows 7 enterprise versions... On our exchange is no payed cetrificate, but installed the certificate om the laptop..

Starting outlook /rpcdiag we see no connection. Sometime he try to make a connections but not working.

 

[bibiodo]

this is what i did

It's quite a time ago I dealt with this, but I think this is what I did:

Export the web certificate from the server (this is the iis environment!)
Remove all certs from the client
Import the cert from the server, but do place that manually as trusted root.
So that is the root CA the client needs to allow the neccesary cert to connect to the exchange webserver.

I was sure the https configuration was working (with as self created cert) because my former laptop OS installation was functional. I’ve been messing around with other settings too, but the change there is a cert issue is huge.

Good luck getting it working