Outlook over HTTP doesn't work, RPCPing error 12044
Ryan
mode but it only connects locally via TCP/IP rather than HTTPS.
This is SBS 2003 standard and the certificate is showing the public FQDN,
the cert from /remote is installed properly on the client. I have also
verified the registry keys are set for the right ports and the server is
listening on 6001,6002, and 6004.
Basically, I can't find anything wrong with the setup and I have set this up
several times before.
I ran the rpcping command below on both a local client and the server and
got the same result.
C:\Program Files\Windows Resource Kits\Tools>rpcping -t ncacn_http -s
EDM-FS1 -o RpcProxy=EDM-FS1 -P "ryanv,cobalt,*" -I "ryanv,cobalt,*" -H 2 -u
10 -a connect -F 3 -v 3 -E -R none
RPCPing v2.12. Copyright (C) Microsoft Corporation, 2002
OS Version is: 5.1, Service Pack 2
Enter password for server:
Enter password for RPC/HTTP proxy:
RPCPinging proxy server EDM-FS1 with Echo Request Packet
Sending ping to server
Error 12044 returned in the WinHttpReceiveResponse.
Ping failed.
Can anyone help me out here?
Rich Matheisen [MVP]
>I can't seem to get Outlook to connect over HTTP. I ran outlook in RPCdiag
>mode but it only connects locally via TCP/IP rather than HTTPS.
Check both the high and low speed connection boxes to force the client
to always usr HTTPS. Outlook will probably still connect to the DC
with TCP, but it should use HTTP for mail.
>This is SBS 2003 standard and the certificate is showing the public FQDN,
>the cert from /remote is installed properly on the client. I have also
>verified the registry keys are set for the right ports and the server is
>listening on 6001,6002, and 6004.
>
>Basically, I can't find anything wrong with the setup and I have set this up
>several times before.
>
>I ran the rpcping command below on both a local client and the server and
>got the same result.
>
>C:\Program Files\Windows Resource Kits\Tools>rpcping -t ncacn_http -s
>EDM-FS1 -o RpcProxy=EDM-FS1 -P "ryanv,cobalt,*" -I "ryanv,cobalt,*" -H 2 -u
>10 -a connect -F 3 -v 3 -E -R none
>RPCPing v2.12. Copyright (C) Microsoft Corporation, 2002
>OS Version is: 5.1, Service Pack 2
>Enter password for server:
>Enter password for RPC/HTTP proxy:
>
>RPCPinging proxy server EDM-FS1 with Echo Request Packet
>Sending ping to server
>Error 12044 returned in the WinHttpReceiveResponse.
>Ping failed.
>
>Can anyone help me out here?
12044 = ERROR_WINHTTP_CLIENT_AUTH_CERT_NEEDED
Are you sure the certificate is correctly installed on the server?
Private and Public keys are present? The client has the root cert of
the CA installed?
--
Rich Matheisen
MCSE+I, Exchange MVP
MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm
Don't send mail to this address mailto:h.p...@getronics.com
Or to these, either: mailto:h.p...@pinkroccade.com mailto:melvin.mcp...@getronics.com mailto:melvin.mcp...@pinkroccade.com
Ryan
"Rich Matheisen [MVP]" wrote:
> Check both the high and low speed connection boxes to force the client
> to always usr HTTPS. Outlook will probably still connect to the DC
> with TCP, but it should use HTTP for mail.
Did that, no difference.
> Are you sure the certificate is correctly installed on the server?
> Private and Public keys are present? The client has the root cert of
> the CA installed?
I followed the steps mentioned within the main RWW page as usual. The
certificate was created through the CEICW wizard and points to the public
fqdn (which resolves to the properly static external IP). I then navigated
to https://mail.domain.com/remote on the client and installed the certificate
to the trusted root authority. Whenever I go back the address bar is now
green and the certificate checks out clean and shows the rigth public fqdn.
There aren't any firewalls running on this SBS server.
Here's what keeps appearing in the IIS logs when I try connecting. I'm not
sure if it means anything:
#Fields: date time s-ip cs-method cs-uri-stem cs-uri-query s-port
cs-username c-ip cs(User-Agent) sc-status sc-substatus sc-win32-status
2008-06-04 21:01:19 192.168.1.10 GET /smex/cgiNotify.exe
SERVER=edm-fs1.domain.local&MESSAGE=2001&UpdateVer=3-4:531700,2-10:8.710.1002,2-1000:8.710.1002,3-800:962,2-21080000:5.32.1011,2-4:8.700.1004,3-20000020:31300,3-20000040:10800,2-21000001:5.2.1032,2-21000002:5.2.1032,3-20001000:651,3-20000400:65100,2-21000080:2.2.1004,3-4000000:15952002,3-10000:15952,2-2000000:5.5.1026,3-80000:86,3-100000:86,3-200:10268,2-400000:1.2.1045&AUTH=dbd69b57adc937c721132e937e314e02
16372 - 192.168.1.10 TMhtload/7.6.1095+(Windows+NT+5.2.3790+Service+Pack+2)
200 0 0
Andrew Sword [MVP]
http://support.microsoft.com/kb/827330
"Ryan" <Ry...@discussions.microsoft.com> wrote in message
news:4B7420F0-99C5-4EA1...@microsoft.com...
Rich Matheisen [MVP]
>
>
>"Rich Matheisen [MVP]" wrote:
>> Check both the high and low speed connection boxes to force the client
>> to always usr HTTPS. Outlook will probably still connect to the DC
>> with TCP, but it should use HTTP for mail.
>
>Did that, no difference.
Then there's a problem with the client. If the only possibility is to
use HTTPS and it's not using it then there's something wrong.
After you changed the situation so both boxes were checked, did you
restart Outlook?
Are there other application running on the client that share the
Outlook profile's connection to Exchange? Even something that's
seemingly innocuous, like MS Word, can do that. So can desktop search
engines, MS Office Communicator, and others. If it's easier to reboot
than to kill them, try that. But the client should either connect with
HTTPS or fail -- it shouldn't use TCP/IP to connect to the mailbox and
public folder server(s).
[ snip ]
>Here's what keeps appearing in the IIS logs when I try connecting. I'm not
>sure if it means anything:
>
>#Fields: date time s-ip cs-method cs-uri-stem cs-uri-query s-port
>cs-username c-ip cs(User-Agent) sc-status sc-substatus sc-win32-status
> 2008-06-04 21:01:19 192.168.1.10 GET /smex/cgiNotify.exe
>SERVER=edm-fs1.domain.local&MESSAGE=2001&UpdateVer=3-4:531700,2-10:8.710.1002,2-1000:8.710.1002,3-800:962,2-21080000:5.32.1011,2-4:8.700.1004,3-20000020:31300,3-20000040:10800,2-21000001:5.2.1032,2-21000002:5.2.1032,3-20001000:651,3-20000400:65100,2-21000080:2.2.1004,3-4000000:15952002,3-10000:15952,2-2000000:5.5.1026,3-80000:86,3-100000:86,3-200:10268,2-400000:1.2.1045&AUTH=dbd69b57adc937c721132e937e314e02
>16372 - 192.168.1.10 TMhtload/7.6.1095+(Windows+NT+5.2.3790+Service+Pack+2)
>200 0 0
That doesn't look relevant. I don't know what you're running on the
machine that uses the "smex" virtual directory, but that's what that
log file line is telling you you're connecting to. Also, the status is
"200" and that says whatever it is is working just fine. :-)
Ryan
Thanks for continuing to help me with this.
"Rich Matheisen [MVP]" wrote:
> After you changed the situation so both boxes were checked, did you
> restart Outlook?
Yes, Outlook has been restarted several times.
> Are there other application running on the client that share the
> Outlook profile's connection to Exchange? Even something that's
> seemingly innocuous, like MS Word, can do that. So can desktop search
> engines, MS Office Communicator, and others. If it's easier to reboot
> than to kill them, try that. But the client should either connect with
> HTTPS or fail -- it shouldn't use TCP/IP to connect to the mailbox and
> public folder server(s).
No other programs are running and I just did a reboot and still have the
same issue.
I also followed all the steps in the troubleshooting guide Andrew posted a
link to but everything checked out exactly how it's supposed to be. Every
SBS 03 install I've done Outlook over HTTP ran fine out of the box. I didn't
install SBS in this situation but I compared every setting I can think of to
a functional SBS server with exchange over http and the settings are the same
(besides different fqdn,certs, and server names obviously)
Rich Matheisen [MVP]
[ snip ]
>No other programs are running and I just did a reboot and still have the
>same issue.
You're not running Outlook /ON/ the Exchange server, are you? You're
running it on a workstation/laptop, right?
What you're describing is that Outlook isn't using HTTPS even if you
tell it to.
Have you tried this connectivity from another client? Have you created
a new Outlook profile?
>I also followed all the steps in the troubleshooting guide Andrew posted a
>link to but everything checked out exactly how it's supposed to be. Every
>SBS 03 install I've done Outlook over HTTP ran fine out of the box. I didn't
>install SBS in this situation but I compared every setting I can think of to
>a functional SBS server with exchange over http and the settings are the same
>(besides different fqdn,certs, and server names obviously)
I'm running out of ideas. :-)