Re: RPC over HTTP from termina server



Thanks for that - that saves me beating head looking for a solution.

I have a number of reasons to use RPC over HTTP from 2003. I have a number
of clients who run SBS 2000 servers. They have subsequently installed 2003
box - moving from Windows 98 on the desktop to thin client/terminal server
and also providing remote access). This has provided huge benefits.

These clients are now wanting to upgrade the SBS 2000 boxes specifically
Exchange server. We see huge benefits in hosting Exchange on an application
server.

Apart from the cost, ongoing management and disruption - what is the point
in upgrading to SBS 2003 - when Exchange 2007 is in the starting blocks?
There is a continual need to upgrade (and appears to be speeding up) - we are
all suffering from upgrade-itus.

Clients have a very real upgrade option - hosting their appilications and
letting a professional IT infra structure company handle upgrade issues, gain
cost benefits in sharing infrasctructure with other companies.

The upgrade path is quite clear. Run 2003 server in house running existing
applications. Most clients are thin client/Terminal server and those in the
organistion who need remote access run Win XP. Move all
mail/exchange/sharepoint/collaboration to a hosted service and use Web
Outlook (and for those running XP RPC over HTTP) - making the SBS 2000 box
redundent.

To have had RPC over HTTP working from 2003 would have been a complete
solution - thin clients would have used the full Outlook client from the 2003
box.

Your comments would be much appreciated - is there a better topology I can
employ?

"Mark Arnold [MVP]" wrote:

On Mon, 10 Jul 2006 21:59:01 -0700, KiwiJohn
<KiwiJohn@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

I have setup Exchange 2003 (on a single server) and accessing mailboxes from
Windows XP client run Outlook 2003 using RPC over HTTP. Works perfectly nice
elegant solution.

However I can't access this same server from a Terminal Server 2003 running
Outlook 2003.

I appreciate that RPC over HTTP requisite is Windows XP (with applied patch)
and it is implied that Windows Server 2003 is not supported - can someone
confirm this - or give a hint as to how I can achieve this (Access Exchange
2003 mailbox from a Terminal Server 2003 with Outlook 2003 via RPC over
HTTP).......

Thanks for any help.




It's not supported, I have never got RPC over HTTPS working from a
2003 box (although it's been a long, long time since I tried so I
can't remember what I fisked about with to try)

Seems to be a pointless idea though..... If you're using Terminal
Services the whole concept is to put the TS near the data (Exchange
server) so why would you want to use RPC over HTTPS to reach it? If
your TS is a long way from the data you might as well use a normal
workstation because it uses no more or less bandwidth.

I've answered your question but I always like to know what you were
trying to achieve when the question doesn't make sense in my own head
(see above).

.



Relevant Pages

  • RE: Outlook RPC over HTTp deosnt work
    ... try to use RPC over HTTP to connect the Exchange Server. ... What SBS is running on the problematic Server? ...
    (microsoft.public.windows.server.sbs)
  • Re: RPC over HTTP Question
    ... allow specific traffic transfer and publish some web services to internet. ... On the Web Server Certificate page, ... The wizard automatically configures Exchange, IIS, and the RPC proxy ... >Subject: Re: RPC over HTTP Question ...
    (microsoft.public.windows.server.sbs)
  • RE: RPC over HTTP
    ... NTLM and Basic Authentication for RPC over HTTP: ... TCP port to connect Exchange server by Outlook, it is easy to go through ...
    (microsoft.public.windows.server.sbs)
  • RE: Outlook RPC over HTTp deosnt work
    ... RPC over HHTP) when I try it I get the .NET password prompt screen! ... > when you try to use RPC over HTTP to connect the Exchange Server. ... we don't have to manually configure RPC over HTTP. ... On the SBS server, verify if it trusts the certificate: ...
    (microsoft.public.windows.server.sbs)
  • RE: RPC over HTTP troubleshooting
    ... When we connect to the server through RPC over HTTPS, ... HTTP Error 401.3 - Unauthorized: Access is denied due to an ACL set on the ... 833401 How to configure RPC over HTTP on a single server in Exchange Server ...
    (microsoft.public.exchange.connectivity)