Re: Outlook 2003 client

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hi Nathan,
Thank you for the reply.

Your latest assumption of the network topology is correct.

When I initially ran CEICW, I created my own web server certificate:
remote.domain.local.

While following the steps to configure Outlook for RPC/HTTP, the install
notes tells me to enter https://remote.domain.local/remote in my Internet
Explorer address bar. After doing that it returns the following error:

Network Access Message: The page cannot be displayed
Technical Information (for Support personnel)
• Error Code: 502 Proxy Error. The host was not found.(11001)
• IP Address: 192.168.1.13
• Date: 18/08/2005 15:52:52
• Server: servername.company.local
Source: proxy

However, when I type https://domain.local/remote, I get the ‘Security Alert‘
window to view the certificate. The warning is ‘The name on the security
certificate is invalid or does not match the name of the site’. When I click
to view the certificate, it is one named ‘publishing.domain.local’ and not
‘remote.domain.local’.

Even after installing ‘publishing.domain.local’ certificate, it still
prompts me the same ‘Security Alert’ window the next time I log on.

On the SBS server I have both ‘remote.domain.local’ and
‘publishing.domain.local’ certificates installed in the ‘Personal’ and
‘Trusted Root Certification Authorities’ folders of Certificates snap-in
(MMC).

1) How do I get https://remote.domain.local/remote to work?
2) Was I right in creating the certificate to be ‘remote.domain.local’, or
should it rather be ‘remote.domain.com’? I ask this as some users would like
to use RPC/HTTP from the Internet in the near future.
3) Where does this ‘publishing.domain.local’ fit into the picture?
4) I am also quite curious to know how RPC/HTTP will improve
performance…does it synchronize less or simply communicate thinner to the
server?
5) Do I have to get my ISP to create an A-record for ‘remote.domain.com’?

I am quite confused now, please advise.
Many thanks.


""Nathan Liu [MSFT]"" wrote:

