Reply to Thread

Message

<blockquote data-quote="Hobbes" data-source="post: 1371118" data-attributes="member: 3371">You&#039;re thinking the same way I am thinking for the most part.It&#039;s likely:1.&nbsp; Ethernet cable2.&nbsp; Router Port3.&nbsp; Ethernet adapter in the computer4.&nbsp; Driver for the ethernet adapterAll are lower layers.&nbsp; 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.&nbsp; If the problem moves to another device the router port is defective.2.&nbsp; Swap cables both ends, ie trade cables at both ends between devices. If the problem moves to another device, the cable is defective.3.&nbsp; If 1 and 2 don&#039;t cause the problem to move to another device, I would search for the latest driver for the ethernet adapter.4.&nbsp; If it was a Dell I would reboot, press F12 during POST, and run diagnostics on the ethernet adapter.</blockquote>

[QUOTE="Hobbes, post: 1371118, member: 3371"] 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. [/QUOTE]

Verification