Re: Outlook over Internet Issues

Hello John,

Thank you for your update.

Robbin is out of office today. I would like backup this post and reply to
you.

To configure the RPC over HTTP for remote Outlook users to connect to your
Exchange server 2003 on SBS, we need to the following steps:

I. Run CECIW on SBS to configure the Exchange server for RPC over HTTP:

a. On the SBS 2003 Server open the Server Management console. Go to
Standard Management\To Do List.

b. Click the "Connect to the Internet" link.

c. When navigating to the Firewall page, select "Enable firewall" and click
Next.

d. On the "Services Configuration" page, select all the items and then
click Next.

e. On the "Web Services Configuration" page, make sure "Allow access to the
entire Web site from the Internet" is selected. If you select "Allow access
to only the following Web site services from the Internet", make sure all
items in the list are selected. Click Next.

Note: This step will publish the RPC over HTTP to external.

f. On the "Web Server Certificate" page, choose to create a new Web server
certificate and then type the public domain name (your public DNS name)
that you will use to access OWA and RWW (for example, if your public domain
name that you use to access the sites is www.xyz.com, you should type
www.xyz.com as the new certificate name).

g. Go through the remaining steps.

II. You need to install the certificate which you create when run CECIW on
the remote Outlook client. The RPC over HTTP need the certificate.

Please access the RWW web site from the remote client via
https://www.xyz.com/remote. If the certificate is trusted, a certificate
warning does not appear. If the certificate is not trusted, a warning
appears. Click View Certificate, click Install Certificate, and then follow
the instructions.

III. Configure the RPC over HTTP on the Outlook client:

1. Click Start, and then click Control Panel.

a. If you are viewing Control Panel in the default Category view, switch to
Classic view, and then double-click Mail.
b. If you are viewing Control Panel in Classic view, double-click Mail.

2. In the Mail Setup dialog box, click E-mail accounts, click View or
change existing e-mail accounts, and then click Next.
3. In the E-mail accounts dialog box, click Microsoft Exchange Server, and
then click Change.
4. In the Microsoft Exchange Server box, type the local name of the
Exchange server:

SBSname.domain.local

5. In the User Name box, type the user name that you use to log on to the
Remote Web Workplace. Do not click Check Name.
6. In the Exchange Server settings page, click More Settings.
7. On the Connection tab, under Exchange over the Internet, select Connect
to my Exchange mailbox using HTTP, and then click Exchange Proxy Settings.
The Exchange Proxy Settings dialog box appears.
8. Under Use this URL to connect to my proxy server for Exchange, type the
following URL:

www.xyz.com

9. Select Connect using SSL only, and then select Mutually authenticate the
session when connecting with SSL.
10. In the Principal name for proxy server box, type the following text:

msstd: www.xyz.com

11. Select On slow networks, connect using HTTP first, then connect using
TCP/IP.
12. Under Proxy authentication settings, select Basic Authentication.
13. Click OK, and then click OK again. Click Next, and then click Finish.
Click Close.
14. In the Mail dialog box, if Always use this profile is selected, choose
the newly configured profile.
15. Open Outlook and type your Windows Small Business Server user name (in
the format SBS2003\user name) and password. You can now work with your
Outlook mailbox.

IV. Ensure that the following requirements have been met on the client
computer.

1. Verify that the computer is running Microsoft Windows XP Service Pack 1
or later
2. Verify that Windows update KB331320 is installed on the computer (not
required if you are running Windows XP Service Pack 2 or later)
Outlook 2003 Performs Slowly or Stops Responding When Connected to Exchange
Server 2003 Through HTTP
http://support.microsoft.com/kb/331320

If we cannot resolve the issue after we perform the steps above, please
help me collect some information for further investigation:

1. Do you get any error when you try to establish RPC over HTTP connection?
If yes, please send the screenshot to Robbin.

2. Please let us know your public FQDN (www.xyz.com) and SBS internal FQDN
(SBSname.domain.local), and create a test account for us to do the test.
Please send the information to Robbin's mailbox.

I hope these steps will give you some help.

Thanks and have a nice day!

