Networking Forums

Networking Forums > Computer Networking > Linux Networking > can't even ping

Reply
Thread Tools Display Modes

can't even ping

 
 
johnny bobby bee
Guest
Posts: n/a

 
      02-08-2004, 08:52 PM
hey folks,

after shutting down my laptop (dual boot winXP/Mandrake 9.1) last night
i couldn't get kde to start this AM.
while i was troubleshooting that i was trying to 'ssh' to another linux box
that i have (redhat) and it didn't work. so i starting troubleshooting
that too.

at this point i can't even ping any of my other 2 computers on my LAN
from the troubled Mandrake
laptop. the other 2 PCs can see and connect to one another fine, but non
of them can
even ping my mandrake laptop.

ifconfig:
gives me an inet addr: 192.168.2.100 Bcast: 192.168.2.225 Mask:255.255.255.0
and everything else looks to be the same as ever. even the readings for
'lo' seem
normal. but attempting to ping anything from the mandrake laptop results
in PING just
hanging and never timing out, no error messages, nothing. i have to
'ctrl c' to stop it.
as root i've tried starting and stopping network services. nothing is
happening.

if i boot to winXP (dual-boot) everything is fine. can ping all LAN PCs
and can surf.

all this happened this morning after shutting down the laptop. before
going to bed all was well.

thanks for any insights,
johnny


--
Woolsey-Swanson Rule:
People would rather live with a problem they cannot solve
than accept a solution they cannot understand.

remove .eh to email

 
Reply With Quote
 
 
 
 
Bit Twister
Guest
Posts: n/a

 
      02-08-2004, 09:13 PM
On Sun, 08 Feb 2004 21:52:28 GMT, johnny bobby bee wrote:

> at this point i can't even ping any of my other 2 computers on my
> LAN from the troubled Mandrake laptop. the other 2 PCs can see and
> connect to one another fine, but non of them can even ping my
> mandrake laptop.


> in PING just hanging and never timing out, no error messages,
> nothing. i have to 'ctrl c' to stop it.


Normal if you cannot get any reply back. Does the following two work
ping -c 1 localhost
ping -c 1 $(hostname)
ping -c 1 -t 3 redhat_ip_addy_here # still broke ??

> as root i've tried starting and stopping network services. nothing is
> happening.


Hope that is terminology problem. You did get an [ OK ] response I assume.

> if i boot to winXP (dual-boot) everything is fine. can ping all LAN PCs
> and can surf.


That tells us the hardware is good.

> all this happened this morning after shutting down the laptop. before
> going to bed all was well.


going to guess you do not have a default route set. Example

route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.2.1 0.0.0.0 UG 0 0 0 eth0

cat /etc/sysconfig/network
HOSTNAME=wb.home.invalid
NETWORKING=yes
GATEWAY=192.168.2.1 <===== guessing here
GATEWAYDEV=eth0


cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
BOOTPROTO=static <==== guessing
IPADDR=192.168.2.100
NETMASK=255.255.255.0
NETWORK=192.168.2.0
BROADCAST=192.168.2.255
ONBOOT=yes <==== assumed this

 
Reply With Quote
 
Bit Twister
Guest
Posts: n/a

 
      02-08-2004, 09:23 PM
On Sun, 08 Feb 2004 21:52:28 GMT, johnny bobby bee wrote:

> at this point i can't even ping any of my other 2 computers on my
> LAN from the troubled Mandrake laptop. the other 2 PCs can see and
> connect to one another fine, but non of them can even ping my
> mandrake laptop.


> in PING just hanging and never timing out, no error messages,
> nothing. i have to 'ctrl c' to stop it.


Normal if you cannot get any reply back. Does the following two work
ping -c 1 localhost
ping -c 1 $(hostname)
ping -c 1 -t 3 redhat_ip_addy_here # still broke ??

> as root i've tried starting and stopping network services. nothing is
> happening.


Hope that is terminology problem. You did get an [ OK ] response I assume.

> if i boot to winXP (dual-boot) everything is fine. can ping all LAN PCs
> and can surf.


That tells us the hardware is good.

> all this happened this morning after shutting down the laptop. before
> going to bed all was well.


going to guess you do not have a default route set. Example

route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.2.1 0.0.0.0 UG 0 0 0 eth0

