think tank forum

I'm looking to build a ttf-approved kit.

What do you think is necessary for general computer and network troubleshooting in the way of tools?

Here's a quick list:
screwdriver set
cable tester
crimper
pci diagnostic card
voltage tester
receptacle tester (GFI/Outlet)
power supply tester
diagnostic software on cds/usb
external hdd for backups
sata/ide to usb adapter
usb to serial adapter
laptop
portable keyboard & mouse

Go!

tolteknician

LiveCD's:
o Ultimate BootCD (Get latest version, 5 beta)
o Memtest86+ -- It's included on the UBCD, but I find it useful anyway since I use it so often.
o Some sort of bootable Windows CD, BartPE, hiren's, etc. ERD is also useful because you can run system restore from it.
o Norton Ghost (Can be included w/ BartPE and hiren's), it's so much faster than dd on NTFS and FAT32.
o FreeBSD LiveFS with USB drive with some additional binaries. I just use the minimal LiveFS offered on the install CD. I also use jggimi's OpenBSD CD's sometimes: http://jggimi.homeip.net/livecd/downloads.html

I would also add an universal notebook PSU's. There are a alot of crap ones out there, the only one I like so far is the one by kensington.

> power supply tester

You mean a paperclip? (And a volt meter)

I thought this would be a software toolkit. :/

It can be software too. I'll put together my list.

man I don't have half of this shit. I just have screwdrivers and a billion screws and spare parts and if I swap out a part and shit works I throw out the old broken one and call it a day.

I. Don't. Have. A. Screwdriver.

It's sad, I know.

LiveCD's:
-Backtrack 3 Final
-Hiren's BootCD
-Ophcrack
-SystemRescueCD
-Ultimate BootCD

There are some crossover apps in many of the above, but the packages are each pretty nice :]

> You mean a paperclip? (And a volt meter)

hell no, I'll pass on getting zapped -- yes you can do it moderately safely but why risk it with an automated psu tester!

I'm going to show you all eventually the software on my USB stick, I'm trying to come up with a really slick setup! Share yours too!

pro tip: use a magnet for keeping track of screws.

