alt.certification.a-plus - Good troubleshooting book?

Author

Good troubleshooting book?

Jason

2003-01-14, 10:23 am

I have my A+ so I have the basic theory and can answer the text book
questions.

But since I dont have access to multiple computers in multiple enviorments
with varying problems, i dont get much of a chance to do any live
troubleshooting.

Its an odd thing to complain about, but my computer never really has any
problems, unless i make the mistake of using the microsoft update, so i dont
get any real TSing experience on my own system. Plus that would be a majorly
narrow way to try and learn anyhow.

So are there any good (and recent) books out there that focus more on
troubleshooting rather than just theory?

smackedass

2003-01-14, 7:23 pm

As far as I know, there is no single comprehensive troubleshooting book.
Then again, I never have looked for one...

What you have to do is combine your own knowledge and experience with
continued reading, studying, classes, more hands-on experience, and on and
on. If you read the threads of this group, and others like it, over time
you will see that there is no single authority to show you everything, or
even close to it. If you can't set up your own lab, try to visit with
people who have created environments where there are different network
configurations, operating systems, etc.

I venture to say that the reason that you haven't gotten many responses to
your post is because, nobody can teach you what you have to take the
initiative to learn on your own, which is basically what you are looking
for. Troubleshooting, "theory", common practice, not-so-common practice,
standard procedure (huh?) are all a piece of the same ball of wax. You'll
be able to bounce questions off of the people who frequent this NG, and
others like it, there are more books available than you'll be able to read
in a lifetime, more Web sites than you'll be able to visit in your
lifetime...

Now, stop reading my lame writing and start reading something more
constructive!

smackedass

Jason wrote in message ...
>
>So are there any good (and recent) books out there that focus more on
>troubleshooting rather than just theory?
>
>
>

Tom MacIntyre

2003-01-14, 9:23 pm

On Wed, 15 Jan 2003 01:15:17 GMT, "smackedass"
<nospamkema@capecod.net> wrote:

>As far as I know, there is no single comprehensive troubleshooting book.
>Then again, I never have looked for one...
>
>What you have to do is combine your own knowledge and experience with
>continued reading, studying, classes, more hands-on experience, and on and
>on. If you read the threads of this group, and others like it, over time
>you will see that there is no single authority to show you everything, or
>even close to it. If you can't set up your own lab, try to visit with
>people who have created environments where there are different network
>configurations, operating systems, etc.
>
>I venture to say that the reason that you haven't gotten many responses to
>your post is because, nobody can teach you what you have to take the
>initiative to learn on your own, which is basically what you are looking
>for. Troubleshooting, "theory", common practice, not-so-common practice,
>standard procedure (huh?) are all a piece of the same ball of wax. You'll
>be able to bounce questions off of the people who frequent this NG, and
>others like it, there are more books available than you'll be able to read
>in a lifetime, more Web sites than you'll be able to visit in your
>lifetime...
>
>Now, stop reading my lame writing and start reading something more
>constructive!
>
>smackedass

Troubleshooting is also learned by doing...anyone can, not everyone is
as good to start with, and the tortoise CAN beat the hare...go for it!

Tom

>
>
>Jason wrote in message ...
>>
>>So are there any good (and recent) books out there that focus more on
>>troubleshooting rather than just theory?
>>
>>
>>
>

Jason

2003-01-15, 11:23 am

Of course i would love to have access to dozens of different systems and
actually work on them..that is my preference, as im sure it is of most
people...but i dont have access to that.
so whats the fallback? reading about it.

i do read this newgroup every day, and visit try to research problems posted
here myself, just so i can learn things.

I have found a few books thru Amazon and so forth, so its not like i couldnt
find the books themselves, i was more curious as to what books people felt
were better than others.

reading about PC TS'ing is limiting, and i fully realize that. But until im
in a position to physically work on multiple computers, its what i have to
settle for.

thanks for the input

"Tom MacIntyre" <tom__macintyre@hotmail.com> wrote in message
news