cat /etc/sysconfig/network
HOSTNAME=wb.home.invalid
NETWORKING=yes
GATEWAY=192.168.2.1 <===== guessing here
GATEWAYDEV=eth0


cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
BOOTPROTO=static <==== guessing
IPADDR=192.168.2.100
NETMASK=255.255.255.0
NETWORK=192.168.2.0
BROADCAST=192.168.2.255
ONBOOT=yes <==== assumed this

 
Reply With Quote
 
johnny bobby bee
Guest
Posts: n/a

 
      02-08-2004, 11:58 PM

Bit Twister wrote:

> Normal if you cannot get any reply back. Does the following two work
> ping -c 1 localhost
> ping -c 1 $(hostname)
> ping -c 1 -t 3 redhat_ip_addy_here # still broke ??
>


none of those work. they all result in PING just hanging there.
can't even ping -c 1 127.0.0.1

>
>>as root i've tried starting and stopping network services. nothing is
>>happening.

>
>
> Hope that is terminology problem. You did get an [ OK ] response I assume.
>


yes, sorry - when i do:
'/etc/rc.d/init.d/network restart'
i get all the devices going down then back up with [ok] all the way. no
error messages.

>
> route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
> 0.0.0.0 192.168.2.1 0.0.0.0 UG 0 0 0 eth0
>


funny thing is, when i issue:
'route -n' i get the routing table back instantly:
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.2.1 0.0.0.0 UG 0 0 0 eth0

when i do:
'route' it gets stuck after the 127.0.0.0 line (5 seconds+) before it
returns the last line:
default 192.168.2.1 0.0.0.0 UG 0 0 0 eth0


> cat /etc/sysconfig/network
> HOSTNAME=wb.home.invalid
> NETWORKING=yes
> GATEWAY=192.168.2.1 <===== guessing here
> GATEWAYDEV=eth0
>


my etc/sysconfig/network was:
HOSTNAME=lin-shine
NETWORKING=yes

i added the GATEWAY lines and it made no difference.

>
> cat /etc/sysconfig/network-scripts/ifcfg-eth0
> DEVICE=eth0
> BOOTPROTO=static <==== guessing
> IPADDR=192.168.2.100
> NETMASK=255.255.255.0
> NETWORK=192.168.2.0
> BROADCAST=192.168.2.255
> ONBOOT=yes <==== assumed this
>


my /etc/sysconfig/network-scripts/ifcfg-eth0 is:
DEVICE=eth0
BOOTPROTO=dhcp
ONBOOT=yes

ifconfig still gives me:
eth0
inet addr: 192.168.2.100 Bcast: 192.168.2.225 Mask:255.255.255.0

lo
inet addr:127.0.0.1 Mask:255.0.0.0

all which looks right to me.

any other suggestions?

--
Woolsey-Swanson Rule:
People would rather live with a problem they cannot solve
than accept a solution they cannot understand.

remove .eh to email

 
Reply With Quote
 
Bit Twister
Guest
Posts: n/a

 
      02-09-2004, 12:48 AM
On Mon, 09 Feb 2004 00:58:36 GMT, johnny bobby bee wrote:

I assume ifconfig has something like
eth0 Link encap:Ethernet HWaddr 00:A0:CC:21:C5:EA
inet addr:192.168.2.100 Bcast:192.168.2.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1

> none of those work. they all result in PING just hanging there.
> can't even ping -c 1 127.0.0.1


Yuck, no idea where to search for that one. If you get that solved,
the rest aught to work.


> 'route' it gets stuck after the 127.0.0.0 line (5 seconds+) before it
> returns the last line:


That is because it is trying to do a dns lookup.

> any other suggestions?


Nope, assuming you have looked at /var/log/messages for module errors,
I am tapped out of suggestions.

 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
When Client Ping DC not respond,but when DC ping clients they resp ahmad Windows Networking 3 07-17-2007 07:44 PM
Ping 224.0.0.2 ping: sendmsg: Operation not permitted interessato@gmail.com Linux Networking 4 01-24-2006 02:47 AM
Ping from cron not having same effect as ping from console Dean Schulze Linux Networking 2 02-24-2004 08:10 PM
Some services working but can't ping (not ping-able) Micah Elliott Linux Networking 1 12-05-2003 09:47 AM
Windows ping and Linux ping command? tom Linux Networking 5 11-10-2003 08:52 PM



1 2 3 4 5 6 7 8 9 10 11