RPC over HTTPS for Exchange

Outlook 2003 on Win2003 x64 server Terminal Session

With Microsoft paid support we proved that my machine can support Outlook
RPCoHTTPS. He config'd his user acct & exchange settings and we ran fine.
When I config my profile exactly (only diff is no cache) as settings on my XP
Pro desktop, it fails to connect. Since we know the machine supports RPCo
HTTPS our conclusion is that it must be either some kind of Cert problem or
User credential problem.

I am using exact user info as I do on desktop that works. Maybe server OS
resolves things differently?? Every time I attempt to connect, it comes back
with a message saying either "Exchange server unavailable" or "You must be
logged on to Outlook first..." Each connection throws an Error in the Event
Log like:

"Windows cannot determine the user or computer name. (The system detected a
possible attempt to compromise security. Please ensure that you can contact
the server that authenticated you. ). Group Policy processing aborted."
Source: Userenv

I run Outlook in /rpcdiag mode and can see that it only gets to the
Connecting... status, but never connects. I could really use some help on
this. Oh yeah - this machine does have IE 7 and desktop is older.

Thanks in advance for any ideas. - Russ

Re: RPC over HTTPS for Exchange

I suggest asking your question in an Exchange-specific newsgroup, such
as:
microsoft.public.exchange.clients
microsoft.public.exchange.setup

Your issue does not sound like it has to do with IIS. Even the failure
event does not have to do with IIS.

My guess is that your profile is somehow using an Intranet machine name
which does not resolve over the Internet with RPC over HTTP. Did you
ever see RPC over HTTP work with an Internet machine against your x64
Windows Server 2003 machine?


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//


xrbbaker wrote:
> Outlook 2003 on Win2003 x64 server Terminal Session
>
> With Microsoft paid support we proved that my machine can support Outlook
> RPCoHTTPS. He config'd his user acct & exchange settings and we ran fine.
> When I config my profile exactly (only diff is no cache) as settings on my XP
> Pro desktop, it fails to connect. Since we know the machine supports RPCo
> HTTPS our conclusion is that it must be either some kind of Cert problem or
> User credential problem.
>
> I am using exact user info as I do on desktop that works. Maybe server OS
> resolves things differently?? Every time I attempt to connect, it comes back
> with a message saying either "Exchange server unavailable" or "You must be
> logged on to Outlook first..." Each connection throws an Error in the Event
> Log like:
>
> "Windows cannot determine the user or computer name. (The system detected a
> possible attempt to compromise security. Please ensure that you can contact
> the server that authenticated you. ). Group Policy processing aborted."
> Source: Userenv
>
> I run Outlook in /rpcdiag mode and can see that it only gets to the
> Connecting... status, but never connects. I could really use some help on
> this. Oh yeah - this machine does have IE 7 and desktop is older.
>
> Thanks in advance for any ideas. - Russ

Re: RPC over HTTPS for Exchange

Thanks. I have it posted in Exchange as well, but this is one of those
things where it is definitely grey as to what is the cause.

My Microsoft guy had me key in the config for his Outlook client, which
connects to his company's Exchange server in India. It worked fine so we
were able to validate RPCoHTTP for Outlook works fine. For some reason when
I config for my setup, (Exchange server is in another state and hosted by a
Service Provider), it can't seem to connect. When I simply click on the
Check Name button, it is unable to resolve. What doesn't make sense to me is
that on my XP desktop, same LAN, same config, same userid, the Check Name
resolves perfectly fine. Hence, to me it looks like some kind of
name/credential resolution problem that only occurs on the Server. So is
this an Outlook/Exchange, or Windows Server 2003 x64 OS, or Terminal
Services, or Security issue???? I think if I knew that for sure I'd be a lot
closer to resolving. Thanks for your insight. Any more greatly appreciated.



"David Wang" wrote:

> I suggest asking your question in an Exchange-specific newsgroup, such
> as:
> microsoft.public.exchange.clients
> microsoft.public.exchange.setup
>
> Your issue does not sound like it has to do with IIS. Even the failure
> event does not have to do with IIS.
>
> My guess is that your profile is somehow using an Intranet machine name
> which does not resolve over the Internet with RPC over HTTP. Did you
> ever see RPC over HTTP work with an Internet machine against your x64
> Windows Server 2003 machine?
>
>
> //David
> http://w3-4u.blogspot.com
> http://blogs.msdn.com/David.Wang
> //
>
>
> xrbbaker wrote:
> > Outlook 2003 on Win2003 x64 server Terminal Session
> >
> > With Microsoft paid support we proved that my machine can support Outlook
> > RPCoHTTPS. He config'd his user acct & exchange settings and we ran fine.
> > When I config my profile exactly (only diff is no cache) as settings on my XP
> > Pro desktop, it fails to connect. Since we know the machine supports RPCo
> > HTTPS our conclusion is that it must be either some kind of Cert problem or
> > User credential problem.
> >
> > I am using exact user info as I do on desktop that works. Maybe server OS
> > resolves things differently?? Every time I attempt to connect, it comes back
> > with a message saying either "Exchange server unavailable" or "You must be
> > logged on to Outlook first..." Each connection throws an Error in the Event
> > Log like:
> >
> > "Windows cannot determine the user or computer name. (The system detected a
> > possible attempt to compromise security. Please ensure that you can contact
> > the server that authenticated you. ). Group Policy processing aborted."
> > Source: Userenv
> >
> > I run Outlook in /rpcdiag mode and can see that it only gets to the
> > Connecting... status, but never connects. I could really use some help on
> > this. Oh yeah - this machine does have IE 7 and desktop is older.
> >
> > Thanks in advance for any ideas. - Russ
>
>