ri92vcn59dvkqd9a49rgbnp8
tftaj2um2@4ax.com...
> On Wed, 15 Jan 2003 01:15:17 GMT, "smackedass"
> <nospamkema@capecod.net> wrote:
>
> >As far as I know, there is no single comprehensive troubleshooting book.
> >Then again, I never have looked for one...
> >
> >What you have to do is combine your own knowledge and experience with
> >continued reading, studying, classes, more hands-on experience, and on
and
> >on. If you read the threads of this group, and others like it, over time
> >you will see that there is no single authority to show you everything, or
> >even close to it. If you can't set up your own lab, try to visit with
> >people who have created environments where there are different network
> >configurations, operating systems, etc.
> >
> >I venture to say that the reason that you haven't gotten many responses
to
> >your post is because, nobody can teach you what you have to take the
> >initiative to learn on your own, which is basically what you are looking
> >for. Troubleshooting, "theory", common practice, not-so-common practice,
> >standard procedure (huh?) are all a piece of the same ball of wax.
You'll
> >be able to bounce questions off of the people who frequent this NG, and
> >others like it, there are more books available than you'll be able to
read
> >in a lifetime, more Web sites than you'll be able to visit in your
> >lifetime...
> >
> >Now, stop reading my lame writing and start reading something more
> >constructive!
> >
> >smackedass
>
> Troubleshooting is also learned by doing...anyone can, not everyone is
> as good to start with, and the tortoise CAN beat the hare...go for it!
>
> Tom
>
> >
> >
> >Jason wrote in message ...
> >>
> >>So are there any good (and recent) books out there that focus more on
> >>troubleshooting rather than just theory?
> >>
> >>
> >>
> >
>

klassick

2003-01-24, 6:23 pm

Stick around Jason.. I screw up my system often enough to keep a dozen techs
busy.

"Jason" <jmcmsg1@rcn.com> wrote in message
news:b041t1$e84$1@bob.news.rcn.net...
> Of course i would love to have access to dozens of different systems and
> actually work on them..that is my preference, as im sure it is of most
> people...but i dont have access to that.
> so whats the fallback? reading about it.
>
> i do read this newgroup every day, and visit try to research problems
posted
> here myself, just so i can learn things.
>
> I have found a few books thru Amazon and so forth, so its not like i
couldnt
> find the books themselves, i was more curious as to what books people felt
> were better than others.
>
> reading about PC TS'ing is limiting, and i fully realize that. But until
im
> in a position to physically work on multiple computers, its what i have to
> settle for.
>
> thanks for the input
>
>
> "Tom MacIntyre" <tom__macintyre@hotmail.com> wrote in message
> news

ri92vcn59dvkqd9a49rgbnp8
tftaj2um2@4ax.com...
> > On Wed, 15 Jan 2003 01:15:17 GMT, "smackedass"
> > <nospamkema@capecod.net> wrote:
> >
> > >As far as I know, there is no single comprehensive troubleshooting
book. [colo
r=darkred]
> > >Then again, I never have looked for one...
> > >
> > >What you have to do is combine your own knowledge and experience with
> > >continued reading, studying, classes, more hands-on experience, and on
> and
> > >on. If you read the threads of this group, and others like it, over[/color]
time[
color=darkred]
> > >you will see that there is no single authority to show you everything,[/color]
or[co
lor=darkred]
> > >even close to it. If you can't set up your own lab, try to visit with
> > >people who have created environments where there are different network
> > >configurations, operating systems, etc.
> > >
> > >I venture to say that the reason that you haven't gotten many responses
> to

> > >your post is because, nobody can teach you what you have to take the
> > >initiative to learn on your own, which is basically what you are lookin[/color]
g[col
or=darkred]
> > >for. Troubleshooting, "theory", common practice, not-so-common[/color]
practice,
> > >standard procedure (huh?) are all a piece of the same ball of wax.
> You'll
> > >be able to bounce questions off of the people who frequent this NG, and
> > >others like it, there are more books available than you'll be able to
> read
> > >in a lifetime, more Web sites than you'll be able to visit in your
> > >lifetime...
> > >
> > >Now, stop reading my lame writing and start reading something more
> > >constructive!
> > >
> > >smackedass
> >
> > Troubleshooting is also learned by doing...anyone can, not everyone is
> > as good to start with, and the tortoise CAN beat the hare...go for it!
> >
> > Tom
> >
> > >
> > >
> > >Jason wrote in message ...
> > >>
> > >>So are there any good (and recent) books out there that focus more on
> > >>troubleshooting rather than just theory?
> > >>
> > >>
> > >>
> > >
> >
>
>

Sponsored Links