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 <remedy_server_name> <port number> On Thu, May 28, 2009 at 12:59 PM, Sean Harrodine <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 ARSlist: "Where the Answers > Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"
