Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*ANR2716E\s+Schedule\s+prompter\s+was\s+not\s+able\s+to\s+contact\s+client\.\.\.W\s+HY\?\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*ANR2716E\s+Schedule\s+prompter\s+was\s+not\s+able\s+to\s+contact\s+client\.\.\.W\s+HY\?\s*$/: 3 ]

Total 3 documents matching your query.

1. Re: ANR2716E Schedule prompter was not able to contact client...W HY? (score: 1): Author: "Garrison, Tony" <Anthony.Garrison AT USAA DOT COM>; Date: Mon, 8 Jul 2002 14:25:49 -0500; I have had this problem with several servers. I solved the problem on several by utilizing the IP address in the dsm.opt as the TCPCLIENTADDRESS instead of the node name. Tony Garrison I/T Sr. System; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-07/msg00215.html (10,924 bytes)
2. Re: ANR2716E Schedule prompter was not able to contact client...W HY? (score: 1): Author: Greg Garrison <gagarris AT US.IBM DOT COM>; Date: Mon, 8 Jul 2002 15:15:06 -0700; I agree on adding the actual IP address for the TCPCLIENTADDRESS option. This is necessary in machines with more than one network card as well. I usually query the activity log and search for the nod; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-07/msg00224.html (12,266 bytes)
3. Re: ANR2716E Schedule prompter was not able to contact client...W HY? (score: 1): Author: Zlatko Krastev/ACIT <acit AT ATTGLOBAL DOT NET>; Date: Wed, 10 Jul 2002 04:30:20 +0300; Ports 1500 and 1501 do *not* need to be bi-directional. Connection on port 1500 is always initiated from the node to the server. Connection on port 1501 is always from the server to the node. Just fi; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-07/msg00286.html (12,789 bytes)

Current List: 1 - 3
Page: [1]