live cds:
freebsd (i previously used freesbie--i don't know what is good these days)
windows a la bart pe
memtest86
gparted
secure erase (i previously used dban)

necessary computer tools:
screwdriver set
usb flash drive
extra computer with web access

handy computer tools:
sata/pata to usb adapter
hdd for backup
multi-meter

necessary networking tools:
rj-45 crimper
wire cutters

handy networking tools:
utp cable stripper
workgroup switch

bonus computer hardware:
screws
power cables
keyboard, mouse, monitor
atx power supply, at power supply
sata, pata, fdd, usb cables
molex power splitters, molex to sata power adapters
ps/2 to usb adapter
dvi to vga adapter
(can use this all to swap out defective hardware to determine the problem)

bonus network hardware:
rj-45
cat5(e)/6
mini wifi router

------------------------------------------------

my opinions on dp's list:

> screwdriver set

super useful.

> cable tester

i question the usefulness of this item. just bring a tiny switch. it can test a cable against your laptop, and it will help you in other situations as well.

> crimper

useful.

> pci diagnostic card

i question the usefulness of this item.

> voltage tester

useful.

> receptacle tester (GFI/Outlet)

i question the usefulness of this item. can you just use a multimeter?

> power supply tester

i question the usefulness of this item. can you just use a multimeter?

> diagnostic software on cds/usb

super useful.

> external hdd for backups

super useful.

> sata/ide to usb adapter

super useful.

> usb to serial adapter

i question the usefulness of this item. if this is useful, maybe a usb to parallel would be useful too.

> laptop

super useful to pull drivers, test network, backup hdds.

> portable keyboard & mouse

useful.

> cable tester
i question the usefulness of this item. just bring a tiny switch. it can test a cable against your laptop, and it will help you in other situations as well.
>>is there any decent way to see whether the point of failure is the cable? how about testing which is the correct terminating end? i think all you can do is see if the network begins to connect to a device on the other end, but you don't know if it's the cable exclusively. other solutions?

> pci diagnostic card
i question the usefulness of this item.
>>there is probably no better solution for a system that won't give you beep codes, it outputs an error code using a readout that lets you know what type of problem there is when the bios or several other things are unavailable to diagnose a problem

> receptacle tester (GFI/Outlet)
i question the usefulness of this item. can you just use a multimeter?
>>yep, toss it

> power supply tester
i question the usefulness of this item. can you just use a multimeter?
>>yep, toss it

> usb to serial adapter
i question the usefulness of this item. if this is useful, maybe a usb to parallel would be useful too.
>>i'd just be using it in conjunction with a null modem cable for configuring managed devices with console ports on them.

> is there any decent way to see whether the point of failure is the cable?

isn't that a decent way? if the cable is a straight-through, plug it from a switch post to a computer port or from a switch uplink port to a switch port. if the cable is cross-over, plug it from a switch port to another switch port. i think you can loop to the switch, and if the light comes on, then you're good. i could be wrong, though. (i'm not talking about the auto-negotiation light--just the connection light.)

> how about testing which is the correct terminating end?

what do you mean?

> i think all you can do is see if the network begins to connect to a device on the other end, but you don't know if it's the cable exclusively.

well if the devices work on a known-working cable, and you put in another cable and they don't work, then you know it is the cable exclusively. don't you?

> there is probably no better solution for a system that won't give you beep codes, it outputs an error code using a readout that lets you know what type of problem there is when the bios or several other things are unavailable to diagnose a problem

ok, cool. i'm glad i got my sister to buy this, then.

> i'd just be using it in conjunction with a null modem cable for configuring managed devices with console ports on them.

oh, ok. so:
laptop with serial port and usb port, or
laptop with usb port and usb-to-serial dongle

me> sata/pata to usb adapter

how about this instead:
sata, pata 2.5", and pata 3.5" to usb adapter (example)

also, screws are expensive ): (example)

>sata, pata 2.5", and pata 3.5" to usb adapter

yeah this is the type of adapter i was referring to. i got this from frys for $14: http://www.newegg.com/Product/Product.aspx?It … 6812232002

well if the devices work on a known-working cable, and you put in another cable and they don't work, then you know it is the cable exclusively. don't you?

this is kind of my attitude to most testing tools. I guess they'd be useful if you didn't have any spare parts though. usually I can guess 50/50 what the failing part is based on software behavior/issues and then just borrow a spare from somebody though.

>isn't that a decent way? if the cable is a straight-through, plug it from a switch post to a computer port or from a switch uplink port to a switch port. if the cable is cross-over, plug it from a switch port to another switch port. i think you can loop to the switch, and if the light comes on, then you're good. i could be wrong, though. (i'm not talking about the auto-negotiation light--just the connection light.)

yeah on short cables this is fine or single cables, but not in situations where you have many cables that you need to differentiate.
you also don't know what type of problem the cable has, whether just one pin is not crimped properly or any of that. sure you can see connectivity if the correct wires are good, but you aren't testing all wires.

> what do you mean?
in the case of multiple cables in one location and you're in another you can't identify which cable terminates where.

> this is kind of my attitude to most testing tools. I guess they'd be useful if you didn't have any spare parts though. usually I can guess 50/50 what the failing part is based on software behavior/issues and then just borrow a spare from somebody though.

if your only concern in testing is to see whether a short cable is good or bad, then sure this is reasonable, just replace the cable. but what if the cable is pretty long and in a wall? what if it's a crossover cable instead of straight through? how would you know what's going on?

on the lesser known list of tools...

taser - for when you absolutely have to have that part replaced and the jerk on the phone refuses to recognize it as in fact dead.

cell jammer - for when that other jerk on the phone won't let you do your job because he has all the time in the world to bother you.

I keep a portable butane soldering iron and accompanying wick / solder tube. Nice to have.

Livescribe plus notebook great.

Hands free phone kit... necessary as well. Type + holding phone = fail and a half.

NICE TO HAVE: Wimax / 3g data internet. Great when all you have is a busted up corp network available.

Business cards... always wanna be leaving em knowing how to get in contact with you down the line.

I will say, the hardware fix is always better to swap in a new part and keep going. Wasteful as it is, it's usually the most cost effective approach.. but it's more than infrequent that physical damage is done to exposed interfaces such as USB ports and such... simply wear and tear. Pulling out a soldering iron and fixing something that's out of warranty or cheap enough that voiding warranty isn't a concern will earn you mucho skill cred at low skill cost.

> not in situations where you have many cables that you need to differentiate.

there are cable testers that test multiple cables at once?

> you also don't know what type of problem the cable has, whether just one pin is not crimped properly or any of that.

well, you gotta redo the whole connector anyway. i would guess that you can tell which one is the problem by visual inspection.

> but you aren't testing all wires.

why do you need to test all of the wires if you aren't going to use all of the wires? just use a multimeter, then, if you really want to test it all thoroughly.

> in the case of multiple cables in one location and you're in another you can't identify which cable terminates where

wow, i never knew of such cable testers

> but what if the cable is pretty long and in a wall?

put a known-working device at each end.

> crossover cable instead of straight through?

use a computer and a switch's uplink port. or use two computers. or use two switches. or add another cross-over to make it straight-through again.

here's what i would do:

cable works?
 -> yes -> no problem! [exit]
 -> no  -> visually inspect it.
            -> found physical damage to connector(s)?
                -> no  -> assume cable is damaged. trash it. [exit]
                -> yes -> replace the connector(s). [go to beginning]

>> in the case of multiple cables in one location and you're in another you can't identify which cable terminates where

>wow, i never knew of such cable testers

i'd suggest a toner if you've got the cash.
http://www.lanshack.com/CableTracker-Network- … 67C67.aspx

toners are cheap pick one up you will always run into some asshole who labeled everything backwards

cable works?
 -> yes -> no problem! [exit]
 -> no  -> visually inspect it.
            -> found physical damage to connector(s)?
                -> no  -> assume cable is damaged. trash it. [exit]
                -> yes -> replace the connector(s). [go to beginning]

Sounds good but what about installed data drops that solution just doesn't work. If you are doing more then just a little network work a mid range tester will pay off. I had a problem a little bit ago where I was getting link lights but interface errors. Turns out the RJ45s I was using were bad.

> but you aren't testing all wires.
>>why do you need to test all of the wires if you aren't going to use all of the wires? just use a multimeter, then, if you really want to test it all thoroughly.

If I make a cable now I verify all wires. If I come back and put in Gigabit I don't want to be troubleshooting a new nic or device.

fair enough. i guess it would be useful, then.

isostick

That's a pretty good idea. Just today I had a retard machine *insisting* my USB drive was a ZIP drive and was unable to boot from it ...

looks useful, i wonder how gimmicky it is.

What do you mean?

well i've read it more carefully now, i think the way it was written made me get the sense that it might be.

so i'm guessing there's firmware that stores a driver that somehow loads itself and is detected by many standard BIOS?

the technical aspect isn't explained very clearly.

this would work well in conjunction with this software package I found a while ago for computer repair: SARDU