Re: RPC over HTTP

From: RMacleod (pipermacleod2002_at_yahoo.com)
Date: 04/01/04 

Date: 1 Apr 2004 12:36:40 -0800

valt@online.microsoft.com (Val Tuckett [MSFT]) wrote in message news:<xnfPBT3FEHA.2956@cpmsftngxa06.phx.gbl>...
> >>It is likely that your Outlook 2003 client is detecting
> a 'fast' network
> >>connection to your Exchange environment when using DSL
> or Cable, thus is
> >>using TCP/IP.
> >>
> >>Try checking the following option - Email Accounts >
> More Settings >
> >>Connection Tab > Exchange Proxy Settings:
> >>'On fast networks, connect using HTTP first, then
> >connect using TCP/IP'
> >
> >Nope. Checked that. I'm thinking that the gateways my
> >cablemodem people are using are blocking something
> >important. Any ideas as to what?
> >
>
> The RPC traffic is encapsulated within HTTP packets, so it is unlikely they
> are blocking anything relating to this traffic (port 80).
>
> Try hard coding your Outlook 2003 client to only use HTTP(s) using this
> registry key:
>
> HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook
> DWORD = RPC::DisableRpcTcpFallback
> Value = 1
>
> This will disable the failover ability of the client, so remember to
> disable it once you have finished troubleshooting.
>
> Otherwise, use the RPCPing command to verify RPC over HTTP connection
> without the use of Outlook 2003. Bring up a CMD box on your client and type
> the following, replacing ExchServer and RPCProxyServer with their valid
> servernames.
>
> rpcping -t ncacn_http -s ExchServer -o RpcProxy=RpcProxyServer -P
> "user,domain,*" -I "user,domain,*" -H 1 -u 10 -a connect -F 3 -v 3 -E -R
> none
>
> You can read through this KB for more details and steps to verify your
> setup.
> 827330 How to troubleshoot client RPC over HTTP connection issues in
> Office
> http://support.microsoft.com/?id=827330
>
> Regards,
> Val
>
> ----
> Val Tuckett
> Microsoft PSS
>
> This posting is provided 'AS IS' with no warranties and confers no rights.
> Please do not send email directly to this alias. This alias is for
> newsgroup purposes only.

That link does not work and a search on 827330 results in nothing.

Relevant Pages

  • RE: Connect Computer and VPN
    ... The RPC filter that we disabled can be enabled (if required for other ... Try to telnet 80 port from client to SBS, ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • Help w/ RPC_S_PROTOCOL_ERROR... on vista!!! please help
    ... I have an RPC Client/Server all of the stubs are created from an .idl ... This rpc interface also uses context handles and "async", ... The server application is a user mode app that helps w/ managing ... The client side is a dll, it is specifically an eappeer dll which get's ...
    (microsoft.public.win32.programmer.kernel)
  • Re: Outlook HTTPS over RPC error - Inconsistent users
    ... Outlook 2003 clients would fail to connect to Exchange 2003 using RPC over ... HTTPS if there is a problem with the certificate assigned to the ... No RPC remote certificate or Root CA certificate on the client. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 and Outlook RPC over HTTP issues
    ... it was an issue with IIS the setting "Accept Client ... Certificates" was checked and I had to set that to "Ignore Client ... that port 443 and port 80 must be open to use RPC over HTTP. ... I have about 20 of these SBS machines at other locations and have ...
    (microsoft.public.windows.server.sbs)
  • RPC Problem with WinXP SP2
    ... I have a Client application which is installed on a Windows XP SP 2 box. ... On start-up the application connects to the application server. ... own RPC Server, to which the application server is intended to ... This RPC connection is used to inform the client app. ...
    (microsoft.public.win32.programmer.networks)