no ping from linux to xp

ola,

somehow i cannot ping to xp from my suse 10.0, but a ping from xp to
suse is no problem. the console does not even show the lost packages,
but when i abort by ctrl-c it reports a 100% loss.
does anyone have an idea?
thank you,

m.

On Fri, 03 Feb 2006 19:30:54 +0100, Markus Laux wrote:

> ola,
>
> somehow i cannot ping to xp from my suse 10.0, but a ping from xp to
> suse is no problem. the console does not even show the lost packages,
> but when i abort by ctrl-c it reports a 100% loss.
> does anyone have an idea?
> thank you,
>
> m.
Have a look at Firewall settings on the XP box, I found that an issue here.

Adrian

On Fri, 03 Feb 2006 19:33:39 +0000, Adrian Hodgson wrote:
> On Fri, 03 Feb 2006 19:30:54 +0100, Markus Laux wrote:
>
>> somehow i cannot ping to xp from my suse 10.0, but a ping from xp to
>> suse is no problem. the console does not even show the lost packages,
>> but when i abort by ctrl-c it reports a 100% loss.
>> does anyone have an idea?
>> thank you,
>>
> Have a look at Firewall settings on the XP box, I found that an issue here.

And, XP will _not_ respond to a broadcast ping:

$ ping -b 255.255.255.255

Jonesy
--
Marvin L Jones | jonz | W3DHJ | linux
Pueblo, Colorado | @ config.com | Jonesy | OS/2
*** I killfile X-Trace: posting.google.com followups in this ng

Adrian Hodgson schrieb:
>
> Have a look at Firewall settings on the XP box, I found that an issue here.
>
> Adrian

i have disabled the firewall for a test, it didn't respond anyway.
but what surprises me most is that the console does not even show the
lost packages until i ctrl-c...

Markus Laux wrote:
> Adrian Hodgson schrieb:
> >
> > Have a look at Firewall settings on the XP box, I found that an issue here.
> >
> > Adrian
>
> i have disabled the firewall for a test, it didn't respond anyway.

Which should mean that _if_ the ping echo requests are arriving, then a
reply should be generated. You can confirm this with ethereal by
watching the packets on the wire.

> but what surprises me most is that the console does not even show the
> lost packages until i ctrl-c...

No packets returned so there is nothing to report till you CTRL-C.
That is standard behavior. Btw, on Linux without the -c option, you
will continually ping at one second intervals till you do CTRL-C.

Since your pings from XP return properly, we can presume that Linux and
network devices know how to send packets from Linux to XP (and vice
versa). Be sure to ping IP addresses and not hostnames.

You can :
-- run ethereal on both boxes to capture the packets for clues
-- methodically ping from Linux to localhost, the Linux ethX IP(s),
Linux gateway to XP, Linux default gateway, then to XP in that order to
see where it fails.

Someone is failing to generate packets or is dropping them. Have you
tried traceroute?

good luck,
prg

On Sat, 04 Feb 2006 20:02:42 +0100, Markus Laux wrote:
> Adrian Hodgson schrieb:
>>
>> Have a look at Firewall settings on the XP box, I found that an issue here.
>
> i have disabled the firewall for a test, it didn't respond anyway.


> but what surprises me most is that the console does not even show the
> lost packages until i ctrl-c...

??

$ ping -c 3 xp

Jonesy
--
Marvin L Jones | jonz | W3DHJ | linux
Pueblo, Colorado | @ config.com | Jonesy | OS/2
*** I killfile X-Trace: posting.google.com followups in this ng

prg schrieb:
> You can :
> -- run ethereal on both boxes to capture the packets for clues
> -- methodically ping from Linux to localhost, the Linux ethX IP(s),
> Linux gateway to XP, Linux default gateway, then to XP in that order to
> see where it fails.
ping localhost OK
ping ip-linux OK
ping gateway OK
ping to xp NOT OK
>
> Someone is failing to generate packets or is dropping them. Have you
> tried traceroute?
linux:/$ # traceroute 10.0.0.2
traceroute to 10.0.0.2 (10.0.0.2), 30 hops max, 40 byte packets
1 * * *
2 * * *
3 * * *
4 * * *

but i think it is better to forget pinging and to hope that samba
doesn't care about this.
however, thanks for support,

m.