RE: Please check your communications path to the AS/400

[Bill.Steadman@xxxxxxxxxxxxx]

I ran a verify connection on a V4R4 machine and the one difference I have
from your  response is:

Successfully connected to server application: Network File

The only way I could stop receiving this comment was to stop the AS/400
NetServer.  So, is your NetServer running?
Bill


On 13 Dec 2000, at 15:18, Eric Sundell PMI wrote:
> Try reconfiguring the connection in 'My AS400 Connections' and do a
> 'Verify' or CWBPING, perhaps one or more of the CA servers are not
> up...
Thanks for the suggestions.  I disconnected the connection in OpsNav and
ran Verify.  It said Verify completed Successfully.  I ran CWBPING and the
results are:
Microsoft wsock32.dll, ver2.2, 32bit of Apr 22 1999, at 20:29:32.
Address 192.168.1.1 used to connect to system .
Successfully connected to AS/400 server mapper
Successfully connected to server application telnet
Successfully connected to server application as-netprt
Successfully connected to server application as-database
Successfully connected to server application as-rmtcmd
Successfully connected to server application as-dtaq
Successfully connected to server application as-file
Successfully connected to server application as-central
Successfully connected to server application as-signon
Connection verified

In WRKACTJOB it shows:
QSERVER              QSYS             SBS
   QPWFSERVSD          QUSER            BCH
   QSERVER             QPGMR            ASJ
   QZDASRVSD           QUSER            BCH
   QZLSFILE            QUSER            PJ
   QZLSSERVER          QPGMR            BCH

<big snip>



+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---