Best regards,

Terence Liu (MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
X-Tomcat-ID: 96115328
References: <80o4MOc3IHA.4056@xxxxxxxxxxxxxxxxxxxxxx>
<f4dd4ef2-5f31-4278-b528-e5f1d674e6cf@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
<eQp1d8X4IHA.2336@xxxxxxxxxxxxxxxxxxxx>
<b4a288e1-2e5d-4b21-93c3-9458ea271189@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
<d2d871c5-9ef3-42ea-986f-2e39cf1438c0@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
<#TTfr0g4IHA.4448@xxxxxxxxxxxxxxxxxxxx>
<150849aa-32de-4d52-9127-271388dadaa9@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
<#tBt9Lk4IHA.4916@xxxxxxxxxxxxxxxxxxxx>
<63tb7451hlr7doi070k1476td725ha9rvc@xxxxxxx>
<713A9A16-F588-48E8-A6E3-4275B379AA8D@xxxxxxxxxxxxx>
<VPVGEkn5IHA.3320@xxxxxxxxxxxxxxxxxxxxxx>
<FPy1$Q85IHA.3324@xxxxxxxxxxxxxxxxxxxxxx>
<n4mds1M6IHA.3320@xxxxxxxxxxxxxxxxxxxxxx>
<C7T2zl56IHA.5352@xxxxxxxxxxxxxxxxxxxxxx>
<Y67EbN$6IHA.3588@xxxxxxxxxxxxxxxxxxxxxx>
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
From: v-robmen@xxxxxxxxxxxxxxxxxxxx ("Robbin Meng [MSFT]")
Organization: Microsoft
Date: Tue, 29 Jul 2008 11:16:03 GMT
Subject: Re: Outlook over Internet Issues
X-Tomcat-NG: microsoft.public.windows.server.sbs
Message-ID: <#o7L9xW8IHA.1624@xxxxxxxxxxxxxxxxxxxxxx>
Newsgroups: microsoft.public.windows.server.sbs
Lines: 11
Path: TK2MSFTNGHUB02.phx.gbl
Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:117159
NNTP-Posting-Host: tk5tomimport2.phx.gbl 10.201.218.20

From: John
Sent: 2008Äê7ÔÂ29ÈÕ 10:59
To: Robbin Meng
Subject: RE: Follow Up For Microsoft SBS Public Newsgroup Post [Outlook
over Internet Issues] with Robbin Meng (42236155)

Robbin,

I still can't seem to get my local clients to communicate over HTTPS. I
have followed the procedures several times, from both Outlook 2003 and
2007. Any ideas on why my clients would not try to communicate over HTTP
vs
TCP?



.

Relevant Pages

  • RE: DST update for Exchange 2003 and Outlook 2003
    ... subfolder named for your Exchange Server, and in that subfolder it will ... Server Settings = Server Name and Log File ... Time Zone Extraction Settings = Outlook Profile Name and Output File ... "If you want to try it out on only a few mailboxes at first, ...
    (microsoft.public.exchange.admin)
  • Re: RPC over HTTP
    ... We have already set up Outlook Web Access and purchase a SSL Certificate ... I have used the "outlook.exe /rpcdiag" to see if it uses the HTTP ... firewall through to the exchange server. ...
    (microsoft.public.windows.server.sbs)
  • Re: RPC over HTTP
    ... On how to configure RPC over Http for Outlook, ... To use Outlook via the Internet ... Verify that the computer trusts the certificate used by the server ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange, Outlook and DNS problem
    ... > Company deceided to switch from ISP POP3 to local Exchange server. ... > Cisco routes to local ISA IP address.ISA is configured to do RPC over ... > HTTP routing for Exchange which is also located in internal network. ... > Outlook while connected internal network. ...
    (microsoft.public.win2000.dns)
  • Re: 2 locations sharing email domain through external hosting serv
    ... Using Outlook via the Internet ... server e-mail account from the Internet when you are working outside your ... Comparing RPC over HTTP and Outlook Web Access ... If Microsoft Exchange Server does not appear in the list, ...
    (microsoft.public.windows.server.sbs)