Network techies, I'm in a brainfart - please help!

[thermodynamic]

I've got 3 computers on my network, using TCP/IP with static addresses.

(On edit: Unless specified, I am doing all the pinging from my Linux box, 192.168.0.4 - sorry for the miscommunication!)

Computers 192.168.0.2 and 192.168.0.6 can ping to each other, but 192.168.0.4 can't ping anything. I've disabled firewalls on all the computers when checking things.

However, if I ping 192.168.0.4 (from itself) there IS a response. Ditto for pinging the local addy of 127.0.0.1.

The switch in place is all 3 jacks are lit and set to 100Mbit/Full Duplex on all so I'm positive the cables are good, probably.

The computer with the problem (192.168.0.4) is using an integrated NIC on the mobo (Abit NF7). I do have a spare NIC, but would rather not use it.

However, I had to install the nividia motherboard Linux drivers in order for SuSE Linux 8.2 Pro to even see the integrated NIC. But since rebooting the card is seen and the address is applied to the card, successfully. And the only configuration options in the BIOS setup are to either enable or disable the card. :eyes:

I'm utterly baffled and I ought to know better. I'm probably missing out on something utterly simple. I shouldn't be a wuss and try out the other NIC (a 3com NIC) but I'd prefer getting the onboard card to work.

Any suggestions would be greatly appreciated. Thanks!

The other two boxes are Windows XP Pro.

[yella_dawg]

1. 1. Use the add-in NIC

2. Suspect the MicroJunk boxes of being too stupid to ping a real computer.

I don't do SuSe, but if it ain't hardware, it's gotta be Windows.

yella

[mreilly]

2. Subnet mask OK?

Double check the subnet mask. Gateway shouldn't matter since it's a local LAN. If you have a DHCP server set up, you might set the NIC for DHCP and see if it grabs the address.

I can't say I know much about SUSE Linux; I'm an XP/Red Hat man. But it sounds like maybe the network settings are allowing incoming ping but are not permitting an outbound ping. You say the firewall is turned off, but are there features that have to be specifically enabled such as ICMP? Maybe that wouldn't matter since the NIC is RETURNING ICMP requests.

I hate to say it but I would try the other NIC just for the hell of it. It might also be the driver is somehow wonky but I've never heard of a partially functioning driver; it's either all or nothing in the wonderful world of networking, at least in my experience. Theoretically I guess the card could be damaged somehow, but not likely.

[thermodynamic]

6. Class C throughout

255.255.255.0

The Win machines can see each other completely. The Linux box can't ping to the Windows boxes and the Windows boxes can't ping the Linux box so I don't think either inbound or outbound is working. :-(

It's possible the NIC port on the mobo itself is bad, which is why I can ping myself (127.0.0.1 or 192.168.0.4) but nobody else. I bloody well hope not, it's a new mobo and I don't want to tear the box apart to get the thing exchanged. :eyes:

Here's a thought, I'm using SuSE's graphical interface to configure. Where would I find the text config files so I can tinker with them directly, if I dare? :evilgrin:

Thx!

[lcordero]

3. Have you tried a diff. switch or hub?

or maybe a diff. port on a hub or switch?
I've had problems before with ports not functioning

[thermodynamic]

4. I know the ports work

I recently moved the Windows box from port 1 to port 3.

The new Linux box is situated on port 1. But I appreciate the thought nonetheless!

[mreilly]

5. You're sure it's not a duplicate IP, I take it

I'm just thinking out loud here. I re-read your original post a couple of times. On-board NICs are tough to work with; they just seem stubborn sometimes. Try a different IP address, maybe, just for the hell of it. Maybe try doing a portscan of this IP from another device to see what kind of shape its in. When all else fails maybe restarting the device will help?

[DBoon]

7. NIC wierdness

I noticed the same thing a few years ago - a 3com NIC that worked fine with Windows, but showed the same behavior you described with Linux.

I basically swapped out the NIC for a slightly different 3com model and the new one worked fine (helps to have spare parts sometimes). Weird, no one could figure out why this was happening.

[frylock]

8. link speed on 192.168.0.4?

[thermodynamic]

9. I dunno where to look

I'm a linux newbie and the graphical configuration tool omits that particular option ( :grr: ) but the switch shows the link at 100/Full duplex. I will check into this further as it could be the reason...

[DS1]

10. few things

Have you disabled any services from running at startup on the XP boxes?

Try deleting the NIC in the Control Panel and rebooting, it should redetect and see what happens. That fixed a problem for me once.