Re: Remedy port query - ARERR 90
Sean, If the port is not defined in the desktop client, the client makes a UDP call to port mapper to determine which TCP port the client needs to use. In most instances UDP is blocked on the firewall rules. Defining the port in the client settings under account eliminates the UDP call. So even if port 4445 is open on the firewall, unless it is defined in the client the person may not connect because UDP is blocked. Dave From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Sean Harrodine Sent: Thursday, May 28, 2009 6:44 AM To: arslist@ARSLIST.ORG Subject: Re: Remedy port query - ARERR 90 ** thanks for the clarification Frank - i thought thats what it was. i will ask our network guys to see if they can see if the traffic is being blocked. Sean From: Frank Caruso To: arslist@ARSLIST.ORG Sent: Thursday, 28 May, 2009 11:22:03 Subject: Re: Remedy port query - ARERR 90 ** Have the user try putting in the port number 4445 in there user tool connection and see if they can connect. If they still cannot connect then you need to punch a whole in the firewall. They could also try using telnet against your Remedy server. They should be able to to try something like: telnet On Thu, May 28, 2009 at 12:59 PM, Sean Harrodine mailto:sean_rem...@yahoo.co.uk>> wrote: ** Hi all, Can anyone confirm the following for me please. We have a remote customer who needs access to our Remedy server. All network connectivity we are being told is in place but he is still receiving an ARERR 90 Now, looking in the "Admin Tool", the "Server TCP/IP Port" is showing as being 4445. Can anyone confirm please if the remote customer will need to specify this specific port against the server name in his Remedy User tool, and basically, is 4445 the true port that needs to be opened up on the firewalls as i suspect it maybe be a firewall blocking the traffic as the server is running fine. TIA Sean _Platinum Sponsor: rmisoluti...@verizon.net<mailto:rmisoluti...@verizon.net> ARSlist: "Where the Answers Are"_ _Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the Answers Are"_ _Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the Answers Are"_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"
Re: Remedy port query - ARERR 90
thanks for the clarification Frank - i thought thats what it was. i will ask our network guys to see if they can see if the traffic is being blocked. Sean From: Frank Caruso To: arslist@ARSLIST.ORG Sent: Thursday, 28 May, 2009 11:22:03 Subject: Re: Remedy port query - ARERR 90 ** Have the user try putting in the port number 4445 in there user tool connection and see if they can connect. If they still cannot connect then you need to punch a whole in the firewall. They could also try using telnet against your Remedy server. They should be able to to try something like: telnet On Thu, May 28, 2009 at 12:59 PM, Sean Harrodine wrote: ** Hi all, Can anyone confirm the following for me please. We have a remote customer who needs access to our Remedy server. All network connectivity we are being told is in place but he is still receiving an ARERR 90 Now, looking in the "Admin Tool", the "Server TCP/IP Port" is showing as being 4445. Can anyone confirm please if the remote customer will need to specify this specific port against the server name in his Remedy User tool, and basically, is 4445 the true port that needs to be opened up on the firewalls as i suspect it maybe be a firewall blocking the traffic as the server is running fine. TIA Sean _Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the Answers Are"_ _Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the Answers Are"_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"
Re: Remedy port query - ARERR 90
Have the user try putting in the port number 4445 in there user tool connection and see if they can connect. If they still cannot connect then you need to punch a whole in the firewall. They could also try using telnet against your Remedy server. They should be able to to try something like: telnet On Thu, May 28, 2009 at 12:59 PM, Sean Harrodine wrote: > ** Hi all, > > Can anyone confirm the following for me please. > > We have a remote customer who needs access to our Remedy server. > All network connectivity we are being told is in place but he is still > receiving an ARERR 90 > > Now, looking in the "Admin Tool", the "Server TCP/IP Port" is showing as > being 4445. > > Can anyone confirm please if the remote customer will need to specify this > specific port against the server name in his Remedy User tool, and > basically, is 4445 the true port that needs to be opened up on the firewalls > as i suspect it maybe be a firewall blocking the traffic as the server is > running fine. > > TIA > > Sean > > _Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the Answers > Are"_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"
Remedy port query - ARERR 90
Hi all, Can anyone confirm the following for me please. We have a remote customer who needs access to our Remedy server. All network connectivity we are being told is in place but he is still receiving an ARERR 90 Now, looking in the "Admin Tool", the "Server TCP/IP Port" is showing as being 4445. Can anyone confirm please if the remote customer will need to specify this specific port against the server name in his Remedy User tool, and basically, is 4445 the true port that needs to be opened up on the firewalls as i suspect it maybe be a firewall blocking the traffic as the server is running fine. TIA Sean ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"
