Re: SBS 2003, Outlook 2003, and RPC-HTTP

From: Matt Gibson (mattg_at_blueedgetech.ca)
Date: 01/07/05


Date: Fri, 7 Jan 2005 13:01:56 -0800

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.



Relevant Pages

  • Re: Problem with multiple access to one exchange email account
    ... The emails are hosted on the SBS exchange server using SMTP protocal. ... The users' Outlook accounts are connected by selecting exchange server ...
    (microsoft.public.windows.server.sbs)
  • Re: Problem with multiple access to one exchange email account
    ... The emails are hosted on the SBS exchange server using SMTP protocal. ... The users' Outlook accounts are connected by selecting exchange server ...
    (microsoft.public.windows.server.sbs)
  • RE: Exchange connectivity issue question
    ... "Log stalls are a common cause of Outlook access issues. ... Nuevo, by separate spindles, do you mean a new RAID controller with new ... “connecting to exchange server” style pop up and the end users having to wait ... while the outlook clients try and talk to our Exchange server, ...
    (microsoft.public.exchange.admin)
  • RE: Created a new mailbox but cant access it via Outlook or OWA
    ... The permissions on the exchange server may be modified. ... Mailboxes to Your Outlook Profile ... 40037315-Created a new mailbox but can't access it via Outlook or OWA. ...
    (microsoft.public.windows.server.sbs)
  • Re: Outlook 2003, Pop, Exchange Server
    ... Windows XP users using Outlook 2003 can connect directly to the MailStreet ... connecting to an Exchange 2003 server via HTTPs gives you ... delivery location to a personal folder file, ... > with the exchange server, can I just add the exchange server to the ...
    (microsoft.public.outlook.general)