On Tuesday, 11/29/2005 at 07:48 EST, Steve Gentry
<[EMAIL PROTECTED]> wrote:
> What I had originally sent in the original post was the OBEYFILE file,
so
> of course you all wouldn't know that I had the above.
> Based on what Alan said, I need to change (in the GATEWAY section)
> 192.168.141.63 to
lly dig
myself a deeper hole. Very frustrating.
Steve G.
There's no place like 127.0.0.1
Alan Altmark <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port
11/28/2005 08:02 PM
Please respond to Linux on 390 Port
To: LINUX-390@VM.MARIST.EDU
cc:
Subject:Re: Lin
On Monday, 11/28/2005 at 06:41 EST, "Post, Mark K" <[EMAIL PROTECTED]>
wrote:
> Well, then maybe I should point out that the two IP addresses are indeed
> different, in the third octet:
> 192.168.140.60 HIPERLF0
> 192.168.141.60 HIPERLF1
>
> If the intent was to actually assign the same IP to both
mailing
list.
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Alan Altmark
Sent: Monday, November 28, 2005 6:02 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Linux network problem/question
-snip-
With the subsequent post from Steve saying that he
On Monday, 11/28/2005 at 05:23 EST, "Post, Mark K" <[EMAIL PROTECTED]>
wrote:
> If the OSA is using 10.140.1.22 as its IP address, why would it be doing
> anything to block traffic that would be going from 192.168.141.60 to
> 192.168.141.63? I can understand that not having PRIROUTER specified
>
something that would be originating from, say CMS USER to LNXRH03.
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Alan Altmark
Sent: Monday, November 28, 2005 1:42 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Linux network problem/question
> I am not able to ping from .60 to .63
Ah. That's a new piece of information. In that case, it's probably the
PRIROUTER setting, as Alan mentioned.
--
For LINUX-390 subscribe / signoff / archive access instructions
On Monday, 11/28/2005 at 12:01 EST, Steve Gentry
<[EMAIL PROTECTED]> wrote:
> Greetings. I'm trying to get from my pc, which is on a different
subnet, to a
> linux guest in an IFL via a hiper socket. I'm not having much luck. So
I
> wonder if someone could help me. When I ping 192.168.141.63, I
n 390 Port [mailto:[EMAIL PROTECTED] On
Behalf Of Steve Gentry
Sent: Monday, November 28, 2005 12:16 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Linux network problem/question
Greetings. I'm trying to get from my pc, which is on a
different subnet, t
Cahnge yur GATEWAY entry from
192.168.141.60 = HIPERLF1 8192
HOST
to
192.168.141.63 = HIPERLF1
8192 HOST
Bill Dodge
email: [EMAIL PROTECTED]
Phone: (703)627-2455
"If you d
28/2005 12:13 PM
Please respond to Linux on 390 Port
To: LINUX-390@VM.MARIST.EDU
cc:
Subject: Re: Linux network problem/question
Your PC needs to be told, via a ROUTE command (or equivalent) that all
access to the 192.168.141.0/24 network mu
05 11:02 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Linux network problem/question
Greetings. I'm trying to get from my pc, which is on a
different subnet, to a linux guest in an IFL via a hiper socket. I'm
not having much luck. So I wonder if som
Greetings. I'm trying to get from my pc, which is on a different subnet, to a linux guest in an IFL via a hiper socket. I'm not having much luck. So I wonder if someone could help me. When I ping 192.168.141.63, I get a Request Timeout. I can ping 192.168.141.60 from my pc and get a reply. T
13 matches
Mail list logo
