Re: Strange Network Problem
- From: "w_tom" <w_tom1@xxxxxxx>
- Date: 2 Aug 2006 23:20:14 -0700
I'm not sure what line the line tester would be testing. But if
tester is for AC electric, it will report nothing useful. If an
ethernet cable tester, see below.
Laptop making a connection at 100 Mhz implies the 100 Mhz option
inside that one router port is OK. Same test must be performed on each
and every router port. Only then have we eliminated that one router as
one potential reason for failure. But (as addressed in another
paragraph) you were using different routers with each test and not
detailing that fact. IOW again, you have confused details - made more
than one change with each test making an accurate reply almost
impossible.
That test that confirms router port working at 100 Mhz still does not
eliminate each wire (inside walls) as a potential reason for failure.
Just another reason why the same test is conducted to each router port
using only same cable to same laptop. Then the same test conducted by
only replacing 'ten foot' cable from laptop to router with 'inside
walls' wire. Then do same test; this time only replace laptop with a
desktop computer - again using only exact same ethernet cables.
Repeat that desktop computer test to every port on that same router -
not even changing router's AC electric connection. It is tedious, it
is anal, and yet necessary to (for example) locate failures that may be
masked by resiliency and redundancy inside all that hardware. Change
only one item to then perform that same battery of tests.
BTW, an ethernet hardware diagnostic (ie provided by ethernet
interface manufacturer) was also defined. Amazing how an ethernet test
using Windows is so resilient as to not detect a noisy or otherwise
defective connection. Ethernet hardware diagnostic (running without
Windows) may detect a slower, intermittent, or periodically failing
ethernet. Windows is designed to make same failures irrelevant.
Hardware diagnostics report same problems that Windows must mask.
Defined previously was another tool to find an ethernet problem -
hopefully you have already downloaded and used.
Dave, I never told you what is right or wrong. I told you how to go
after the problem without wasting time, and without any consideration
for irrelevant emotions. You don't care how I told you. You only care
about making a problem permanently solved. Take a 'kill the problem'
attitude. Only women who are poor problem solvers also waste time with
the Oprah attitude of "but how did you feel'. Sorry. I'm not
politically correct which is why problems are solved immediately. The
blunt answer is the useful one. If you were told what you did wrong,
then be thankful that the post was honest rather than politically
correct. You care about solving the problem yesterday. Solve the
problem no matter how right or grossly misinformed you once were.
Never mentioned was a 'different router'. Such details imply you
were also testing using a different ethernet router. Again, confusing
your support by not providing another critical detail. That was my #1
point. Provided too late was another critical detail - another router
- long after it was required in your original post.
Defined earlier were various types of wiring failures that would work
OK (maybe with the laptop) and yet were still defective. Will a line
tester find all such problems? No. Detecting some previously listed
wiring failures require either 1) special 'hundreds of dollars' tester
OR 2) can be suspected by listing each test with only one change each
time OR 3) required visual inspection with an eyelet (or equivalent)
magnifying glass. A conductivity tester will not detect many wiring
problems - which is why a tester should cost hundreds or will not be
useful.
Again, this sounds all quite anal. Numerous reasons for your
symptoms means a tedious 'one change at a time' testing is necessary.
Remember, Windows and that laptop have a bad habit of 'correcting'
defects. Sometimes what is tested with Windows or with that laptop as
OK may actually be defective - because some hardware is so resilient.
Sorry to be blunt, but ethernet problems get confusing when testing
is not anally 'only one change per test'. Use of a second router
without posting same is just another reason your replies would be
confused. Again, you don't care what was done wrong or right (an
emotional reasponse). Care about how to correct a defective procedure.
Dave A wrote:
Maybe instead of telling all the things I did wrong, you could ask for more
information. If I knew all the information you needed, I probably would not
be asking for help.
The WiFi used to say disabled but I took that out of the picture by using a
different 8 port router (no wireless). same results.
If I set the computers up in the room where the cable modem and router are,
I have no problems what so ever. All computers work and all connect at 100
mps. When I take them back to the individual rooms, I get the limited or no
connection. I do however get a conection with the lapptop. The connection
there is also 100 mps.
I can also say that I have tried all port on the router and the results are
the same.
My next step is to test the wiring on the lines. I have had a close friend
loan me a line tester and I will test in the next say or so. (I am out of
town right now).
.
- References:
- Re: Strange Network Problem
- From: Chuck
- Re: Strange Network Problem
- From: Chuck
- Re: Strange Network Problem
- From: Dave A
- Re: Strange Network Problem
- From: w_tom
- Re: Strange Network Problem
- From: Dave A
- Re: Strange Network Problem
- Prev by Date: Re: ICS on a networked computer connected through USB to a DSL Modem
- Next by Date: Re: DNS Caching addresses
- Previous by thread: Re: Strange Network Problem
- Next by thread: User accounts
- Index(es):
Relevant Pages
|
