Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

ive got this situation: Operator pickups phone in helpdesk. By CallerID he gets users contract number and can see personal details. Main question from user is "I dont have internet connection or i cant view web-sites"

Main Page:

  1. MAC
  2. IP
  3. Ping results (his and neighbourhoods)
  4. Type of connection (raidolink/LAN/WiFi)
  5. Account Ballance (+10$/-2$/Disconnected)
  6. First/Last/Middle Name, Contact Phone
  7. CallerID

Second Page:

  1. List of calls before

What else shoud operator know to determine whats problem user has (or if there any problems with conenction to that user) without asking any questions to user?

And what common questions for user are? Like any router/computer is powered on/ etc.


locked by HopelessN00b Jan 21 '15 at 3:28

This question exists because it has historical significance, but it is not considered a good, on-topic question for this site, so please do not use it as evidence that you can ask similar questions here. This question and its answers are frozen and cannot be changed. More info: help center.

closed as primarily opinion-based by HopelessN00b Jan 21 '15 at 3:27

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise.If this question can be reworded to fit the rules in the help center, please edit the question.

up vote 1 down vote accepted

On the first page:

  • Any currently outstanding incident tickets for that user.
  • Any known problems that may be affecting that user.
  • Any user "flags" - common account statuses that might be relevant to the account handler in dealing with the customer
Ok, and what else should know operator about network - status? – MealstroM Jun 7 '11 at 11:03
Ah, sorry, "known problems" is a technical term from ITIL, which is (among other things) a service desk/helpdesk management methodology. Known problems would include relevant network status. – RobM Dec 29 '11 at 11:16

Well, some link error statistics have proven to be useful for troubleshooting, but to really know what the user's problem is, this would surely be the most valuable tool:

soothsayer with glass ball

You would need to provide more details on the typical problem range the helpdesk operators are meant to solve in order to get meaningful answers, as only few people here will capable of telepathy or soothsaying.

Ive edited my question, it is now more specific now. – MealstroM Jun 7 '11 at 9:00
Well the answer is still "it depends". Do you have your own infrastructure or do you just authenticate dialins and provide IP connectivity? Do you rent out modems or routers that are under your control? You would need a concise list of problems that your helpdesk should be able to solve - then you can derive questionnaires and resolution steps from there on. If your helpdesk should also be able to troubleshoot things, there is no sense in forbidding questions - if no questions were needed, you would be able to see and resolve a problem before a user calls in in the first place. – the-wabbit Jun 7 '11 at 11:52
it is a lot of trouble to monitore all users. we can monitore some valuable nods. All network equipments is ours. We've already have Nagios system. – MealstroM Jun 7 '11 at 11:59

Not the answer you're looking for? Browse other questions tagged or ask your own question.