Outlook 2003 RPC HTTP problem

  • Thread starter Thread starter Gary Smith
  • Start date Start date
G

Gary Smith

Hello,

I have been searching the groups now for some information regarding
the RPC over HTTP and have found much useful but then again useless
information.

I am trying to setup my laptop. I upgraded Office XP to Office 2003
today and then tried to setup the RPC. When I go the options under
profile to edit the Exchange server settings I get the Microsoft
Exchange Server box, Use Cache Exchange Mode checkbox (right
underneath the other box) and then the User Name box. Also when I go
to more settings then to connections I have nothing in the lower half
of that tab.

My backend environment is a mixed mode of 3 servers. I have an
Exchange 2000 backend, Exchange 2003 backend and a Exchange 2003
frontend server.

The account that I'm trying to configure is on the Exchange 2003
backend.

All of the articles (including screen shots) seem to show a different
box for editing the Exchange Server settings than what I get. I am
running the Professional version.


Am I just missing something simple?

Gary Smith
 
neo said:
You need to be running Windows XP (SP1) with patch
http://support.microsoft.com/default.aspx?scid=kb;en-us;331320. Outside of
that, I will assume that the site has configured Exchange 2003 on Windows
2003 and the domain controller/global catalogs are all up to snuff.

I did verify that this was installed. Does it matter that my domain
is based on Windows 2000. I have two Windows 2003 servers (the back
end and the front end servers only). I did run forestprep and
domainprep prior to installing the software when I built it.

Gary
 
DC/GCs must be Windows 2003 servers and be configured properly to accept a
RPC proxy call. There is a really good deployment whitepaper for Exchange
2003 that covers RPC/HTTP and its requirements at
http://www.microsoft.com/exchange. (it is a little long, but has great info
inside about the new technology.)

Cheers,
/Neo

ps - domain functionality level doesn't matter (can be mixed, windows 2000,
or windows 2003 level). only requirement is that dc/gcs are at windows 2003
server, exchange 2003 on windows 2003, and clients are windows xp (sp1) +
the patch or better.

Gary Smith said:
"neo [mvp outlook]" <[email protected]> wrote in message
You need to be running Windows XP (SP1) with patch
http://support.microsoft.com/default.aspx?scid=kb;en-us;331320. Outside of
that, I will assume that the site has configured Exchange 2003 on Windows
2003 and the domain controller/global catalogs are all up to snuff.

I did verify that this was installed. Does it matter that my domain
is based on Windows 2000. I have two Windows 2003 servers (the back
end and the front end servers only). I did run forestprep and
domainprep prior to installing the software when I built it.

Gary
 
The introduction of the article itself exlpains it. I only upgrade to
Exchange 2003. We will rollout Windows 2003 In a couple months.
Still recooping from the cost of the other software.

I should have done a little more searching on the MS site first. The
RPC over HTTP wasn't the primary reason for the install anyways. It
was just one of those extra benefits.

Thanks for the help,

Gary

neo said:
DC/GCs must be Windows 2003 servers and be configured properly to accept a
RPC proxy call. There is a really good deployment whitepaper for Exchange
2003 that covers RPC/HTTP and its requirements at
http://www.microsoft.com/exchange. (it is a little long, but has great info
inside about the new technology.)

Cheers,
/Neo

ps - domain functionality level doesn't matter (can be mixed, windows 2000,
or windows 2003 level). only requirement is that dc/gcs are at windows 2003
server, exchange 2003 on windows 2003, and clients are windows xp (sp1) +
the patch or better.

Gary Smith said:
"neo [mvp outlook]" <[email protected]> wrote in message
You need to be running Windows XP (SP1) with patch
http://support.microsoft.com/default.aspx?scid=kb;en-us;331320. Outside of
that, I will assume that the site has configured Exchange 2003 on Windows
2003 and the domain controller/global catalogs are all up to snuff.

I did verify that this was installed. Does it matter that my domain
is based on Windows 2000. I have two Windows 2003 servers (the back
end and the front end servers only). I did run forestprep and
domainprep prior to installing the software when I built it.

Gary
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top