testing a cat5 network

[22Admub]

I'm installing a cat5 network. I just installed in one port, and I figured I should test that before I move on. However, I don't have a laptop or a broadband connection(hopefully I will in a few days). So, instead of draggin my computer in there, I just took the router and hooked it up to the port, then I connected the computer to the patch panel(they're in the same room). In order to test it, I simply did the following command in WinXP: ping -l 65000 192.168.2.1 That basically pings the router with a 65kilobyte packet. that took 49 ms. Sounds about right(it takes 46 seconds when I have it directly connected to the router). So I was just wondering if this is a good enuogh test, and if there's better way to do it with the stuff I got(I don't want to have to buy a cable tester, unless absolutely necessary).

On a kinda side note, why does it take almost 50 ms to ping the router, but only about 12-13 to ping another computer connected thru the router?

 

[22Admub]

couple more questions, after I connect everything together the first ping never goes through and gets a request timed out, then after that it always works fine, no matter how many times I ping(left it for a good ten minutes doing that). Is that a major problem or anythign. The other question is, is there any way to test if the network will work at gigabit speeds, using the stuff I got(2 comps and a router), or would I have to get gigabit capable equipment?

 

[22Admub]

Another question/problem
Not sure if this will get answered like the others before it, but here it goes.
I had one of the cables wired into the patch panel and noticed that one of the wires on it had broken off(before that the connection was fine, using the test in my first post). So what I did was, just yanked out the cable from the patch panel, then I cut off a few inches of it and put it back on, simple. But the thing is when I connect it to my older computer, it connects at 100Mbps, but, when I try to ping it, it only goes thru about half the time. And when I try try to ping it with a packet over 1,000 bytes, it doesn't work at all. However, if I force the network car to go at 10Mbps, it works flawlessly, even with a 65,000 byte packet. And when I connect it to my newer computer, it works perfectly, at both speeds 10/100. So I do something wrong here with the patch panel? BTW, the old computer works perfectly on the other 7 connections I've wired so far.

Is there anyone that could answer any of the questions in any of these 3 posts? I'd really appreciate it.

 

[zetter]

Sounds like you need a PentaScanner.

If you've only used Cat5 cabling, you're unlikely to be able to run Gigabit Ethernet reliably. For that, you'd need at least Cat5e or Cat6.

As for why your cabling only works some times and not others, you could have screwed up the cable pairing on the termination blocks or you haven't terminated the cables at reasonably even lenghts.

 

[22Admub]

my fault, it is cat5e. I checked, and doubled checked the cables, they're in the right place(both the jacks and the patch panel have color codes for both wiring standards, and I've been using the "A" standard). And all the wires are at an even length to within a couple mm. could it be the quality of the NIC? I have a 25 ft. crossover that works fine when I had it connceted between 2 compputers that had the same onboard NIC as my newer comp. But if I connect my newer and older ones together with the crossover, I can only do 10Mbps.

 

[gunrunnerjohn]

What you're describing is the classic symptom of not getting the twisted pairs in the correct places. Just because you have continuity on the leads, that doesn't mean the cable is wired correctly. I just rewired a ton of cables at a client for that very reason, the cable experts didn't have a clue about Ethernet cables.

 

[22Admub]

yeah, but why would it work on one comp, and not the other? if it was incorrect wiring(which I'm 99.9% sure it isn't, I even checked a 3rd time), then wouldn't the problem repeat itself on other computers?

BTW, can anyone give me an answer to my first post? That's the one that's most important to me, the other's are more or less curiosity.

 

[spidey07]

The only way to test a CAT5 installation is to scan the cable with a very expensive cable scanner. Only then can you be sure the network is up to par to run 100 Base-T.

That being said raw file transfers of very large files is an acceptible test. Check the network cards on both ends and make sure ther are ZERO errors. You you never get any errors of any kind on a good net.

if you aren't getting 7-10 megabytes/sec of transfer speed then something is wrong. Most times you can blame mis-wired or split pairs (only one cable of a cable pair is attached in the right place).

To put this in perspective I've been doing this for 12 years now and still only get 1 our of 3 cables to pass a CAT5e/6 scan and they barely pass at that. Hence I tell my guys "if I catch you making a patch cable you will get a written warning". And they're a lot better at cabling than I ever was. No, this stuff isn't hard but until you scan the cable you just never know and it will bite you soon.

So to answer your original question - no, a large ping is not an acceptible test. A huge transfer of multi gigabytes can give you an idea of how sound the net is. But only a full scan of the cables will give you a "yes, its good".

 

[22Admub]

Is there any type of freeware program that I can run on 2 comps on the network, just to see if I did the installation coreectly? I figure I'll just move my comp from jack to jack, and test all the connections. The network doesn't need to be able to transfer files at super fast speeds, I just need to make sure that all the runs of wire will all the computer on the other to end to browse the internet, and have low lag. I guess I'll lug my comp around to test out each port some time in the next few days.

 

[cmetz]

Set up a ftp client and server. Create a large file. ftp that file from one box to the next. Check your interface info on both sides for errors. Not a great way to do things but pretty simple.

 

[skyking]

try qcheck, download it here.
Link.

 

[zetter]

Try re-terminating your cabling to the 586B standard instead of 586A. All our cabling here at work is done to the B standard and passes the PentaScanner tests fine.

 

[22Admub]

How do you check the interfaces for errors?

cmetz and skyking, I'll try those, thx. Zetter, first of all, everything I've read, suggests that both wiring standards are the same. especially for 100mbit and lower, when it comes to gigabit, then you have to make sure that all the stuff is the same. I'll wait for a couple more replies on this before I try that one.

skyking, I couldn't find qcheck on their site. is that for windows?
nm fount it thru google, http://www.ixiacom.com/enterprise/Qcheck.php,
sound like what I've been looking for, I'll give it a shot.

 

[ScottMac]

568A or 568B - No difference whatsoever, they are functionally equal.

568A also follows the color code for traditional telephony assignments.

If you have bad cabling, you'll (likely) get a lot of retransmissions: retransmissions = more traffic, longer delays (while the processes are waiting for the packet to be re-transmitted) .... it's a Bad Thing.

Qcheck is a great program, and it's free. It'll give you throughput, latency, and packet drop for a couple different protocols.

No PC-based program is going to give you a solid evaluation of the cabling - it's too limited by the NIC, OS, processor, etc. The best you can hope for is "It's looks good enough for me," which is all most home users need.

Good Luck

Scott

 

[mcveigh]

not to hijavk the thread, but does anyone know a somewhat inexpensive cable tester? I currnetly use a cheapo $50 one that basically tells me if it gets a signal on each wire. it works well, but I would like something bettter but say under $300...

is that too low to get something halfway decent?

 

[ScottMac]

For basic connectivity and location, I use a Fluke MicroScanner Pro.

It does pair-order, continuity, polarity, TDR, Tone Generation (for a toner probe), it'll blink the led of the connected port, and has "office locators" - you plug a module into an unidentified outlet (up to five of 'em) and it'll tell you which locator it sees on the other end of the cable.

I like it.

For Certification, I use my WaveTek or MS350 (only goes to Cat5, but with a few exceptions, my home network only goes to 100Meg anyway).

FWIW

Scott

 

[gunrunnerjohn]

Originally posted by: mcveigh
not to hijavk the thread, but does anyone know a somewhat inexpensive cable tester? I currnetly use a cheapo $50 one that basically tells me if it gets a signal on each wire. it works well, but I would like something bettter but say under $300... is that too low to get something halfway decent?

I use a cheap cable tester to check continuity, and then physically examine both ends to make sure the pairs are properly wired. It's served me well for years, and I don't have any significant cabling issue. I can't say the same for a number of the "professionals" that have wired clients before I arrived!