Re: Forcing RPC over HTTP instead of TCP
From: RP (RP_at_discussions.microsoft.com)
Date: 02/01/05
- Next message: Mark Arnold [MVP]: "Re: Pop3 clients on internal network cant connect"
- Previous message: Rob Cawood: "Re: Outlook Clients Free Busy Data Unavailable"
- In reply to: neo [mvp outlook]: "Re: Forcing RPC over HTTP instead of TCP"
- Next in thread: neo [mvp outlook]: "Re: Forcing RPC over HTTP instead of TCP"
- Reply: neo [mvp outlook]: "Re: Forcing RPC over HTTP instead of TCP"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 31 Jan 2005 21:40:32 -0800
They don't support it, but we're trying to eliminate some things. Our desired
config is as follows on the same side of the firewall:
1. DC and GC are same machine (Windows 2003)
2. Front-end Exchange server
3. Back-end Exchange Server
On the hostile side of the firewall is our outlook client. We have enabled
port 443 for the client to establish a connection with the front-end server.
We figured that we would first try to communicate frm the front-end server
to the back-end server using RPC/HTTP to start our troubleshooting. If this
worked we knew we were going in the right direction. The problem is that we
can't even get RPC/HTTP to work when everything is on the same side of the
firewall. I'm trying all kinds of searches in hopes of finding something
which will trigger something for us.
Thanks
"neo [mvp outlook]" wrote:
> Nope.
>
> I don't know why I'm noticing this now, but just to clarify, Outlook &
> Exchange on the same box is not recommended. Last I checked, Microsoft
> doesn't even support this type of configuration.
>
> "RP" <RP@discussions.microsoft.com> wrote in message
> news:97332B08-EEC2-4B49-8CB4-0C6035AA4611@microsoft.com...
> > That didn't work either. Something must be configured wrong. I didn't see
> > the
> > RPC key so I created it. Should it have been there already?
> >
> > thanks
> >
> > "neo [mvp outlook]" wrote:
> >
> >> sorry... dword
> >>
> >> "RP" <RP@discussions.microsoft.com> wrote in message
> >> news:B1A69C54-C3CE-4258-8539-2666BABCB77B@microsoft.com...
> >> > Should this be a string value?
> >> >
> >> > Thanks
> >> >
> >> > "neo [mvp outlook]" wrote:
> >> >
> >> >> To disable Outlook's ability to fallback to using RPC:
> >> >>
> >> >> Value Name: DisableRpcTcpFallback
> >> >> Data: 1
> >> >> Path: HKCU\Software\Microsoft\Office\11.0\Outlook\RPC
> >> >>
> >> >> "RP" <RP@discussions.microsoft.com> wrote in message
> >> >> news:629E2BE6-631B-4412-92D3-6FF40A836EB9@microsoft.com...
> >> >> > I'm in a test environment and have had some problems configuring RPC
> >> >> > over
> >> >> > HTTP so we've decided to back track and take "baby" steps. How can I
> >> >> > force
> >> >> > RPC over HTTP before failing back to TCP/IP. In this environment I'm
> >> >> > using
> >> >> > an
> >> >> > Outlook client which is installed on a Front-end sever (necessary
> >> >> > due
> >> >> > to
> >> >> > limited resources). I'm trying to connect to the back end server and
> >> >> > when
> >> >> > I
> >> >> > connect it indicates that the connection is TCP.
> >> >> >
> >> >> > Any advice, help or assistance is greatly appreciated.
> >> >> >
> >> >> > Thanks
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
>
- Next message: Mark Arnold [MVP]: "Re: Pop3 clients on internal network cant connect"
- Previous message: Rob Cawood: "Re: Outlook Clients Free Busy Data Unavailable"
- In reply to: neo [mvp outlook]: "Re: Forcing RPC over HTTP instead of TCP"
- Next in thread: neo [mvp outlook]: "Re: Forcing RPC over HTTP instead of TCP"
- Reply: neo [mvp outlook]: "Re: Forcing RPC over HTTP instead of TCP"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|