can't see computer from internal network

I hope this is the right place to post this, as I believe it is a linux
issue.

I recently installed Fedora Core 5 on one of my home PC's. After
installing I have ssh setup and running. I have two other PC's in my
house, one a windows xp desktop, and the other a windows xp laptop
(connected to the network via wireless).

Here's the situation.

1). I can ssh into the linux box from my xp desktop pc and ping it.

2). I can ping my laptop from my xp desktop and my laptop can ping my
xp desktop.

3). My laptop cannot ping my linux box, nor can my linux box ping my
laptop.

I am curious if anyone has any ideas as to what might be going on? If
more information is needed please let me know, I'd be more than happy
to provide any details.

Thanks.

<(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ups.com

> I recently installed Fedora Core 5 on one of my home PC's. After
> installing I have ssh setup and running. I have two other PC's in my
> house, one a windows xp desktop, and the other a windows xp laptop
> (connected to the network via wireless).
....
> 3). My laptop cannot ping my linux box, nor can my linux box ping my
> laptop.
>
> I am curious if anyone has any ideas as to what might be going on? If
> more information is needed please let me know, I'd be more than happy
> to provide any details.

Someone might be better able to advise you if you provided information about
the wireless access point, and the output of "route print" on the XP boxes
and "/sbin/route -n" on the Linux.

Certainly...

My router is a D-Link DI-524. It has an address of 192.168.0.1

Here is the linux routing table.

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0
eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0
eth0
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0
eth0

Working PC Routes (Hamachi is installed on both machines, I don't think
that is affecting anything)
================================================== =========================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...7a 79 05 0f 3b 91 ...... Hamachi Network Interface
0x3 ...00 30 1b 30 6f ee ...... NVIDIA nForce MCP Networking Controller
- Packet Scheduler Miniport
================================================== =========================
================================================== =========================
Active Routes:
Network Destination Netmask Gateway Interface
Metric
0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.100
20
5.0.0.0 255.0.0.0 5.15.59.145 5.15.59.145
20
5.15.59.145 255.255.255.255 127.0.0.1 127.0.0.1
20
5.255.255.255 255.255.255.255 5.15.59.145 5.15.59.145
20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
169.254.0.0 255.255.0.0 192.168.0.100 192.168.0.100
30
192.168.0.0 255.255.255.0 192.168.0.100 192.168.0.100
20
192.168.0.100 255.255.255.255 127.0.0.1 127.0.0.1
20
192.168.0.255 255.255.255.255 192.168.0.100 192.168.0.100
20
224.0.0.0 240.0.0.0 5.15.59.145 5.15.59.145
20
224.0.0.0 240.0.0.0 192.168.0.100 192.168.0.100
20
255.255.255.255 255.255.255.255 5.15.59.145 5.15.59.145 1
255.255.255.255 255.255.255.255 192.168.0.100 192.168.0.100 1
Default Gateway: 192.168.0.1
================================================== =========================
Persistent Routes:
None


and my laptop (wireless) that is not working. (hamachi is also
installed here.)

nterface List
0x1 ........................... MS TCP Loopback interface
0x2 ...7a 79 05 0f 3d ca ...... Hamachi Network Interface
0x3 ...00 0f 1f 2a 09 77 ...... Broadcom 440x 10/100 Integrated
Controller - Packet Scheduler Miniport
0x4 ...00 0e 35 7f 5d 2f ...... Intel(R) PRO/Wireless 2200BG Network
Connection - Packet Scheduler Miniport
================================================== =========================
================================================== =========================
Active Routes:
Network Destination Netmask Gateway Interface
Metric
0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.105
25
5.0.0.0 255.0.0.0 5.15.61.202 5.15.61.202
20
5.15.61.202 255.255.255.255 127.0.0.1 127.0.0.1
20
5.255.255.255 255.255.255.255 5.15.61.202 5.15.61.202
20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
192.168.0.0 255.255.255.0 192.168.0.105 192.168.0.105
25
192.168.0.105 255.255.255.255 127.0.0.1 127.0.0.1
25
192.168.0.255 255.255.255.255 192.168.0.105 192.168.0.105
25
224.0.0.0 240.0.0.0 5.15.61.202 5.15.61.202
20
224.0.0.0 240.0.0.0 192.168.0.105 192.168.0.105
25
255.255.255.255 255.255.255.255 5.15.61.202 5.15.61.202
1
255.255.255.255 255.255.255.255 192.168.0.105 3
1
255.255.255.255 255.255.255.255 192.168.0.105 192.168.0.105
1
Default Gateway: 192.168.0.1
================================================== =========================
Persistent Routes:
None


Let me know if any more information is needed. Thanks again.

On 1 Apr 2006, in the Usenet newsgroup comp.os.linux.networking, in article
<(E-Mail Removed) .com>, (E-Mail Removed)
wrote:

>Kernel IP routing table
>Destination Gateway Genmask Flags Metric Ref Use Iface
>192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
>169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
>0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0

OK - local net - reach the world through 192.168.0.1. What happened to the
loopback?

>Active Routes:
>Network Destination Netmask Gateway Interface Metric
> 0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.100 20
> 5.0.0.0 255.0.0.0 5.15.59.145 5.15.59.145 20
> 5.15.59.145 255.255.255.255 127.0.0.1 127.0.0.1 20
> 5.255.255.255 255.255.255.255 5.15.59.145 5.15.59.145 20

OK - where did using 5.0.0.0 come from. That network is not currently
allocated. Please don't pull addresses out of mid-air. There are over
17 million addresses in RFC1918 you could be using for local stuff.

> 192.168.0.0 255.255.255.0 192.168.0.100 192.168.0.100 20
> 192.168.0.100 255.255.255.255 127.0.0.1 127.0.0.1 20

So it looks like two interfaces here (192.168.0.100 and 5.15.59.145) plus
loopback

>Active Routes:
>Network Destination Netmask Gateway Interface Metric
> 0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.105 25
> 5.0.0.0 255.0.0.0 5.15.61.202 5.15.61.202 20
> 5.15.61.202 255.255.255.255 127.0.0.1 127.0.0.1 20
> 5.255.255.255 255.255.255.255 5.15.61.202 5.15.61.202 20
> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
> 192.168.0.0 255.255.255.0 192.168.0.105 192.168.0.105 25
> 192.168.0.105 255.255.255.255 127.0.0.1 127.0.0.1 25

and two interfaces here (192.168.0.105 and 5.15.61.202) plus the loopback

>Let me know if any more information is needed. Thanks again.

All three systems expect to be able to talk _directly_ to each other
without using an intermediate router. Unless your wireless router is
bridging, this won't be the case. Use a packet sniffer - and try to
ping the other host. Does the Linux box ask for (ARP) the MAC address
of the lapdoggy, and does the _router_ respond with it's MAC but the
IP of the lapdog. Or does no one respond, because the lapdoggy never heard
the ARP. The same would be true from the lapdog - does it ARP and get
a response from the router when trying to talk to the Linux box?

Old guy