Re: rpc ober http problem

From: robert (anonymous_at_discussions.microsoft.com)
Date: 07/05/04


Date: Mon, 5 Jul 2004 02:33:59 -0700

Evan,

thanks for your answer. I startet a new installation.
Now it seems, that rpc over http is working, don't know
why but it works.
 I can read and write mail messages from my outlook client
when on my firewall only http and https protocols are
enabled(port 80 and 443).

But one strange behavior has remained.

1)If I login as administrator on my XP client then
rpc over http works.
If I login as an normal user than outlook can not connect
to the rpc proxy. The outlook connection status shows
always tcp/ip connections.

I tried to create the initial outlook account (XP client
connected to the Exchange subnet) when I was logged in to
the XP client as an administrator and also as an normal
user.

Any idea what's wrong ??

regards robert

>-----Original Message-----
>Robert -
>
>Your three questions:
>
>> 1)Has someone an idea how to check what this exception
error
>> means.
>
>Error 1706 means: RPC_S_INVALID_ENDPOINT_FORMAT
>My guess is, it's not liking something about your "-e"
parameter, although
>at a glance it looks correct to me.
>
>> 2)Is there a way to check wether the proxy server is
>> running or not. Is this a service??
>
>It's a virtual directory in IIS, so as long as the
hosting IIS web virtual
>server is running, the /rpc directory is running.
>
>> 3) In an older Docu microsoft writes, one should change
>> the HKLM\Software\Microsoft\Rpc\RpcProxy\ValidPorts key
>> to:
>>
exchangeserver:593;exchangeserverFQDN:593;exchangeserver:60
>> 01-6002,exchangeFQDN:6001-6002
>>
etc.....globalcatalogserver:593;globalcatalogserverFQDN:593
>> ...
>>
>> If I do this change, after ca. 15 minutes, the FE-Server
>> changes this key automatically and removes the
>> globalcatalogserver entries and the exchangeserver:593
>> port entries.
>
>Two important things in this question:
>1) You don't need to expose the endpoint mapper (593) any
longer. You also
>don't need to expose the global catalog servers if the
backend servers are
>Exchange 2003 Sp1. In a working E2k3 Sp1 RPC/HTTPS
environment, you should
>see only back-end servers and only ports 6001, 6002, and
6004 listed in this
>reg key.
>
>2) If it's getting overwritten every 15 minutes, that
implies to me that
>you're using the new "managed topology" functionality,
which is great and
>it'll set up the reg-key just like it needs to be -- so
long as the managed
>topology is setup in the proper way (see my blog for more
info:
>http://blogs.msdn.com/evand/archive/2004/06/09/152016.aspx
).
>
>So, if you see the BE servers listed, both netbios name
and FQDN, and ports
>6001, 6002 and 6004... you should be in good shape from
that aspect. You may
>want to confirm that these 3 ports are all listening
(Netstat -a) on the
>backend server you're trying to ping, although I would
expect that to cause
>a "1722" exception rather than a "1706".
>
>--
>Evan Dodds
>Microsoft Exchange Support
>
>****** Disclaimer ******
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>Note: Please do not reply to this e-mail address. It is
used for newsgroup
>purposes only.
>
>
>"robert" <anonymous@discussions.microsoft.com> wrote in
message
>news:244bf01c45f50$ea6386b0$a501280a@phx.gbl...
>> Hello,
>>
>> i've just installed a test environement for rpc over
>> http testing.
>>
>> I istalled:
>> ServerA: W2K3 with Exchange 2003 sp1 as Backend Server
>> ServerB: W2K3 with Exchange 2003 sp1 as Frontend Server
>> ServerC: W2K3 as DC Controller
>> Workstation: with Windows XP and Outlook 2003 with
Hotfix
>> 331320 installed.
>> I configured the servers as is written in the
>> "Exchange Server 2003 RPC over HTTP Deployment
Scenarios"
>> document from June 28 from microsoft.
>>
>> All tree Servers are in the same subnet.
>> The Workstation is on another subnet. A firewall between
>> these subnets has port 80 and 443 open.
>>
>> I made the following tests:
>>
>> 1) From the client WS I can use OWA. So the Exchange FE
>> and BE Servers seems to work.
>> 2) I put the Client into the same subnet as the Exchange
>> servers and configured the outlook client.
>> 3) Then i connected the client in this separat subnet
>> to test rpc over http.
>> 4) As I start outlook, i check the connection status.
>> Outlook tries to connect with tcp/ip instead http, and
>> doesn't find a server.
>>
>> 5) Tried to rpcping the proxy server from the client.
>> as is written in the Knowledge Articel 831051.
>>
>> the command:
>> rpcping -t ncacn_http -s serverA -o RpcProxy=serverB
>> -P "username,domain,*" -H 1 -u 10 -a connect -F 3 -E
>> -R none -v 3
>>
>> works. I can ping my rpc-proxy server.
>>
>> 6) Tried to verify that the client can contact the
backend
>> ports (asis written in the same knowledge articel)
>>
>> the command:
>> rpcping -t ncacn_http -s serverA -o RpcProxy=serverB
>> -P "username,domain,*" -I "username,domain,*" -H 1 -F 3
>> -a connect -u 10 -v 3 -e 6001
>>
>> doesn't work, I get an Exeption 1706 error message.
>> No idea what this means?????????????
>>
>> Questions:
>> 1)Has someone an idea how to check what this exeption
error
>> means.
>>
>> 2)Is there a way to check wether the proxy server is
>> running or not. Is this a service??
>>
>> 3) In an older Docu microsoft writes, one should change
>> the HKLM\Software\Microsoft\Rpc\RpcProxy\ValidPorts key
>> to:
>>
exchangeserver:593;exchangeserverFQDN:593;exchangeserver:60
>> 01-6002,exchangeFQDN:6001-6002
>>
etc.....globalcatalogserver:593;globalcatalogserverFQDN:593
>> ...
>>
>> If I do this change, after ca. 15 minutes, the FE-Server
>> changes this key automatically and removes the
>> globalcatalogserver entries and the exchangeserver:593
>> port entries.
>>
>>
>> regards robert
>>
>>
>>
>>
>
>
>.
>



Relevant Pages

  • [UNIX] Alteon ACEdirector Signature/Security Bug
    ... A new security bug has been discovered in the Nortel Alteon ACEdirector ... HTTP clients could exploit it to determine the IP addresses of ostensibly ... "hidden" web servers that are load-balanced by the ACEdirector. ... uses it to persistently map a series of HTTP client requests to the same ...
    (Securiteam)
  • Alteon ACEdirector signature/security bug
    ... This is to inform you of a bug in the Nortel Alteon ACEdirector ... balance incoming HTTP requests made to one virtual IP address ... amongst the real IP addresses of multiple HTTP servers. ... series of HTTP client requests to the the same one of the real HTTP ...
    (Bugtraq)
  • Re: Two Questions abt RPC over HTTP
    ... running basic) in the client connection settings. ... Didn't catch your scenario completly but RPC over HTTP is configured on ... MAPI profile basis. ...
    (microsoft.public.exchange.admin)
  • RE: RPC/HTTPS GC question
    ... RPC over HTTP Interactions on the Back-End Servers: ... The Microsoft Exchange Information Store service listens for incoming ...
    (microsoft.public.exchange.admin)
  • Re: Pitfalls with RPC over HTTP(S)
    ... SBS Rocks!!! ... I noticed on another thread that once you enable a client ... > for RPC over HTTP, the client will use that for all communication to the ...
    (microsoft.public.exchange.connectivity)