Any computer gurus out there?

[SoonerDVM]

Ok guys. This has happened a few times since my last post, but until today, I never had time to run the requested tests. It just happened again a few minutes ago.

Here are the requested pings:

and the requested route print:

 

[tmadlock]

Instead of rebooting the computer, try removing the power cord from the router when this happens again. Let the router sit unplugged for at least 30 seconds so it will reset, and then plug it back in and see what happens. Also, and this may have been said already, swith out your ethernet cable between your computer and router just to rule that out.

 

[poopgiggle]

At a glance it looks like your routing tables are fine, but there wasn't any reason to suspect otherwise. Are you sure you have something connected to the network with the IPs 192.168.0.2 and .3?

If not, "destination host unreachable" just means that nothing is responding to that address.

If so, it means that your computer isn't talking to your router correctly.

This is where you get into fiddly details about how things are implemented, and that I would need to get a really detailed look at the network traffic to diagnose.

BEGIN TECHSPEAK
Something is definitely screwed up at the link layer, because communicating with an IP address on the same network doesn't require the router to do any router-y stuff at all; it just has to distribute Ethernet frames to the right places. Assuming the router is acting like a switch (and not a hub), something is getting screwed up with mapping ports to MAC addresses.(E: or something is screwed up with your computer's link layer communications)

That's probably why renewing the DHCP lease doesn't do anything (or you can't do it), because you're trying to fix the wrong layer. Restarting the computer, however, would cause the link-layer connection to refresh, which is why rebooting the computer fixes the problem.
END TECHSPEAK

Next time this happens, instead of rebooting your computer, try unplugging and re-plugging the Ethernet cable to the router. If it fixes the problem, then all the mumbo-jumbo I just said is probably the problem. If not, it's probably a problem with the Ethernet card itself.

I'm thinking you need a new router or a new Ethernet card. Hopefully the former because your Ethernet card is probably a part of your motherboard.

EDIT: You could MAYBE also have a software problem somewhere in your networking stack but I can't for the life of me think of anything that would cause that short of some hacker trying to get all tricky, and frankly you probably aren't important enough to attract the attention of someone with that much Kung Fu.

 

[Zombie]

different network cable or port tried? If not try that

if so I have an idea but gonna let others skirt all around a potentially easy fix first

 

[poopgiggle]

different network cable or port tried? If not try that

if so I have an idea but gonna let others skirt all around a potentially easy fix first

I'm at my parents' house and bored out of my mind. 'sperging out about networking is the only way I can stay sane.

1. If a different port fixes the issue, then the router is broken.

2. Didn't she try a different cable already?

 

[Hobbes]

BEGIN TECHSPEAK
Something is definitely screwed up at the link layer, because communicating with an IP address on the same network doesn't require the router to do any router-y stuff at all; it just has to distribute Ethernet frames to the right places. Assuming the router is acting like a switch (and not a hub), something is getting screwed up with mapping ports to MAC addresses.(E: or something is screwed up with your computer's link layer communications)


END TECHSPEAK

Next time this happens, instead of rebooting your computer, try unplugging and re-plugging the Ethernet cable to the router. If it fixes the problem, then all the mumbo-jumbo I just said is probably the problem. If not, it's probably a problem with the Ethernet card itself.

I'm thinking you need a new router or a new Ethernet card. Hopefully the former because your Ethernet card is probably a part of your motherboard.

You're thinking the same way I am thinking for the most part.

It's likely:

1. Ethernet cable
2. Router Port
3. Ethernet adapter in the computer
4. Driver for the ethernet adapter

All are lower layers.
The only reason I wanted the route tables was to see if packets were being routed to the proper interface and it looks like they are.

If I was working this at work I would:
1. Swap cables at the router. If the problem moves to another device the router port is defective.
2. Swap cables both ends, ie trade cables at both ends between devices. If the problem moves to another device, the cable is defective.
3. If 1 and 2 don't cause the problem to move to another device, I would search for the latest driver for the ethernet adapter.
4. If it was a Dell I would reboot, press F12 during POST, and run diagnostics on the ethernet adapter.

 

[SoonerDVM]

4. If it was a Dell I would reboot, press F12 during POST, and run diagnostics on the ethernet adapter.

Dude... it IS a Dell.... :p

 

[Hobbes]

Dude... it IS a Dell.... :p

Fortunate for you.


I would still go by the list 1,2,3,4 above.

Swapping cables, first at one end, and then at both ends, probably sounds very low tech, but it eliminates a LOT of guessing.
It also isolates hardware which is what both poopgiggle and I are homing in on.

 

[KOPBET]

Fortunate for you.


I would still go by the list 1,2,3,4 above.

Swapping cables, first at one end, and then at both ends, probably sounds very low tech, but it eliminates a LOT of guessing.
It also isolates hardware which is what both poopgiggle and I are homing in on.

which should have been done three weeks ago...

C'mon, eliminate the easy stuff and let's get down the road.

 

[Hobbes]

Computer Ethernet <-- ethernet cable <-- router <-- cable modem


So far we can say for sure that the cable modem is good to go because other devices behind the CM don't fail.
Next we need to isolate the router.

Sooner, unplug the ethernet cable from the PC to the router and the ethernet cable from the PS3 to the router and plug the cable from the PC into the port that had the PS3 plugged in and plug the PS3 into the port that had the PC plugged in.

If the PS3 starts to lose connectivity the same way the PC did we can say for certain the port on the router is bad.
Either replace the router OR don't use that port.

If the problem remains with the PC, we can say for certain that the router is good to go.
We will color the router green and proceed to testing the cables.