Forums
New posts
Search forums
What's new
New posts
New media
New media comments
Latest activity
Classifieds
Media
New media
New comments
Search media
Log in
Register
What's New?
Search
Search
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Navigation
Install the app
Install
More Options
Advertise with us
Contact Us
Close Menu
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
The Water Cooler
General Discussion
Any computer gurus out there?
Search titles only
By:
Reply to Thread
This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.
Message
<blockquote data-quote="poopgiggle" data-source="post: 1371076" data-attributes="member: 6406"><p>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? </p><p></p><p>If not, "destination host unreachable" just means that nothing is responding to that address.</p><p></p><p>If so, it means that your computer isn't talking to your router correctly. </p><p></p><p>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. </p><p></p><p>BEGIN TECHSPEAK</p><p>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)</p><p></p><p>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.</p><p>END TECHSPEAK</p><p></p><p>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.</p><p></p><p>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.</p><p></p><p>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.</p></blockquote><p></p>
[QUOTE="poopgiggle, post: 1371076, member: 6406"] 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. [/QUOTE]
Insert Quotes…
Verification
Post Reply
Forums
The Water Cooler
General Discussion
Any computer gurus out there?
Search titles only
By:
Top
Bottom
