You probably need to review the BMC documents about plugins behind a VIP 
or firewall without a portmapper.  "Using a Hardware Load Balancer with 
BMC Remedy Action Request System 7.0" page 9, and others that I can't find 
at the moment.

Here's an example of some lines from one of our ar.conf's (this one from a 
server group, but relevant since we don't use portmapper either)

Plugin-Port: 9000
Register-With-Portmapper: F
TCD-Specific-Port: 8639
Server-Plugin-Alias: ARSYS.ARDBC.CONFIGFILE ARSYS.ARDBC.CONFIGFILE 
ksms562:9000
Server-Plugin-Alias: ARSYS.ARDBC.LDAP ARSYS.ARDBC.LDAP ksms562:9000
Server-Plugin-Alias: ARSYS.ARDBC.PREVIEW ARSYS.ARDBC.PREVIEW ksms562:9000
Server-Plugin-Alias: ARSYS.AREA.LDAP ARSYS.AREA.LDAP ksms562:9000
Server-Plugin-Alias: ARSYS.ARF.WEBSERVICE ARSYS.ARF.WEBSERVICE 
ksms562:9000
Server-Plugin-Alias: BMC.ARF.CMDBCONSOLE BMC.ARF.CMDBCONSOLE ksms562:9000
Server-Plugin-Alias: REMEDY.ARDBC.APPQUERY REMEDY.ARDBC.APPQUERY 
ksms562:9000
Server-Plugin-Alias: REMEDY.ARDBC.FLASHBOARD.FORM 
REMEDY.ARDBC.FLASHBOARD.FORM ksms562:9000
Server-Plugin-Alias: REMEDY.ARDBC.SERVER.ADMINISTRATION 
REMEDY.ARDBC.SERVER.ADMINISTRATION ksms562:9000
Server-Plugin-Alias: REMEDY.ARF.CAI REMEDY.ARF.CAI ksms562:9000
Server-Plugin-Alias: REMEDY.ARF.CBDATA REMEDY.ARF.CBDATA ksms562:9000
Server-Plugin-Alias: REMEDY.ARF.OMFOBJIE REMEDY.ARF.OMFOBJIE ksms562:9000
Server-Plugin-Alias: REMEDY.ARF.SLASETUP REMEDY.ARF.SLASETUP ksms562:9000

You may not need the alias lines, but you certainly need the Plugin-Port.

hth,
tony

-- 
Tony Worthington
[EMAIL PROTECTED]
262-703-5911



Mike Chepaykin <[EMAIL PROTECTED]> 
Sent by: "Action Request System discussion list(ARSList)" 
<[email protected]>
08/06/2007 10:12 AM
Please respond to
[email protected]


To
[email protected]
cc

Subject
RPC: Unable to receive






Hello listers.

ARERR [8760] Cannot establish a network connection to the AR System 
Plug-In server : bmcstage : RPC: Rpcbind failure - RPC: Unable to receive

This is what I got in RUT when I move my ARS server behind the firewall, 
uncheck "Register with portmapper", assign static TCP port and shutdown 
remedy portmapper service. And restart my windows box of course - a shut 
in a head 8).

This error appears only in Problem Management Console on window open. 
Other consoles - incident, asset, cmdb - 
appear without any errors.

No errors in arerror, armonitor, arplugin logs and no errors on client 
side logs too.

When I change environment back (no firewall restrictions at all) and move 
to portmapper - everything is fine again.

Why (and which?) plugin try to register himself in portmapper? Or maybe 
the cause is something else?

windows2003, mssql2000, ars7.0.1p2, ITSM 7.0.2

-- 
Mike Chepaykin

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where 
the Answers Are"



CONFIDENTIALITY NOTICE: 
This is a transmission from Kohl's Department Stores, Inc.
and may contain information which is confidential and proprietary.
If you are not the addressee, any disclosure, copying or distribution or use of 
the contents of this message is expressly prohibited.
If you have received this transmission in error, please destroy it and notify 
us immediately at 262-703-7000.

CAUTION:
Internet and e-mail communications are Kohl's property and Kohl's reserves the 
right to retrieve and read any message created, sent and received.  Kohl's 
reserves the right to monitor messages to or from authorized Kohl's Associates 
at any time
without any further consent.

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the 
Answers Are"

Reply via email to