RE: RPCPING Utility and Exception 1722

  • From: "Lara, Greg" <GLara@xxxxxxx>
  • To: "'[ExchangeList]'" <exchangelist@xxxxxxxxxxxxx>
  • Date: Tue, 28 Sep 2004 10:32:03 -0400

I noticed a couple of things. You don't need MX records in your internal DNS
database. You do need to publish MX records for external DNS however, if you
want this domain to receive mail from the outside. Also, your first rpcping
example shows, yet you don't have listed for your internal DNS, so double check that
if it wasn't typo on your part.

I suggest reading the following Microsoft KB article, if you haven't
already. It has a section that discusses this error response.;en-us;831051

Greg Lara

This e-mail message may contain privileged, confidential and/or proprietary
information intended only for the person(s) named. If you are not the
intended recipient, please destroy this message, and any attachments, and
notify the sender by return e-mail. If you are not the intended
recipient(s), or the employee or agent responsible for delivering the
message to the intended recipient(s), you are hereby notified that any
dissemination, disclosure or copying of this communication is strictly

-----Original Message-----
From: Mustafa Cicek [mailto:mbcicek@xxxxxxxxx] 
Sent: Tuesday, September 28, 2004 11:11 AM
To: [ExchangeList]
Subject: [exchangelist] RPCPING Utility and Exception 1722


First of all I have a criticism to MS EXCHANGE newsgroup experts:
Why do you cancel the problem, although the problem still exists? You give
no feedback more, if the problem complicated!!!

I hope you give a tip for the following situation:

I user RPCPING tool to diagnose the problem. I used it in internal
network. If I use as Exchange Server my back-end Exchange named, then RPCPING for all -e 6001, 6002 and 6004
successful. Here is it:
rpcping -t ncacn_http -s -o -P "administrator,EXCHTEST,*" -I
"administrator,exchtest,*" -H 1 -u 10 -a connect -F 3 -v 3 -e 6001

RPCPing v2.12. Copyright (C) Microsoft Corporation, 2002
OS Version is: 5.2
Completed 1 calls in 218 ms
4 T/S or 218.000 ms/T

But if I use as Exchange Server in this utility, I
have the following error for all 6001,6002 and 6004:

rpcping -t ncacn_http -s -o -P "administrator,EXCHTEST,*1" -I
"administrator,exchtest,*" -H 1 -u 10 -a connect  -F 3 -v 3 -e 6001

RPCPing v2.12. Copyright (C) Microsoft Corporation, 2002
OS Version is: 5.1, Service Pack 2

Exception 1722 (0x000006BA)

You know, I don't want to publish my back-end Exchange Server in Internet.
That is also not recomended RPC over HTTP in an FE/BE einvironment.

I think the problem is DNS name resolution. Or not? I list my DNS
configuration below and want to also a solution tip:

In external DNS:

On ISA Server:
External address of ISA:
Internal address of ISA:

HOSTS file include on ISA:

NAT mapping on Netscreen Firewall 2:
NAT address for front-end exchange:

In internal DNS:
A record: (Front-End)
A record: (Back-End)
A record: (Global Catalog)
A record for
A record:
first MX record: points to
second MX record: points to

Best Regards

Other related posts: