tcp/ip interface has failed status. Cant ping ip address. - IBM AS400
This is a discussion on tcp/ip interface has failed status. Cant ping ip address. - IBM AS400 ; the tcp/ip interface to my router has a failed status:
Work with TCP/IP Interfaces
Type options, press Enter.
1=Add 2=Change 4=Remove 5=Display 9=Start 10
Internet Subnet Interface
Opt Address Mask Status
10.10.10.1 255.255.255.0 Failed
When I try to ping an ...
-
tcp/ip interface has failed status. Cant ping ip address.
the tcp/ip interface to my router has a failed status:
Work with TCP/IP Interfaces
Type options, press Enter.
1=Add 2=Change 4=Remove 5=Display 9=Start 10
Internet Subnet Interface
Opt Address Mask Status
10.10.10.1 255.255.255.0 Failed
When I try to ping an IP address I get a "cant reach remote system "
error:
ping '4.2.2.1'
Verifying connection to host system 4.2.2.1.
Cannot reach remote system
Using WRKCFGSTS *LIN shows my lan line description to be active.
I have ended and started the interface and the status quickly changes
from active to failed. No messages in the QSYSOPR message queue. also
none in the QTCP job that I see when I WRKCFGSTS *LIN.
Any ideas why the interface to the router fails and I cant ping the
internet? My LAN works to the extent my PC can connect to my 400. and
my PC can ping the 4.2.2.1 address.
thanks,
-Steve
-
Re: tcp/ip interface has failed status. Cant ping ip address.
Steve Richter wrote:
> the tcp/ip interface to my router has a failed status:
> Work with TCP/IP Interfaces
>
> Type options, press Enter.
> 1=Add 2=Change 4=Remove 5=Display 9=Start 10
>
> Internet Subnet Interface
> Opt Address Mask Status
>
> 10.10.10.1 255.255.255.0 Failed
>
> When I try to ping an IP address I get a "cant reach remote system "
> error:
> ping '4.2.2.1'
> Verifying connection to host system 4.2.2.1.
> Cannot reach remote system
What routes are defined?
Tom Liotta
http://zap.to/tl400
-
Re: tcp/ip interface has failed status. Cant ping ip address.
Tom Liotta wrote:
> Steve Richter wrote:
>
> > the tcp/ip interface to my router has a failed status:
> > Work with TCP/IP Interfaces
> >
> > Type options, press Enter.
> > 1=Add 2=Change 4=Remove 5=Display 9=Start 10
> >
> > Internet Subnet Interface
> > Opt Address Mask Status
> >
> > 10.10.10.1 255.255.255.0 Failed
> >
> > When I try to ping an IP address I get a "cant reach remote system "
> > error:
> > ping '4.2.2.1'
> > Verifying connection to host system 4.2.2.1.
> > Cannot reach remote system
>
>
> What routes are defined?
only one route. *DFTROUTE with next hop set to the IP of my router:
Work with TCP/IP Routes
System
Type options, press Enter.
1=Add 2=Change 4=Remove 5=Display
Route Subnet Next Preferred
Opt Destination Mask Hop Interface
*DFTROUTE *NONE 10.10.10.1 *NONE
>
>
> Tom Liotta
>
> http://zap.to/tl400
-
Re: tcp/ip interface has failed status. Cant ping ip address.
I had this happen once on a model 170. I wound up swapping out the
network card. I would suggest first re-seating the network card.
-
Re: tcp/ip interface has failed status. Cant ping ip address.
Steve Richter schreef:
> Tom Liotta wrote:
>> Steve Richter wrote:
>>
>>> the tcp/ip interface to my router has a failed status:
>>> Work with TCP/IP Interfaces
>>>
>>> Type options, press Enter.
>>> 1=Add 2=Change 4=Remove 5=Display 9=Start 10
>>>
>>> Internet Subnet Interface
>>> Opt Address Mask Status
>>>
>>> 10.10.10.1 255.255.255.0 Failed
>>>
>>> When I try to ping an IP address I get a "cant reach remote system "
>>> error:
>>> ping '4.2.2.1'
>>> Verifying connection to host system 4.2.2.1.
>>> Cannot reach remote system
>>
>> What routes are defined?
>
> only one route. *DFTROUTE with next hop set to the IP of my router:
>
> Work with TCP/IP Routes
> System
> Type options, press Enter.
> 1=Add 2=Change 4=Remove 5=Display
>
> Route Subnet Next Preferred
> Opt Destination Mask Hop Interface
>
> *DFTROUTE *NONE 10.10.10.1 *NONE
>
>
>
>
>
>>
>> Tom Liotta
>>
>> http://zap.to/tl400
>
If I read this correctly you have a router with IP address 10.10.10.1.
You defined your AS/400 IP address to be the same address. You cannot
have two identical addresses on the same LAN, so when you start your
interface, it sees the address is already active and fails (power down
the router before you activate your interface and you'll see that the
interface stays active).
The interface address you assign is the address of the AS/400 network
card, so it has to have a unique address. Try assigning it address
10.10.10.2 (if nothing else it using that) and you'll see it will work.
--
Vriendelijke groeten / Best regards,
René H. Hartman
www.hac-maarssen.nl
-
Re: tcp/ip interface has failed status. Cant ping ip address.
As René points out, your route is invalid. Also 10.x.x.x address
usually do not use a subnet like 255.255.255.0 This is probably
also incorrect. You would expect a subnet like 255.0.0.0
-
Re: tcp/ip interface has failed status. Cant ping ip address.
René H. Hartman wrote:
> Steve Richter schreef:
> > Tom Liotta wrote:
> >> Steve Richter wrote:
> >>
> >>> the tcp/ip interface to my router has a failed status:
> >>> Work with TCP/IP Interfaces
> >>>
> >>> Type options, press Enter.
> >>> 1=Add 2=Change 4=Remove 5=Display 9=Start 10
> >>>
> >>> Internet Subnet Interface
> >>> Opt Address Mask Status
> >>>
> >>> 10.10.10.1 255.255.255.0 Failed
> >>>
> >>> When I try to ping an IP address I get a "cant reach remote system "
> >>> error:
> >>> ping '4.2.2.1'
> >>> Verifying connection to host system 4.2.2.1.
> >>> Cannot reach remote system
> >>
> >> What routes are defined?
> >
> > only one route. *DFTROUTE with next hop set to the IP of my router:
> >
> > Work with TCP/IP Routes
> > System
> > Type options, press Enter.
> > 1=Add 2=Change 4=Remove 5=Display
> >
> > Route Subnet Next Preferred
> > Opt Destination Mask Hop Interface
> >
> > *DFTROUTE *NONE 10.10.10.1 *NONE
> >
> >
> >
> >
> >
> >>
> >> Tom Liotta
> >>
> >> http://zap.to/tl400
> >
> If I read this correctly you have a router with IP address 10.10.10.1.
> You defined your AS/400 IP address to be the same address. You cannot
> have two identical addresses on the same LAN, so when you start your
> interface, it sees the address is already active and fails (power down
> the router before you activate your interface and you'll see that the
> interface stays active).
>
> The interface address you assign is the address of the AS/400 network
> card, so it has to have a unique address. Try assigning it address
> 10.10.10.2 (if nothing else it using that) and you'll see it will work.
my as400 IP address in 10.10.10.160. the router is 10.10.10.1
Work with TCP/IP Interfaces
S
Type options, press Enter.
1=Add 2=Change 4=Remove 5=Display 9=Start 10=End
Internet Subnet Line Line
Opt Address Mask Description Type
10.10.10.1 255.255.255.0 LANLINE *ELAN
10.10.10.160 255.255.255.0 LANLINE *ELAN
127.0.0.1 255.0.0.0 *LOOPBACK *NONE
I tried to delete the 10.10.10.1 interface ( the one with a failed
status ) and the system said that interface had routes. Here are the
routes from Netstat:
Display Associated Routes
System
Interface internet address . . . . . . . . . : 10.10.10.1
Type options, press Enter.
5=Display details
Route Subnet Next Route
Opt Destination Mask Hop Available
10.10.10.0 255.255.255.0 *DIRECT *NO
224.0.0.0 240.0.0.0 *DIRECT *NO
*DFTROUTE *NONE 10.10.10.1 *NO
ILE is easy. IP is not!
-Steve
-
Re: tcp/ip interface has failed status. Cant ping ip address.
Steve Richter said the following on 30.11.2006 21:30:
> my as400 IP address in 10.10.10.160. the router is 10.10.10.1
As I see it, your as400 has both IP adresses (10.10.10.160 and 10.10.10.1)
>
> Work with TCP/IP Interfaces
> S
> Type options, press Enter.
> 1=Add 2=Change 4=Remove 5=Display 9=Start 10=End
>
> Internet Subnet Line Line
> Opt Address Mask Description Type
>
> 10.10.10.1 255.255.255.0 LANLINE *ELAN
> 10.10.10.160 255.255.255.0 LANLINE *ELAN
> 127.0.0.1 255.0.0.0 *LOOPBACK *NONE
>
>
> I tried to delete the 10.10.10.1 interface ( the one with a failed
> status ) and the system said that interface had routes. Here are the
> routes from Netstat:
Try to end 10.10.10.1 interface first. You will probably have to delete
*DFTROUTE also, and then add *DFTROUTE back again, since it is pointing to
the interface you are deleting.
> Display Associated Routes
> System
> Interface internet address . . . . . . . . . : 10.10.10.1
>
> Type options, press Enter.
> 5=Display details
>
> Route Subnet Next Route
> Opt Destination Mask Hop Available
> 10.10.10.0 255.255.255.0 *DIRECT *NO
> 224.0.0.0 240.0.0.0 *DIRECT *NO
> *DFTROUTE *NONE 10.10.10.1 *NO
>
>
> ILE is easy. IP is not!
You are probably a programer :-)
--
Dejan Rodiger - PGP ID 0xAC8722DC
Delete wirus from e-mail address
-
Re: tcp/ip interface has failed status. Cant ping ip address.
Dejan Rodiger wrote:
> Steve Richter said the following on 30.11.2006 21:30:
> > my as400 IP address in 10.10.10.160. the router is 10.10.10.1
>
> As I see it, your as400 has both IP adresses (10.10.10.160 and 10.10.10.1)
>
> >
> > Work with TCP/IP Interfaces
> > S
> > Type options, press Enter.
> > 1=Add 2=Change 4=Remove 5=Display 9=Start 10=End
> >
> > Internet Subnet Line Line
> > Opt Address Mask Description Type
> >
> > 10.10.10.1 255.255.255.0 LANLINE *ELAN
> > 10.10.10.160 255.255.255.0 LANLINE *ELAN
> > 127.0.0.1 255.0.0.0 *LOOPBACK *NONE
> >
> >
> > I tried to delete the 10.10.10.1 interface ( the one with a failed
> > status ) and the system said that interface had routes. Here are the
> > routes from Netstat:
>
> Try to end 10.10.10.1 interface first. You will probably have to delete
> *DFTROUTE also, and then add *DFTROUTE back again, since it is pointing to
> the interface you are deleting.
perfect. deleting the dftroute let me delete the interface. Now the
ping goes thru.
>
> > Display Associated Routes
> > System
> > Interface internet address . . . . . . . . . : 10.10.10.1
> >
> > Type options, press Enter.
> > 5=Display details
> >
> > Route Subnet Next Route
> > Opt Destination Mask Hop Available
> > 10.10.10.0 255.255.255.0 *DIRECT *NO
> > 224.0.0.0 240.0.0.0 *DIRECT *NO
> > *DFTROUTE *NONE 10.10.10.1 *NO
> >
> >
> > ILE is easy. IP is not!
>
> You are probably a programer :-)
absolutely. If I cant run a debugger on it, there are bound to be
problems.
thanks for all the help.
-Steve
