Re: RPC over HTTP problem for some users only

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


.

Relevant Pages

  • RE: Outlook indefinitely "trying to connect ..." to Exchange 2003 using RPC/HTTP
    ... I understand that your issue is that the outlook ... sometime does not work when using RPC over HTTP. ... If you use the RPC over HTTP when using the WLAN for the connection, ...
    (microsoft.public.windows.server.sbs)
  • Re: Problem Connecting to Exchange Server from Outlook
    ... Teach Yourself Outlook 2003 in 24 Hours ... Outlook & Exchange Solutions Center: http://www.slipstick.com ... The connection to the Microsoft ... Exchange Server is unavailable. ...
    (microsoft.public.outlook)
  • Re: HTTP Connection to Exchange from Outlook
    ... is a way to connect using HTTP in a way that would look like a VPN connection ... email account (in Outlook) that will connect them to our Exchange Server. ... using some sort of HTTP connection. ...
    (microsoft.public.exchange.clients)
  • Re: HTTP Connection to Exchange from Outlook
    ... You need a SSL connection for your Exchange Server, for the FQDN Exchange machine. ... > email account (in Outlook) that will connect them to our Exchange> Server. ...
    (microsoft.public.exchange.clients)
  • Re: Outlook Vs Outlook Anywhere
    ... We've many users who go overseas and hook up in hotels and then find that because the hotel LAN is on the same IP range as the office LAN they cannot resolve the Exchange server fqdn. ... outlook as though they were on the LAN. ... IIRC, prior to SBS 2003, VPN used to be the only way to allow remote ... > Anywhere type connection as opposed to regular Outlook connected to> Exchange ...
    (microsoft.public.windows.server.sbs)