Networking & wireless forum: Can't ping 1 computer on network, all access in Network Neig

Pingable PC #1:
IP: 192.168.1.104
Subnet: 255.255.255.0
Default Gateway: 192.168.1.1

Pingable PC #2:
IP: 192.168.1.95
Subnet: 255.255.255.0
Default Gateway: 192.168.1.1

Unpingable PC:
IP: 192.168.1.110
Subnet: 255.255.255.0
Default Gateway: 192.168.1.1

No, I did not know ZoneAlarm would remain running when you turned off the option to run at startup, then rebooted. Hmmm

There is a firewall on the router. But I don't understand this. If there is a firewall on the router, and it is turned on, why aren't all of the computers equally affected.

Likewise for ZoneAlarm. All are running with ZoneAlarm.

Just curious is all...

So, here's what I've done:

I turned off the router firewall.

I uninstalled ZoneAlarm.

I rebooted.

I ran WinSockXPFix.

Tried to ping (after checking IPConfig).

Request timed out.

Not a problem, cuz if I knew what you know, I'd have been troubleshooting this thing properly long ago! Now I have to ask the expert (Bob) - and thank you for your time and experience, by the way.

All computers can ping 192.168.1.1

What next?

Router cannot ping troublesome computer. Router pings other 2 computers fine.

I don't understand what you mean about a Linux computer from CD. I don't have a Linux computer.

I hate to show my lack of expertise, but you are losing me.

I've checked out the DAMN SMALL LINUX website, but I can't for the life of me figure out what to even download! Their FAQ says download the DSL-X.X.X.ISO, but I see quite a few of those and all sorts of different folders that mean absolutely nothing to me.

At the risk of losing your assistance, I have to ask for more specific help here!

ping 192.0.1.1 worked from the failed machine to the router.

The ping from the router to the machine failed. Which puts the suspect on the machine (cables changed... not homemade.)

I do have a sneaking suspicion about the OS install but I boot my linux cd and perform that test to rule out the hardware possibility.

There is an even more remote possibility of a failed port on the router. But that's way down the possibility list. Easy to dismiss.

Bob

On the failed machine I take it you uninstalled ZA and ran the winsock repair tool. I'm proceeding as if this was accomplished.

I also dropped a hint about home made cables which drew no response so I take it the cable was not home mode and has been changed out.

Bob

Okay Bob - here's what I've now come up with.

I got DAMN SMALL LINUX, burned a bootable CD, booted from that CD, then tried to ping that computer. Request timed out.

I then did IFCONFIG -A and here's what it says:

Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisoins:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0B)

What does all that mean?

This is crazy, and I don't understand a word of what you're saying anymore, but I'm still following you, believe it or not. (And that sentence makes absolutely no sense whatsoever) The fact I could even boot with that disk is a miracle in and of itself. Chuckle.

DHCP Server is enabled in my Linksys router. Max users - 5=.

I'll have to check out the ping after I get back from taking the young'uns to the dentist.

ifconfig

All by itself

ifconfig *

Tell all, but I strongly remember using -a for all. But http://www.computerhope.com/unix/uifconfi.htm notes

ifconfig eth0

Bob

"Also, the default user doesn't have the permission to use ping, so you have to become root by typing "sudo su -" just to make sure you can ping google.com (you can also use sudo of course). It's only a detail but I found that annoying."
http://www.linuxforums.org/reviews/damn_small_linux_3.0_review.html

Retry ifconfig and ping...

But if eth0 isn't showing up then tell me about this machine, what is it?

Bob

1. The linux test tells me if we have a hardware or software issue. The keyboard issue may be a BIOS setting, but it's the one that has no specific name except KEYBOARD USB LEGACY SUPPORT or similar. Same for mouse.

2. I can't find your Dell's chipset. I have a suspicion that if we were to install the motherboard chipset driver and then retest and if fail then the network card driver we would strike off another common issue. But I can't point to that since I couldn't determine what a DXPO51 is made of. It wasn't on the Dell site and the XPS has many different models with varying Intel Chipsets.

Bob

Dead for us. Too bad since the forces us to dive into Windows and hope a driver update will help. I need the Intel Chipset and maybe a link on Dell's website about your machine to offer which driver I would install.

As to DSL, since it didn't go, I would try PCLinuxOS next. While I prefer the Big Daddy CD, it's a big download. It may find your network card when DSL didn't.

Bob