Outlook RPC over HTTP

[Guido]

I am having trouble configuring Outlook 2007 to connect remotely to Exchange
Server 2003 (Windows SBS 2003).

I have done the connect to the Internet Wizard correctly. I can connect
using OWA by either typing the IP Address/Exchange or the Web Cerificate
generated, mail.domain_name.com.au/exchange.

When configuring Outlook 2007, it requires the name of the Exchange Server.
What is the exact syntax of the Exchange Server.

Your help is appreciated.

Regards,

Guido

 

[Milly Staples [MVP - Outlook]]

The exchange server is identified by its exact name such as exchange.yourdomain.com or ex1.yourdomain.com.

--
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact.
How to ask a question:
http://support.microsoft.com/KB/555375


After furious head scratching, Guido asked:

| I am having trouble configuring Outlook 2007 to connect remotely to
| Exchange Server 2003 (Windows SBS 2003).
|
| I have done the connect to the Internet Wizard correctly. I can
| connect using OWA by either typing the IP Address/Exchange or the Web
| Cerificate generated, mail.domain_name.com.au/exchange.
|
| When configuring Outlook 2007, it requires the name of the Exchange
| Server. What is the exact syntax of the Exchange Server.
|
| Your help is appreciated.
|
| Regards,
|
| Guido

 

[Guido]

Hi Milly,

I was just trying to give you some background.

In summary, Outlook cannor connect remotely to Exchange Server.

I have noticed that in Exchange Properties, RPC-HTTP Tab, the box that is
ticked is:

Not part of an Exchange managed RPC-HTTP topology.

Do I then select the other option:

RPC-HTTP back-end server.

Thanks,

Guido

 

[neo [mvp outlook]]

Lets backup a second...

When you type in https://IP_Address/exchange or
https://fqdn.exchange.servername/exchange, do you get any type of warning
about accepting the certificate? If yes, then the desktop cannot connect as
the certificate has to be verified back to the signing CA. (By this I mean
if the certificate is self issued, then the public 1/2 of the certificate
needs to be installed on any desktop/laptop that you expect to connect via
rpc/https)

Other than that, is it safe to assume that your SBS 2003 box has the latest
service packs and security fixes? Safe to assume that you are working with
a single server site or are you trying to establish a multi-exchange server
site?

 

[Guido]

Thanks Neo.

We do not get any warnings about the certificate. We did install the
certificate on the workstation.

The rest of your assumptions are all correct, single server, latest service
packs and updates.

At the SBS 2003 we run the Connect to internet wizard and generated a web
server cerificate: mail.domain_name.com.au.

Is there something else that we have not done or enabled at the Server.

Regards,

Guido

 

[neo [mvp outlook]]

Okay, so you are working with a self signed certificate. When you install
the certificate to the workstation, make sure it is to the computer's
trusted root certificate store?

The other thing that we need to make sure is that you identified the
exchange server as a back-end server. (Start Exchange System Manager, right
click on the server object, select properties, and go to the rpc-http tab.)

 

[Guido]

Hi Neo,

We have solved the problem.

At the login we type domain_name\user_name instead of user_name.

Thank you for your help.

Regards,

Guido