> Hi TonyV,
>
> Thank you for your kind reply.
>
> As you mentioned, can I assume your network topology like the below
> description:
> (Branch office) problematic user <-> Router <-> 64K link <-> Router <-> SBS
> 2003 / ISA Server <-> Switch <-> LAN users (main office)
>
> For your question: I had a look at the certificate status on the SBS Server
> and it shows 'The CA root certificate is not trusted because it is not in
> the trusted root certification authorities store'. How do I fix this?
>
> Answer: Please understand this message is anticipation, since we need to
> access the RWW with SSL, so we need the certificate. If we don't have
> install the certificate in the Trusted Root Certification Authorities
> store, the message will display. Please click 'Install Certificate' button,
> in the next page, click Next, then choose the default "Automatically select
> the certificate store based on the type of certificate" option, click Next,
> then click Finish. In the Security Warning dialog box, click Yes. You
> should then be able to see the RWW logon page.
>
> Question 2: Does the user have to be a member of the RWW security group to
> run Outlook in RPC/HTTP mode?
>
> Answer: It is not necessary for the user must be a member of the RWW
> security group to run Outlook in RPC/HTTP mode, but for SBS 2003 Server, if
> we use the four default User template to create new user, and the new user
> account is a member of the Remote Web Workplace Users security group by
> default. In addition, we can follow the detailed steps to configure the
> Outlook client to connect Exchange mailbox using RPC over HTTP, after we
> logon the RWW and click the "Configure Outlook via the Internet" link.
>
> I am appreciated your time and cooperation. If anything is unclear, please
> feel free to let me know. I am looking forward to hearing from you.
>
> Best regards,
>
> Nathan 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.
>
> --------------------
> >From: "TonyV" <tonyv@xxxxxxxxxx>
> >Newsgroups: microsoft.public.windows.server.sbs
> >Subject: Re: Outlook 2003 client
> >Date: Mon, 15 Aug 2005 18:37:28 +0200
> >Organization: unused
> >Lines: 199
> >Message-ID: <1124123847.957881@xxxxxxxxxxxxxxxxxxxxxxxx>
> >References: <1123769685.940816@xxxxxxxxxxxxxxxxxxxxxxxx>
> <6JZGmhvnFHA.3672@xxxxxxxxxxxxxxxxxxxxx>
> >NNTP-Posting-Host: proxy.storm.co.za
> >X-Trace: ctb-nnrp2.saix.net 1124123848 13999 196.22.192.24 (15 Aug 2005
> 16:37:28 GMT)
> >X-Complaints-To: abuse@xxxxxxxx
> >NNTP-Posting-Date: 15 Aug 2005 16:37:28 GMT
> >X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
> >X-RFC2646: Format=Flowed; Original
> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
> >Cache-Post-Path: proxy.jhb.stormnet.co.za!unknown@xxxxxxxxxxxxxxx
> >X-Cache: nntpcache 3.0.1 (see http://www.nntpcache.org/)
> >Path:
> TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!t-onli
> ne.de!border2.nntp.dca.giganews.com!nntp.giganews.com!nx02.iad01.newshosting
> .com!newshosting.com!ctb-nntp1.saix.net!not-for-mail
> >Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:144504
> >X-Tomcat-NG: microsoft.public.windows.server.sbs
> >
> >The 64k link I'm talking about is permanent between 2 cities (non-VPN). The
> >Outlook user works in a branch office of the company.
> > He is on a different subnet than the SBS server, but on the same side of
> >the ISA firewall than the other LAN users. Therefore there is only 2
> routers
> >between the user and the SBS server.
> >This user is not mobile and never comes into the main office.
> >
> >I went ahead and configured RPC over HTTP anyway.
> >When I accessed https://servername/remote to access RWW, I was prompted
> >about the certificate.
> >I had a look at the certificate status on the SBS Server and it shows 'The
> >CA root certificate is not trusted because it is not in the trusted root
> >certification authorities store'. How do I fix this?
> >
> >This raises another question....Does the user have to be a member of the
> RWW
> >security group to run Outllok in RPC/HTTP mode?
> >
> >
> >
> >""Nathan Liu [MSFT]"" <v-natliu@xxxxxxxxxxxxxxxxxxxx> wrote in message
> >news:6JZGmhvnFHA.3672@xxxxxxxxxxxxxxxxxxxxxxxx
> >> Hello TonyV,
> >>
> >> Thank you for posting in the SBS newsgroup.
> >>
> >> According to your description, I understand that the Outlook 2003 slow
> >> send/receive email, when you are accessing the Exchange mailbox over 64K
> >> link. If I have misunderstood your concern, please don't hesitate to let
> >> me
> >> know.
> >>
> >> First of all, please understand the speed of sending/receiving emails
> >> depend on the speed of the network transport on the Internet, when you
> >> remote access the Exchange Server mailbox through Internet connection.
> >>
> >> To narrow down this issue, please answer and perform the below questions
> >> and steps:
> >>
> >> 1. As you mentioned, "An Outlook 2003 user is accessing his Exchange
> >> mailbox over 64K link. The outlook client is setup in cached mode but not
> >> RPC/HTTP", can I assume the user access the Exchange by using Dial-up VPN
> >> through 64K ISDN internet connection? If so, does the workstation join in
> >> the SBS 2003 Domain?
> >>
> >> 2. Please configure the Outlook 2003 client to connect Exchange mailbox
> >> using RPC over HTTP, and then check if it take effect. To do so, please
> >> perform the below steps:
> >>
> >> a. On the workstation, use the https://Router_Public_IP/remote or
> >> https://SBS2003FQDN/remote link to access the RWW on the SBS 2003 Server.
> >>
> >> b. After logon, please click "Configure Outlook via the Internet" link
> >> to
> >> view the detailed steps to configure the problematic Outlook client to
> >> connect Exchange mailbox using RPC over HTTP.
> >>
> >> c. Please check if the issue can be reproduced.
> >>
> >> 3. Please disable any Anti-Virus or firewall software on the
> >> workstation,
> >> and then check if it take effect.
> >>
> >> 4. Please also try the below steps to check if the issue can be
> >> reproduced:
> >>
> >> Step 1: Starting Outlook in Safe Mode
> >> =========================
> >> Safe Mode will disable all add-ins and extensions that will not start, as
> >> well as any corrupted resources, files, registries and templates.
> >>
> >> a. Close Outlook.
> >>
> >> b. Click Start menu-> Run, type "Outlook /Safe" (without the quotation
> >> marks and there is a space between Outlook and /Safe) in the Open box and
> >> press Enter.
> >>
> >> If issue still persists in safe mode, please perform the next step.
> >>
> >> Step 2: Creating a new Outlook profile
> >> ==========================
> >> Please use the following method to create a new profile to perform a
> test:
> >>
> >> a. Close Outlook.
> >>
> >> b. Click Start menu-> Control Panel. If Control Panel is not in Classic
> >> View, click Switch to Classic View, and then double-click the Mail icon.
> >>
> >> c. Click Show Profiles and then click Add. In the New Profile dialog box,
> >> type a descriptive name for the new profile in the Profile Name box, and
> >> then click OK.
> >>
> >> d. On the pop-up "E-mail Accounts", choose "add a new e-mail account",
> >> click next.
> >>
> >> e. Choose the type of your account, click next.
> >>
> >> f. Input the corresponding info of the mail account, click Next, click
> >> Finish.
> >>
> >> g. On the "Mail" box, click the "Prompt for a profile to be used" option
> >> and click OK. This way, you will be prompted for a profile when starting
> >> Outlook.
> >>
> >> For more information, please refer to the article:
> >>
> >> 829918 How to create a new e-mail profile in Outlook 2003
> >> http://support.microsoft.com/?id=829918
> >>
> >> Start Outlook with the new profile to test the issue again. Is the issue
> >> resolved?
> >>
> >> I am appreciated your time and cooperation. If anything is unclear,
> please
> >> feel free to let me know. I am looking forward to hearing from you.
> >>
> >> Best regards,
> >>
> >> Nathan 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.
> >>
> >> --------------------
> >>>From: "TonyV" <tonyv@xxxxxxxxxx>
> >>>Newsgroups: microsoft.public.windows.server.sbs
> >>>Subject: Outlook 2003 client
> >>>Date: Thu, 11 Aug 2005 16:14:40 +0200
> >>>Organization: unused
> >>>Lines: 19
> >>>Message-ID: <1123769685.940816@xxxxxxxxxxxxxxxxxxxxxxxx>
> >>>NNTP-Posting-Host: proxy.storm.co.za
> >>>X-Trace: ctb-nnrp2.saix.net 1123769686 16256 196.22.192.24 (11 Aug 2005
> >> 14:14:46 GMT)
> >>>X-Complaints-To: abuse@xxxxxxxx
> >>>NNTP-Posting-Date: 11 Aug 2005 14:14:46 GMT
> >>>X-Priority: 3
> >>>X-MSMail-Priority: Normal
> >>>X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
> >>>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
> >>>X-RFC2646: Format=Flowed; Original
> >>>Cache-Post-Path: proxy.jhb.stormnet.co.za!unknown@xxxxxxxxxxxxxxx
> >>>X-Cache: nntpcache 3.0.1 (see http://www.nntpcache.org/)
> >>>Path:
> >>
> TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!t-onli
> >> ne.de!tsicnews.teliasonera.com!ctb-nntp1.saix.net!not-for-mail
> >>>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:143389
> >>>X-Tomcat-NG: microsoft.public.windows.server.sbs
> >>>
> >>>An Outlook 2003 user is accessing his Exchange mailbox over 64K link.
> The
> >>>outlook client is setup in cached mode but not RPC/HTTP.
> >>>He can send and receive mail, but is extremely slow as it shows a
> >>>popup window that says 'Outlook is trying to retrieve data from the
> >>>MSExchange server Servername.domain.local'.
> >>>The mail does eventually get sent/received, and attachment sizes are only
> >>>about 50kb (if any).
> >>>
> >>>This even happens when there is no other users on the line.
> >>>I saw it once trying to syncronise the SENT items, and took about 2
> >> minutes.
> >>>
> >>>I can't figure out why it is so slow. How do I fault find this?
> >>>Please advise.
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>
> >
> >
.

Quantcast