Finding the cause of the problem

Since implementing the Cisco NAC, I’ve had a few fun calls that could have been avoided with a little more troubleshooting. The calls always start with, “Hey, we’re having some NAC issues here.” and go down hill from there. Here are a few issues initially blamed on the NAC with the true cause of the issue in parentheses.

User shared drives are not mapping at login. (Network cable was unplugged. User was being authenticated with cached credentials.)
No one can log on to the domain when using X computer in Y room. (There was no computer account on the domain. Joined the computer to the domain and logins started working.)
User cannot log on, no matter what computer they try. (User account had been disabled due to administrative request.)
Clicking noise when computer is turned on. (Seriously? A technician actually asked if the recent agent install had caused the issue. A cookie to the correct answer in the comments.)
A projector connected to the computer did not show the shared screen. (It helps if the projector is actually turned on.)

There are a few more in the ever growing compilation list to be posted later. I get at least two calls a weeks that are very face-palm worthy. I’m thinking about setting up a wall-o’-shame at work. Let the guilty party step forth.

Sometimes it’s more important to be human, than to have good taste. – Brecht

09.Dec.08 Humor, Networking, Security

You can follow any responses to this entry through the RSS 2.0 feed.
You can leave a response, or trackback from your own site.

2 Responses to “Finding the cause of the problem”

gb | December 9th, 2008 at 7:51 pm
Clicking noise = HDD?
wyckedone | December 17th, 2008 at 5:02 pm
gb wins! The system this was happening to would start clicking…LOUDLY…as soon as it was turned on. How the tech thought it was even possible the agent could have caused the issue is beyond me.