Hi, Balaji: I didn't experience RPC Bind failures on 6.3, but we did on ARWeb 4.0. However, UDP port 111 (Sun RPC) remained open when we upgraded to 6.3.
I do know that in ARWeb 4.0, we (at another worksite) had to open traffic between the ARWeb server in the DMZ and the ARS server on the internal network on a TCP port we designated AND UDP 111. Our security god was not happy with it. We had to set up an exercise where he watched the traffic from the web server to the ARS server. I could prove it every time I opened a search(query) menu. The result was that he unblocked the port from the ARWeb to ARS server. Since we upgraded those same servers from 5.1.2 and then finally to 6.3, we never closed the UDP 111 port. So, it is hard to say whether or not it is still needed. To my knowledge, we never received the RPC bind errors after he opened the port. That old environment was: Remedy ARS 4.5.1 upgraded to Remedy ARS 5.1.2 and then to 6.3 patch 5 Win2K/SQL Server 2000 ARWeb 4.0 upgraded to Remedy Mid-Tier 5.1.2 and then to 6.3 patch 5 Win2K/IIS 5.0 Servlet exec 5.0 patch 6 Michelle -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Carey Matthew Black Sent: Monday, April 24, 2006 1:29 PM To: [email protected] Subject: Re: RPC bind failure error Balaji, For a long time in the v5.1.2 Mid-Tier it simply ignored the configured TCP port. Sounds like they might have "reintroduced" that kind of a bug in to some portion of that Mid-tier version/client. Since the behaviour is transient it will likely be harder for Remedy to find. Please work with Techsupport to try to pin point the code that is not following the rules on this one. (also as a minor note.... Mid-Tier v6.3 patch 16 is out there too.) -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. Never ascribe to malice, that which can be explained by incompetence. On 4/24/06, Balaji Chandrashekar <[EMAIL PROTECTED]> wrote: > Sorry, forgot to provide the environment details: > > ARS 6.3 (patch 16) > Oracle 9.1.6 > Solaris 9 > mid-tier 6.3 (patch 15) > > And a small correction: RPC 111 is blocked on the firewall (and > not on the server as mentioned earlier) > > Regards, > Balaji > > ------------------------------------------------------------------------ -------- > From: Balaji Chandrashekar [mailto:[EMAIL PROTECTED] > Sent: Mon 4/24/2006 11:20 PM > To: [email protected] > Subject: RPC bind failure error > > > I am having a strange problem with ARS and Mid-tier. > > There is a firewall between ARS and mid-tier and once in a while > the mid-tier throws an "RPC bind failure" error and looses > connectivity with the server. After 20-25 minutes, the > connection > resumes automatically on its own. During this time, end users > are > not able to access the server. This happens atleast twice in a > day! > > ARS is configured for a specific port and the mid-tier server > has > this configured in the serverlist (TCP port specified). > > We checked the firewall logs and found that once in a while the > mid-tier is trying to reach the server on RPC port 111, which is > blocked on the server. Only the TCP specific port is allowed. > But, no idea how the connection is resumed again. > > Stange thing is, it works perfectly fine in this setup and once > in > a while looses connectivity in this way. > > In case any one has faced a similar problem or any help in this > regard is appreciated. > > Many Thanks, > Balaji ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
