Ok, if you've figured out how to be able to issue ping commands, then the following commands will be of interest: #cp q nic details #cp q lan details ifconfig -a route -n lsmod
Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Doug Carroll Sent: Monday, August 15, 2005 5:17 PM To: [email protected] Subject: Re: Can't Access YAST to complete install Sorry, I'm not seeing post on my topic at all, just checked the archives and saw some replies. for some of the questions, the SLES9 host is on the same subnet as my SLES8 hosts and I can not ping in either direction. SLES8 and SLES8 are both on the same guestlan. i.e. SLES8 can not ping SLES9 host and visa-versa I can not ping the Gateway either from the SLES9 host I can ping the SLES9s own IP from SLES9 the /28 is the correct subnet for the host i have tried re-ipling the SLES9 server and it goes through skipping the customization steps it is still unreachable William 'Doug' Carroll Mainframe Systems Engineer II Global Technology Infrastructure (614) 213-4954 Office (877) 899-1697 Pager (614) 244-9897 Fax http://www.bankone.com ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
