Re: RPC over HTTP problem for some users only
- From: "neo [mvp outlook]" <neo@xxxxxxxxxxxxxxx>
- Date: Wed, 14 Dec 2005 04:26:26 -0800
I don't have any experience with NLB clusters when it comes to FEs, but I
think the change only has to be done on the BEs. I'm trying to get
clarification from the exchange mvps just to make sure that i give you good
info.
/neo
"Rich Bashaw" <RichBashaw@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:16103E73-39AE-4E33-817C-4CBE3A588678@xxxxxxxxxxxxxxxx
> It did contain DC/GC reference. I deleted it and relaunched Outlook. Same
> problem and it recreated the same registry key.
>
> I did have my Outlook configured to use HTTP on a fast connection and I
> even
> went further and added the DisableRpcTcpFallback registry kety to force it
> to
> use HTTP and it failed to connect at all.
>
> Internal DNS uses the same FQDN so that it matches the SSL cert, it just
> resolves to a private IP rather than a public one. As an experiment, I
> added
> a HOSTS file entry for the external IP of the RPCProxy server, and it
> tried
> harder to connect. It gets a Mail and a Referal with HTTPS and then hangs.
>
> Maybe I should try the RFR reg key. Do I do that on the RPC PRoxy server
> only or all backend servers as well?
>
> We have 2 NLB front end exchange servers (RPCPRoxy is the Virtual IP of
> this
> NLB cluster) and about 5 backend servers the main one is a Windows
> Active/Passive cluster.
>
> "neo [mvp outlook]" wrote:
>
>> Double click on it and see if it contains a reference to a DC/GC. Not
>> sure
>> how big your site is, but I'm half tempted to point you at
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;282446&sd=RMVP
>> and
>> say set the "No RFR Service" registry value. This will cause the
>> Exchange
>> 200x boxes to proxy all GC calls. (If you do set it, restart exchange
>> services, and then delete the value you/i have on the client workstation.
>> once that is done, outlook 2003's rpc diagnostic dialog should show
>> exchange
>> handling directory calls.)
>>
>> The default connection methodology for Outlook 2003 when RPC/HTTP is
>> configured:
>> Fast (broadband or better) - TCP/IP then HTTP
>> Slow (128k or slower) - HTTP then TCP/IP
>>
>> A user can check the box in the proxy settings where Outlook will try
>> HTTP
>> first on a fast connection. If yours is this way, then there are some
>> things one could do to stop the connection. For example:
>>
>> 1) The RPCProxy folder in IIS is configured to prohibit connections from
>> internal IP addresses
>>
>> 2) Filtering on the VPN connection
>>
>> 3) Different name resolution strategy for internal vs. external users
>> (e.g.
>> example, lets say the exchange proxy server's external dns address is
>> outlook.contoso.com. internally, this entry might not exist.)
>>
>>
>> "Rich Bashaw" <RichBashaw@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:08D727EA-FE30-4C40-A7A2-00A367BFDD26@xxxxxxxxxxxxxxxx
>> >I have a 001f662a, but that is all.
>> >
>> > I have noticed another difference. When I connect from home over the
>> > Internet, every thing works fine. When I connect my VPN and then
>> > beccome
>> > part
>> > of the same subnet as the mail server, it fails for RPC over HTTP and
>> > defaults to TCP/IP. Is there a reason it would not work when I am on
>> > the
>> > same
>> > subnet?
>> >
>> > "neo [mvp outlook]" wrote:
>> >
>> >> Assuming that there are no issues with web server certificate for the
>> >> rpcproxy folder in IIS (e.g. hitting it with the web browser does not
>> >> generate the security prompt about the certificate), the only thing
>> >> that
>> >> comes to my mind is where Outlook is trying to authenticate to a GC
>> >> over
>> >> RPC/HTTPS.
>> >>
>> >> As of SP1/2 for Exchange 2003, GCs are no longer advertised via
>> >> DSProxy
>> >> for
>> >> RPC/HTTP clients. If you can, see if one of your customers is willing
>> >> to
>> >> open regedit and motor to:
>> >>
>> >> HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows
>> >> Messaging
>> >> Subsystem\Profiles\<profile>\dca740c8c042101ab4b908002b2fe182
>> >>
>> >> If the string value 001e6602 exists, delete it.
>> >>
>> >> By the way, when you guys tried a new mail profile. Did you delete
>> >> the
>> >> existing mail profile and then recreate it with the same name or
>> >> create a
>> >> new one and then delete the old?
>> >>
>> >> /neo
>> >>
>> >> PS - the value should be removed while Outlook is closed.
>> >>
>> >>
>> >> "Rich Bashaw" <RichBashaw@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> >> news:A0E80BE8-CB3F-4ACB-8FF8-2C6427FB27C9@xxxxxxxxxxxxxxxx
>> >> > We have RPC over HTTP enable and it is working for some users.
>> >> > Others
>> >> > cannot
>> >> > connect at all. We have tried new profiles to no avail. The only
>> >> > thing
>> >> > that
>> >> > seems to work is a fresh install of Office 2003 on the machine. And
>> >> > sometimes
>> >> > that doesn't work either. Sometimes you need to reinstall the OS and
>> >> > Office.
>> >> > We have a lot of users offsite and we would like to avoid having to
>> >> > reinstall
>> >> > for all of them. They all have the correct versions of Office and
>> >> > Windows.
>> >> >
>> >> > These offsite user used to be part of a different domain. We
>> >> > migrated
>> >> > the
>> >> > office to a new exchange server and a new user account. They were
>> >> > previously
>> >> > connected to a SBS server and using RPC over HTTP.
>> >> >
>> >> > What I would like to know is if there are certain regisrty settings
>> >> > that I
>> >> > can check and fix rather than doing a complete reinstall.
>> >> >
>> >> > Thanks,
>> >> >
>> >> > Rich
>> >>
>> >>
>> >>
>>
>>
>>
.
- Follow-Ups:
- Re: RPC over HTTP problem for some users only
- From: Rich Bashaw
- Re: RPC over HTTP problem for some users only
- References:
- Re: RPC over HTTP problem for some users only
- From: neo [mvp outlook]
- Re: RPC over HTTP problem for some users only
- From: Rich Bashaw
- Re: RPC over HTTP problem for some users only
- From: neo [mvp outlook]
- Re: RPC over HTTP problem for some users only
- From: Rich Bashaw
- Re: RPC over HTTP problem for some users only
- Prev by Date: Re: RPC over HTTP problem for some users only
- Next by Date: Re: Attachments
- Previous by thread: Re: RPC over HTTP problem for some users only
- Next by thread: Re: RPC over HTTP problem for some users only
- Index(es):
Relevant Pages
|