× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: TCP/IP & CAw95 configuration troubles
  • From: "Guillermo Andrades [CPI]" <gab@xxxxxxxxxxxxxxx>
  • Date: Thu, 11 Dec 1997 12:37:24 +0100

John,

No, the AS/400 and the PC's are in the same hub, in the same office.

HUB-.-.-.-.-.-.---.   
              |   |
              |   |
              |   AS400 Ethernet 2617
              |
              each PC in one hub connection 

All works ok when using CAw95 with NetSoft 802 (MS-DLC-32)
Also works some connecction with MS SNA Router installed in an NT
Server connected to the same hub.

In the AS/400 the PING to the proper AS/400 works ok. thus:
        ping cpi1.dominio400.cpi.com   ---> OK
        ping '201.0.0.1'  ----> OK

But ping from AS/400 to PC does'nt work:
        ping '201.0.0.11' nor .111 
        ping pc06.dominio400.cpi.com nor pc11

But ping between PCs yes it works using numbers and using names.

local domain name       DOMINIO400.CPI.COM
System Name             CPI1 (same as neta)

then, the main system table (step 10):
                                                  
      127.0.0.1        LOOPBACK                   
                       LOCALHOST                  
      201.0.0.1        CPI1.DOMINIO400.CPI.COM    
                       CPI1                       
      201.0.0.11       PC06                       
                       PC06.DOMINIO400.CPI.COM    
      201.0.0.111      PC11.dominio400.cpi.com    
                       PC11                       
                                                  
Please if any other help?

Thanks                                             
        


> From: John Cirocco <jcirocco@us.ibm.com>
> To: MIDRANGE-L@midrange.com
> Subject: Re: TCP/IP & CAw95 configuration troubles
> Date: 10 de diciembre de 1997 19:11
> 
> 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.
> 
> Hope this helps,
> John W. Cirocco

+---
| 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 thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.