RPC over HTTP
Exchange Server Forum Index Exchange Server
Discussion forums for Microsoft Exchange Server users.
Microsoft Outlook
 
 FAQFAQ   MemberlistMemberlist     RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
 
Google
 
Web ExchangeServerHelp.com
RPC over HTTP

 
Post new topic   Reply to topic    Exchange Server Forum Index -> Connectivity
Author Message
Grant
Guest
Posted: Tue Jan 04, 2005 8:56 pm    Post subject: RPC over HTTP Reply with quote
Hello,

Ive got an exchange front end proxy server but would like to set up another.
The reason is that clients in London get redirected all the way back to
australia and then internally back to the london exchange server again. I
want to set up another proxy in London so that they go straight into the
server here instead of being routed around the globe.

This is using Exchange 2003 SP1. Ive tried this article:
http://www.microsoft.com/technet/prodtechnol/Exchange/guides/E2k3RPCHTTPDep/1583ab17-f7d1-41c1-ba52-37ec276e3644.mspx

but no joy. We only have a single exchange server here in London so can it
be set up as the front end proxy and back end, co-existing with the proxy in
Australia?

Appreciate any help on this,
Thanks,
Grant

Back to top
Mark Arnold [MVP]
Guest
Posted: Wed Jan 05, 2005 2:04 am    Post subject: Re: RPC over HTTP Reply with quote
On Tue, 4 Jan 2005 14:56:15 -0000, "Grant" <gpsnett@hotmail.com>
wrote:

Quote:
Hello,

Ive got an exchange front end proxy server but would like to set up another.
The reason is that clients in London get redirected all the way back to
australia and then internally back to the london exchange server again. I
want to set up another proxy in London so that they go straight into the
server here instead of being routed around the globe.

This is using Exchange 2003 SP1. Ive tried this article:
http://www.microsoft.com/technet/prodtechnol/Exchange/guides/E2k3RPCHTTPDep/1583ab17-f7d1-41c1-ba52-37ec276e3644.mspx

but no joy. We only have a single exchange server here in London so can it
be set up as the front end proxy and back end, co-existing with the proxy in
Australia?

Appreciate any help on this,
Thanks,
Grant

It's can't be a front end and a back end at the same time.

I would suggest that you configure a fresh server as a front end and
expose it to the Internet.
You're in luck since you already know that the BE is configured
correctly. Simply follow the guidelines and configure the new box in
the same manner as the existing. Should be easy since you have access
to the existing FE.
Back to top
Grant
Guest
Posted: Wed Jan 05, 2005 4:08 pm    Post subject: Re: RPC over HTTP Reply with quote
Thanks for the reply. service pack 1 tightens that up a bit then. The
documentation (pre-sp1) says that you can have the server as both a proxy
and backend.

Cheers,
Grant

"Mark Arnold [MVP]" <mark@mvps.org> wrote in message
news:hjtlt01jro56h5dh14qgijvjmieaad72kc@4ax.com...
Quote:
On Tue, 4 Jan 2005 14:56:15 -0000, "Grant" <gpsnett@hotmail.com
wrote:

Hello,

Ive got an exchange front end proxy server but would like to set up
another.
The reason is that clients in London get redirected all the way back to
australia and then internally back to the london exchange server again. I
want to set up another proxy in London so that they go straight into the
server here instead of being routed around the globe.

This is using Exchange 2003 SP1. Ive tried this article:
http://www.microsoft.com/technet/prodtechnol/Exchange/guides/E2k3RPCHTTPDep/1583ab17-f7d1-41c1-ba52-37ec276e3644.mspx

but no joy. We only have a single exchange server here in London so can it
be set up as the front end proxy and back end, co-existing with the proxy
in
Australia?

Appreciate any help on this,
Thanks,
Grant

It's can't be a front end and a back end at the same time.
I would suggest that you configure a fresh server as a front end and
expose it to the Internet.
You're in luck since you already know that the BE is configured
correctly. Simply follow the guidelines and configure the new box in
the same manner as the existing. Should be easy since you have access
to the existing FE.


Back to top
Steven
Guest
Posted: Wed Jan 05, 2005 11:13 pm    Post subject: Re: RPC over HTTP Reply with quote
I think perhaps there might be some confusion here. Do you have the link to
the documentation that states this? Front-end servers have never been able
to be backend servers (or the other way around).

Best regards,
Steven

"Grant" wrote:

Quote:
Thanks for the reply. service pack 1 tightens that up a bit then. The
documentation (pre-sp1) says that you can have the server as both a proxy
and backend.

Cheers,
Grant

"Mark Arnold [MVP]" <mark@mvps.org> wrote in message
news:hjtlt01jro56h5dh14qgijvjmieaad72kc@4ax.com...
On Tue, 4 Jan 2005 14:56:15 -0000, "Grant" <gpsnett@hotmail.com
wrote:

Hello,

Ive got an exchange front end proxy server but would like to set up
another.
The reason is that clients in London get redirected all the way back to
australia and then internally back to the london exchange server again. I
want to set up another proxy in London so that they go straight into the
server here instead of being routed around the globe.

This is using Exchange 2003 SP1. Ive tried this article:
http://www.microsoft.com/technet/prodtechnol/Exchange/guides/E2k3RPCHTTPDep/1583ab17-f7d1-41c1-ba52-37ec276e3644.mspx

but no joy. We only have a single exchange server here in London so can it
be set up as the front end proxy and back end, co-existing with the proxy
in
Australia?

Appreciate any help on this,
Thanks,
Grant

It's can't be a front end and a back end at the same time.
I would suggest that you configure a fresh server as a front end and
expose it to the Internet.
You're in luck since you already know that the BE is configured
correctly. Simply follow the guidelines and configure the new box in
the same manner as the existing. Should be easy since you have access
to the existing FE.


