BINGO!! The ARTCPPORT was the answer. A number of weeks ago, I was trying to use SSH Port forwarding through a UNIX box and in order to make it work I had to set the ARTCPPORT to my forwarded port. Naturally it is not a port that is literally referenced anywhere else.
Since I've been working on a terminal server for a number of weeks now, I totally forgot that I had done that. Thanks for your suggestions and help. On Wed, 12 Jul 2006 09:47:13 +0530, Narayanan, Radhika <[EMAIL PROTECTED]> wrote: >We've seen such cases with our users where they had installed an application related to MS Proxy client. When they uninstalled the application, they >were able to connect to remedy. This is probably true with some other memory-resident applications ( may be pcAnywhere too ) which could be listening on ports. And when we attempt to connect to remedy using a named port that's already used by one of the memory-resident applications, we get this error. > >At another instance a user had set up an environment variable for ARTCPPORT to the wrong port no. Hence couldn't connect to remedy servers not using that port no. or registered with portmapper. > >But in both the above cases, the users were able to connect to Remedy by browser, only wasn't able to connect by the windows client tool which ruled out >any other firewall related problems with their gateway or IP or PC. > > >Thanks >Radhika >Direct : +44 20718 20262 >Extn : 20262 > >-----Original Message----- >From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Campbell, Grant I >Sent: 12 July, 2006 12:57 AM >To: arslist@ARSLIST.ORG >Subject: Problems with ARS Client tools - RPC Connection Refused error > > >** >I am having a very strange problem with my Remedy Client tools on my workstation. I have a rather significant number of servers I am normally able to connect to, but recently I cannot connect to any of them. I am receiving the very familiar error message: > >ARERR [90] Cannot establish a network connection to the AR System server : <my server name>(0) : RPC: Miscellaneous tli error - System error (Connection refused) > >Normally this indicates a problem at the server end and I've seen it many times before, however, I am getting this for *every* server I try to connect to. I know this is a specific problem with my workstation because I can connect to these servers from other workstations (through Terminal Server or VNC). Others can connect to these servers. I have exhausted a significant number of troubleshooting steps: (uninstalling/reinstalling...using older and new versions of ARS...cleaning registry entries...even running in "Safe mode"). I'm at the place where I'm going to start uninstalling other software to see if that is the problem. > >I was just wondering if anyone has see this as a "client" problem before. > >~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >Grant Campbell >EDS - Canada Central Application Delivery Unit - Remedy Development Team >Oshawa Shopping Centre : 419 King St. W, Suite 3550 : Oshawa, ON Canada L1J 2K5 >Phone:+1-905-429-3203 : Cell:+1-905-435-7572 : E-mail: [EMAIL PROTECTED] <blocked::blocked::mailto:[EMAIL PROTECTED]> >~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > >__20060125_______________________This posting was submitted with HTML in it___ > > > >This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you. > >__________________________________________________________________________ _____ >UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
