• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 885
  • Last Modified:

Outlook 2007 to use Exchange using HTTP

I just completed a SWING migration and I have successfully moved everything to the new box. (w a new machine name and new ip address.)  I've already configured everything firewall (ports 80, 443, 993, 25) to point to the new server.  

Everybody can connect locally from their Outlook 2007 and can access OWA as well when their outside.

However I also have users who use Exchange using HTTP on their computers at home cause they hate OWA.  Who doesn't?  lol

Anyway, I have read so many articles here and microsoft tech websites on how to configure this.  Do I really have to make registry changes? on both the Server and the client side???  

On a newly installed Exchange server2003 SP2 on a new Server 2003 Standard SP2 Machine, I guess RPC over HTTP is not enabled by default?  I installed the RPC over HTTP sindows component and now I see RPC and RpcCert on the virtual directories on IIS.  Not sure what to do next.

Please help.  The OUTLOOK clients used to work using Exchange using HTTP but now, they hate me :(

Please help.
0
chudkllr
Asked:
chudkllr
  • 9
  • 6
4 Solutions
 
MesthaCommented:
There are no registry changes required on the clients. It only requires changes on the Exchange server and the domain controller. If you already had the feature enabled before then the only place to make the change is on the Exchange server itself.

http://www.amset.info/exchange/rpc-http.asp

Simon.
0
 
chudkllrAuthor Commented:
After I edit the sample under "Separate Exchange and Domain Controller Configuration", and replaced the appropriate information, saving it as a reg file (all files)  and then I double click on it, rpc-http-server.reg has been successfully entered into the registry.  However, when I check the key under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\RpcProxy, it didnt change anything.  Even after a reboot.

even if I manually paste the information on "valid Ports"  still no RPC over HTTP love.

Any thoughts?


_________


Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\RpcProxy]
"ValidPorts"="
exchange-server:100-5000;
exchange-server:6001-6002;
exchange-server.domain.local:6001-6002;
dc:6001-6002;
dc.domain.local:6001-6002;
exchange-server:6004;
exchange-server.domain.local:6004;
dc:6004;
dc.domain.local:6004;
mail.external.com:6001-6002;
mail.external.com:6004;
dc:593;
dc.domain.local:593;
exchange-server:593;
exchange-server.domain.local:593;
mail.external.com:593;"

0
 
chudkllrAuthor Commented:
On the client side

these are my settings:

Microsoft Exchange Server: exchangeserver.mydomain.local  

and then I click more settings, on the Connection Tab, Outlook Anywhere

Connect to MS Exchange using HTTP is checked and on the Exchange Proxy Settings,

https://mail.mydomain.com

Connect Using SSL unchecked

On Fast... unchecked
On Slow...Checked

Proxy Authentication

Basic Authen.

***This was how it was configured before.  The difference the one stated on AMSET is I have to check everything and use NTLM authentication.  I tried that too. and still no Coneection :(

0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
MesthaCommented:
Test your configuration using the Microsoft test site:

https://testexchangeconnectivity.com/

Simon.
0
 
chudkllrAuthor Commented:
This is the only error I get when i do the Microsoft Office Outlook 2003 RPC/HTTP Connectivity Test

      Testing Http Authentication Methods for URL https:/mail.mydomain.com/rpc/rpcproxy.dll
       Http Authentication Test failed

Exception Details: Message: The underlying connection was closed: The connection was closed unexpectedly. Type: System.Net.WebException Stack Trace: at System.Net.HttpWebRequest.GetResponse() at Microsoft.Exchange.Tools.ExRca.Tests.HttpAuthMethodsTest.PerformTestReally()
      

Thanks Simon
0
 
MesthaCommented:
Is the port open on the firewall and is pointing to the correct server?
Is Outlook Anywhere enabled on the server?

The error tends to point to the problem being outside of Exchange.

Simon.
0
 
chudkllrAuthor Commented:
ports 80, 443, 993, 25 are all pointing to the new server.  OWA works (which btw works in Firefox but not in IE) so Outlook Anywhere should be enabled already right?
0
 
MesthaCommented:
No - RPC Over HTTPS (Outlook Anywhere is its name on Exchange 2007, you would be well advised not to use that name in reference to Exchange 2003 because it will confuse people) is not enabled by default.

You have to install the RPC Proxy component in Windows Components then enable the feature in Exchange. You have installed the component?

Simon.
0
 
chudkllrAuthor Commented:
Yes the component is istalled and Rpc and RpcCert is on IIS

RPC is set to Enable anonymous, Integrated Windows authen and Baisc Authen are all checked
0
 
MesthaCommented:
Anonymous should NOT be enabled on the RPC virtual directory. That will cause problems. Only Basic and Integrated. After changing it run iisreset in a command prompt to write the change to the IIS metabase.

Simon.
0
 
chudkllrAuthor Commented:
OK.  I think we're getting there.  When I do a test on testexchangeconnectivity.com and go through the Microsoft Office Outlook 2003 RPC/HTTP Connectivity Test,  everything is tests successfully.  It passes w no errors whether RPC Proxy Auth Method is Basic or NTLM.  So maybe its there's a setting Im missing on my client machine  which I've tried everthing already.
0
 
MesthaCommented:
If the test is working correctly, then the feature is probably configured correctly. You just need to look at the client configuration to ensure that is correct.

I have client configuration instructions on my web site here:
http://www.amset.info/exchange/rpc-http.asp

Simon.
0
 
chudkllrAuthor Commented:
I follow the exact directions on amset however, Im still not connecting. i tired both Basic and NTLM.

i even run the client test cmd, outlook /rpcdiag and nothing shows up on the Exchange connection status.

:(
0
 
chudkllrAuthor Commented:
Thanks Simon.  The links you provided were very detailed and clear.   The machine I was testing it on (my XP machine at home) had SP1.  I updated to SP3 and Im not sure if that fixed the problem.  Everyone can connect now using NTLM Authentication on the client side
0
 
chudkllrAuthor Commented:
Thanks Simon for your help
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 9
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now