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.

Thanks in advance for any ideas. - Russ

Hi xrbbaker,

Please check this http://support.microsoft.com/?id=913843

Iverson Xue

"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.

Thanks in advance for any ideas. - Russ

The service provider remoted in to my server machine and ensured that
everything was configured correctly - and it still didn't work. It never
gets past authentication. He even used his own configuration for his account
and it didn't work either. I think it must be an OS issue.

thanks much




"Iverson Xue" wrote:

Hi xrbbaker,

Please check this http://support.microsoft.com/?id=913843

Iverson Xue

"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.

Thanks in advance for any ideas. - Russ