Re: SBS 2003, Outlook 2003, and RPC-HTTP
From: Matt Gibson (mattg_at_blueedgetech.ca)
Date: 01/09/05
- Next message: Matt Gibson: "Re: Moving to new Server"
- Previous message: hooutoo_at_gmail.com: "Re: Sub Domains"
- In reply to: James: "Re: SBS 2003, Outlook 2003, and RPC-HTTP"
- Next in thread: James: "Re: SBS 2003, Outlook 2003, and RPC-HTTP"
- Reply: James: "Re: SBS 2003, Outlook 2003, and RPC-HTTP"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 8 Jan 2005 16:39:58 -0800
Okay :)
First of all, if you DON'T install that certificate, nothing will work.
So do that right off the bat.
Secondly, during the account setup, some of the refrences will be to
mail.exchangeserver.local, and some will be to mail.exchangeserver.com. You
can't just mix and match them.
If you go into your e-mail account, hit change...the first window that pops
up should have mail.exchange server.local. WHen you go into the exchange
proxy settings, the first textbox should be mail.exchangeserver.com. Put in
msstd:mail.exchangeserver.com in the second. That isn't optional.
Rerun the internet connection wizard. Make sure that your web certificate
name is mail.exchangeserver.com
Give that a shot.
-Matt
"James" <James@discussions.microsoft.com> wrote in message
news:B2E51347-AF6E-4D32-8B81-3BC32E3A6350@microsoft.com...
> If you browse to https://mail.exchangeserver.com/rpc do you get a
> certificate warning?
> - yes, I'm warned the the security certificate was issured by a company I
> have not chosen to trust. But it also states the certificate is valid
> and
> it's name matches the name of the page to be viewed. After clicking yes
> to
> proceed, a challenge box appears.
> Should I install the certificate on the client machine, instead of just
> proceeding?
>
>
> You've installed the hotfix?
> - no hotfixes have been install. XP Pro and Office 2003 are both up to
> date
> with the latest services packs. The one hotfix I found relating to this
> wouldn't install because XP server pack 2 was installed.
>
>
> In outlook, if you go to your e-mail accounts, you're referring to your
> exchange server by it's internal name?
> - if your referring to the 'E-Mail Accounts' box that list email accounts
> in
> order to process (listing by Name and Type) and you can set one to
> Default...
> then no. It's listing is 'Microsoft Exchange Server' Type: 'Exchange
> (Default).
> Does the certificate name and the account listing need to be the same?
>
>
> Under the Exchange Proxy settings in Outlook, you've got the first textbox
> as mail.exchangeserver.com ?
> - the differents between the internal name and external is '.local' and
> '.com' (name.domain.local or name.domain.com). I've been using 'local'
> for
> internal testing and 'com' for external clients. Thought I have switched,
> mixed and match just to see if I was using the wrong name.
>
>
> Under the second, you've got msstd:mail.exchangeserver.com ?
> - no, I have not been filling in this box. FAQ's and docs I've read have
> left this as optional.
> Should this information be enter?
>
> And then you've got Basic AUthentication selected at the bottom?
> - yes, Basic Authentication is selected (since SSL is being used).
>
> Thanks for you help Matt.
>
>
> "Matt Gibson" wrote:
>
>> If you browse to https://mail.exchangeserver.com/rpc do you get a
>> certificate warning?
>>
>> You've installed the hotfix?
>>
>> Firewall won't matter as long as it's passing 443 traffic.
>>
>> In outlook, if you go to your e-mail accounts, you're referring to your
>> exchange server by it's internal name?
>>
>> Under the Exchange Proxy settings in Outlook, you've got the first
>> textbox
>> as mail.exchangeserver.com ?
>>
>> Under the second, you've got msstd:mail.exchangeserver.com ?
>>
>> And then you've got Basic AUthentication selected at the bottom?
>>
>> -Matt
>>
>> "James" <James@discussions.microsoft.com> wrote in message
>> news:A6577D82-4A04-4841-B751-51959F5B5EB6@microsoft.com...
>> > I've been working my way through setting up a RPC-HTTP connection
>> > between
>> > Outlook 2003 and Exchange 2003. It's to the point that an internal
>> > (within
>> > the local network and domain) RPC-HTTP connection seems to work fine.
>> > Also,
>> > I've used IE to connect to Exchange's RPC folder (example -
>> > https://mail.exchangeserver.com/rpc and then filled out a challenge box
>> > for
>> > user name and password). The proper error page shows up (403.2
>> > Forbidden:
>> > Read access is denied) and everything seems fine.
>> > But Outlook can't find the server. I've made repeated attempts to
>> > connect
>> > with Outlook in rpc diagnostic mode (DOS box - "outlook /rpcdiag") and
>> > get
>> > the challenge box for user name and pass; but it never finds an
>> > Exchange
>> > server. I've tried to put the user name in different formats:
>> > domain_name\user_name, server_name\user_name, just user_name, and so
>> > on;
>> > just
>> > to see if it mattered.
>> > There is a PIX 501 firewall sitting between external clients and the
>> > Exchange server. The PIX is setup to allow/pass traffic from ports 80
>> > (HTTP)
>> > and 443(HTTPS) to the Exchange server. Since the RPC packets are being
>> > moved
>> > via HTTP, I have not punch a hole for RPC in the firewall.
>> > The Exchange I'm using is part of the Small Business Server 2003
>> > package.
>> > SBS made it easy to setup the Exchange side of RPC-HTTP (a wizard and a
>> > check
>> > box later it was ready) and I've gone through different 'How to' FAQs
>> > that
>> > verified Exchange's setting are correct. So I'm left with the firewall
>> > and/or the client.
>> >
>> > Any help on this would be great.
>> >
>> > Thanks.
>>
>>
>>
- Next message: Matt Gibson: "Re: Moving to new Server"
- Previous message: hooutoo_at_gmail.com: "Re: Sub Domains"
- In reply to: James: "Re: SBS 2003, Outlook 2003, and RPC-HTTP"
- Next in thread: James: "Re: SBS 2003, Outlook 2003, and RPC-HTTP"
- Reply: James: "Re: SBS 2003, Outlook 2003, and RPC-HTTP"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
