One way to look at the questions that are asked here is: how far away is the asker from even comprehending the answer?
Our favorite kinds of questions are the ones where the asker just needs a little bit of help getting over a tiny hill. "I need to do X. I tried Y and Z. Z almost worked, but I got X-purple. How do I get rid of the purple? I scoured the man page and found nothing."
It drives us crazy when questions show rather a lack of any kind of knowledge. "How can I get a server on the Internet? KTHXBYE!" In this case the asker has a huge MOUNTAIN of knowledge to get over before they can even BEGIN to solve their problem.
Don't answer a question if you don't feel like it. Not every question deserves an answer. On the other hand, if you think someone else might be happy to answer it, there's no reason to close it.
When in doubt, an answer deserves about the same amount of effort as the question got. If someone writes a one sentence question about "how to get a server onto the Internet," they deserve about a sentence answer, either linking to a checklist somewhere, or just tell them to hire a damn sysadmin. On the other hand, if they put a lot of effort into asking a very specific question, they deserve more effort for the answer.
The other day I saw a question on Stack Overflow which was basically "Can I make a forum using Python." The question didn't show very much effort, but it was an honest question. So I answered it: "Yes. Python is a general purpose language, so it can be used for just about anything, including making forums." This actually satisfied the asker. There was no need to go into a dissertation about how to do this... I'm not going to give someone an undergraduate education in programming just because they typed a question onto the site!
Most importantly, look for common patterns and write canonical, permanent answers. If people keep asking how to get a server onto the internet, make a simple, clear checklist, and point people to that. The checklist doesn't have to have detailed instructions. It could be something like (a) get a domain (b) get a dns server (c) open the firewall (d) run appropriate services. If people keep asking what 220.127.116.11/24 means, create a general purpose question with the title "How do I interpret an IP address of the form A.B.C.D/E?", answer that question concisely, and close everything as a dupe.
But before you close things, keep in mind:
Just because you're bored by a simple question, doesn't mean it doesn't belong here! Help prevent repetition by creating canonical question/answer pairs that can be used as duplicate targets, or leave the simple questions to the newbies. You don't have to answer everything.
If you're bored by Server Fault, that's OK. Take a month off. Take a year off. Find something you can do where you're actually learning, not repeating yourself endlessly.
There are basically two ways discussion groups can go. They can stick with the same people (who are learning and getting smarter) or they can stick with the same subject. If they stick with the same people, the only way to keep them entertained is to get more and more esoteric until you have a site where nobody can get useful information except the 14 old-timers who have been around since the beginning. This is nice for the 14 old-timers, but doesn't make the Internet a better place. If you stick with the same subject, eventually the old-timers get bored. That's a better outcome, I think. I think the old-timers would be better served by finding a new area to learn about that's challenging and interesting.