Can't ping my printer

This is weird.
I have a Kyocera FS1010 printer with a network card configured as
192.168.0.100. I can ping it from my machine when its booted in
wndows, but not from the same computer booted in Linux (MDK10.1 official.

'ifconfig' says:
eth1 Link encap:Ethernet HWaddr 00:11:11:BA0:68
inet addr:192.168.0.3 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::211:11ff:feba:d068/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1472 errors:0 dropped:0 overruns:0 frame:0
TX packets:642 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:398033 (388.7 Kb) TX bytes:80629 (78.7 Kb)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:249 errors:0 dropped:0 overruns:0 frame:0
TX packets:249 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:22735 (22.2 Kb) TX bytes:22735 (22.2 Kb)

.... and 'route' says
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 0 0 0 eth1
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default smoothwall 0.0.0.0 UG 0 0 0 eth1

Seems like I should be able to ping 192.168.0.100, but I can't.

Any pointers gratefully received

Your configuration seem to be correct.
Does your MDK10.1 has an firewall enabled?
You could try to disable them using 'service iptables stop':
try ping your printer after the service has been stopped.

Chano.

On Mon, 04 Jul 2005 05:08:52 -0700, luciano.cavallero wrote:

> Your configuration seem to be correct.
> Does your MDK10.1 has an firewall enabled?
No
> You could try to disable them using 'service iptables stop':
> try ping your printer after the service has been stopped.

'service iptables stop' reports
Cannot find iptables service

This has only been a problem since an adsl router was installed. I've
tried with a fixed ip address and with a dhcp server (router) acquired
address, all with the same effect (no ping from 192.168.0.100).

At the moment I'm reduced to saving documents on a windows partition,
rebooting into windows so I can print them - somebody save me from this!

> This has only been a problem since an adsl router was installed. I've
> tried with a fixed ip address and with a dhcp server (router) acquired
> address, all with the same effect (no ping from 192.168.0.100).

Where is eth0 in all this? If you have two NIC's, it is possible that
the network containing the printer is attached to eth0? Can you ping
the ADSL router? What is its address? Is it the gateway that showed up
in the output of route? How are things connected together? Hub?

Allen McIntosh wrote:
>> This has only been a problem since an adsl router was installed. I've
>> tried with a fixed ip address and with a dhcp server (router) acquired
>> address, all with the same effect (no ping from 192.168.0.100).
>

If you type 'arp -a' do you see an entry for the printer?

Cheers,
Chris

In the Usenet newsgroup comp.os.linux.networking, in article
<(E-Mail Removed)>, John Stolz wrote:

>This is weird.
>I have a Kyocera FS1010 printer with a network card configured as
>192.168.0.100. I can ping it from my machine when its booted in
>wndows, but not from the same computer booted in Linux (MDK10.1 official.

>'ifconfig' says:

Looks fine, though in a single NIC system, the Ethernet should be eth0.
What you _show_ will work OK

>... and 'route' says

Looks fine, as above

>Seems like I should be able to ping 192.168.0.100, but I can't.

What happens when you try? Does the computer catch or fire or something?

Try using 'tcpdump' and see what traffic is passing on the wire.

Old guy

Moe Trin wrote:

> In the Usenet newsgroup comp.os.linux.networking, in article
> <(E-Mail Removed)>, John Stolz wrote:
>
>>This is weird.
>>I have a Kyocera FS1010 printer with a network card configured as
>>192.168.0.100. I can ping it from my machine when its booted in
>>wndows, but not from the same computer booted in Linux (MDK10.1 official.
>
>>'ifconfig' says:
>
> Looks fine, though in a single NIC system, the Ethernet should be eth0.
> What you _show_ will work OK
>
>>... and 'route' says
>
> Looks fine, as above
>
>>Seems like I should be able to ping 192.168.0.100, but I can't.
>
> What happens when you try? Does the computer catch or fire or something?
>
> Try using 'tcpdump' and see what traffic is passing on the wire.
>
> Old guy
you really need the 4th cd.... then you can browse to it with your
linneibourhood but printers are tricky in mandrake

On Mon, 04 Jul 2005 17:43:28 -0400, Allen McIntosh wrote:

>> This has only been a problem since an adsl router was installed. I've
>> tried with a fixed ip address and with a dhcp server (router) acquired
>> address, all with the same effect (no ping from 192.168.0.100).
>
> Where is eth0 in all this?
Eth0 is a firewire card

> If you have two NIC's, it is possible that
> the network containing the printer is attached to eth0?
No, its definatly on the same network as the router and the other machines
I can see perfectly well
>Can you ping the ADSL router?
Yep

>What is its address?
192.168.0.1

> Is it the gateway that showed up in the output of route?
Yep

>How are things connected together? Hub?
Router has 4 ports, one of which is connected to a switch. I can ping
machines connected via the router and the switch, but not the printer
(which is connected to the switch)

Thanks for helping, any further suggestions would be appreciated

On Mon, 04 Jul 2005 23:19:43 +0100, can2002 wrote:

> Allen McIntosh wrote:
>>> This has only been a problem since an adsl router was installed. I've
>>> tried with a fixed ip address and with a dhcp server (router) acquired
>>> address, all with the same effect (no ping from 192.168.0.100).
>>
>
> If you type 'arp -a' do you see an entry for the printer?
>
> Cheers,
> Chris

Nope,
arp -a reports
? (192.168.0.106) at 00:50:FC:25:F9:BA [ether] on eth1
venus (192.168.0.104) at 00:50:FC:A0:17:EA [ether] on eth1
router (192.168.0.1) at 00:11:50:2F:9A:ED [ether] on eth1

printer is on 192.168.0.100

On Mon, 04 Jul 2005 20:05:51 -0500, Moe Trin wrote:


>>Seems like I should be able to ping 192.168.0.100, but I can't.
>
> What happens when you try?
Exactly nothing.

> Does the computer catch or fire or something?
Not normally, I didn't know ping could do that ;-)


> Try using 'tcpdump' and see what traffic is passing on the wire.
What's tcpdump? Neither I nor my system knows about it.
[root@uranus stolzy]# tcpdump
bash: tcpdump: command not found