|
Guillermo, At 01:11 PM 12/10/97 -0500, John W. Cirocco wrote: >Guillermo, > >By chance is your /400 on a different ring or segment? > >If it is, you need to specify a default route if you have not done so. See >Work with TCP/IP routes on CFGTCP menu option 1. > >If it is not, have you tried to ping yourself (stop the giggling folks)? You >should have an entry for *loopback with IP of 127.0.0.1 on the Work with TCP/IP >interfaces. Try pinging from the /400 command line to the IP address of the >/400. If for some reason your TCP/IP did not start up properly, this part >would fail. You should also try to ping the interface addresses you have set up. Also, be sure you lines/controllers are varied on. Cheers Vernon Hamberg Systems Software Programmer Old Republic National Title Insurance Company 400 Second Avenue South Minneapolis, MN 55401 (612) 371-1111 x480 +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@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 +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
