I was not suscribed to arslist, I´ve been registered and I hope anyone can see my post now.
Thanks a lot. Enrique Palazuelos wrote: > > Hello, > > This is my first post, please excuse my terrible english. > > We have an ars server and a midtier server connected to. The ars server is > configured to use only the artcpport 1234 (for example). In preproduction > environment Midtier works ok when editing reports. It only open > connections on 1234 TCP Port, but in production environment Midtier tries > to open an udp port via Sun RPC and gets an RPC timeout, which is normal > because these ports are closed. The ar.conf files are similar. > TCD-Specific-Port is configured to 1234 and works ok, but the Midtier > production Server tries to open a different port only when we try to edit > a report. We have set the parameter "Register-With-Portmapper: T" in both > files, but in preproduction server, these parameter is under the > TCD-Specific-Port. In the ars production server TCD-Specific-Port > parameter is under "Register-With-Portmapper: T". > > The order of parameters in the ar.conf is important? Which are the > necessary parameters to use only tcp ports? We have a 6.3 Midtier Server > patch 14 and a 5.1.2 Ars Server. > > We have open a ticket to BMC. They have purposed to a open a pluginreport > port, but we can´t open ports without explaining why, and these port is > not configured on preproduction environment and it works ok. We can´t > upgrade because development requirements, > > Any suggestion? > > Thanks a lot. > -- View this message in context: http://www.nabble.com/Midtier-using-RPC-but-ars-is-not-configured-to-tf3757780.html#a10676829 Sent from the ARS (Action Request System) mailing list archive at Nabble.com. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