Back to top
Ben Winzenz [Exchange MVP
Guest
Posted: Wed Jan 05, 2005 11:59 pm    Post subject: Re: RPC over HTTP Reply with quote
Well, you can still install the RPC Proxy service on the same server that is
hosting the mailboxes. The RPC Proxy service is simply a Windows 2003
component. It doesn't matter which server it is installed on. Doesn't have
to be a Front end server. I suspect that is what Grant may be referring to.

--
Ben Winzenz
Exchange MVP


"Steven" <Steven@discussions.microsoft.com> wrote in message
news:FD90B09D-55DE-42AD-A4A1-262931D522C4@microsoft.com...
Quote:
I think perhaps there might be some confusion here. Do you have the link
to
the documentation that states this? Front-end servers have never been
able
to be backend servers (or the other way around).

Best regards,
Steven

"Grant" wrote:

Thanks for the reply. service pack 1 tightens that up a bit then. The
documentation (pre-sp1) says that you can have the server as both a proxy
and backend.

Cheers,
Grant

"Mark Arnold [MVP]" <mark@mvps.org> wrote in message
news:hjtlt01jro56h5dh14qgijvjmieaad72kc@4ax.com...
On Tue, 4 Jan 2005 14:56:15 -0000, "Grant" <gpsnett@hotmail.com
wrote:

Hello,

Ive got an exchange front end proxy server but would like to set up
another.
The reason is that clients in London get redirected all the way back to
australia and then internally back to the london exchange server again.
I
want to set up another proxy in London so that they go straight into
the
server here instead of being routed around the globe.

This is using Exchange 2003 SP1. Ive tried this article:
http://www.microsoft.com/technet/prodtechnol/Exchange/guides/E2k3RPCHTTPDep/1583ab17-f7d1-41c1-ba52-37ec276e3644.mspx

but no joy. We only have a single exchange server here in London so can
it
be set up as the front end proxy and back end, co-existing with the
proxy
in
Australia?

Appreciate any help on this,
Thanks,
Grant

It's can't be a front end and a back end at the same time.
I would suggest that you configure a fresh server as a front end and
expose it to the Internet.
You're in luck since you already know that the BE is configured
correctly. Simply follow the guidelines and configure the new box in
the same manner as the existing. Should be easy since you have access
to the existing FE.


Back to top
Ed
Guest
Posted: Thu Jan 06, 2005 12:50 am    Post subject: Re: RPC over HTTP - RpcHttp Troubleshooter v1.0.rtf (0/1) Reply with quote
here is the document

also

Microsoft Security Announcement: Have you installed the patch for
Microsoft Security Bulletin MS03-026? If not Microsoft strongly
advises you to review the information at the following link regarding
Microsoft Security Bulletin MS03-026
http://www.microsoft.com/security/security_bulletins/ms03-026.asp
and/or to visit Windows Update at http://windowsupdate.microsoft.com
to install the patch. Running the SCAN program from the Windows Update
site will help to insure you are current with all security patches,
not just MS03-026.

http://www.microsoft.com/technet/treeview/default.asp?url=/technet/security/tips/pcprotec.asp


Also had to make the following registry changes on the WindowsXP
client

Here is my current registry settings on the working laptop. Notice I
still have the TcpFalBack to force HTTP and I have 3 extra entries. I
forgot the Microsoft article but those three are for when you keep
getting prompted for username and password.


[HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook\RPC]


"EnableRPCtunnelingUI"=dword:00000001

Forgot Article but was a fix if you are kept being asked to enter name
and password

"ConnectTimeout"=dword:000493e0
"ConnectTimeoutLow"=dword:000493e0
"RFRTimeout"=dword:000493e0


Forces TCPIP off

"DisableRpcTcpFallback"=dword:00000001







On Wed, 5 Jan 2005 09:13:05 -0800, Steven
<Steven@discussions.microsoft.com> wrote:

Quote:
I think perhaps there might be some confusion here. Do you have the link to
the documentation that states this? Front-end servers have never been able
to be backend servers (or the other way around).

Best regards,
Steven

"Grant" wrote:

Thanks for the reply. service pack 1 tightens that up a bit then. The
documentation (pre-sp1) says that you can have the server as both a proxy
and backend.

Cheers,
Grant

"Mark Arnold [MVP]" <mark@mvps.org> wrote in message
news:hjtlt01jro56h5dh14qgijvjmieaad72kc@4ax.com...
On Tue, 4 Jan 2005 14:56:15 -0000, "Grant" <gpsnett@hotmail.com
wrote:

Hello,

Ive got an exchange front end proxy server but would like to set up
another.
The reason is that clients in London get redirected all the way back to
australia and then internally back to the london exchange server again. I
want to set up another proxy in London so that they go straight into the
server here instead of being routed around the globe.

This is using Exchange 2003 SP1. Ive tried this article:
http://www.microsoft.com/technet/prodtechnol/Exchange/guides/E2k3RPCHTTPDep/1583ab17-f7d1-41c1-ba52-37ec276e3644.mspx

but no joy. We only have a single exchange server here in London so can it
be set up as the front end proxy and back end, co-existing with the proxy
in
Australia?

Appreciate any help on this,
Thanks,
Grant

It's can't be a front end and a back end at the same time.
I would suggest that you configure a fresh server as a front end and
expose it to the Internet.
You're in luck since you already know that the BE is configured
correctly. Simply follow the guidelines and configure the new box in
the same manner as the existing. Should be easy since you have access
to the existing FE.


Back to top
 
Post new topic   Reply to topic    Exchange Server Forum Index -> Connectivity All times are GMT
Page 1 of 1

 
 You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum




Windows Server Dedicated Servers
New Topics Powered by phpBB