Here is how I approach it at small shops where you have to be a jack of all trades:
1. Take each issue and document the exact problem, work on resolving it and document the fix [build a knowledge base.]
Building a knowledge base is so beneficial on saving time and justifying purchases as well as hiring additional resources (it also identifies where you spend the majority of your time.)
2. When you have to fly solo you are sometimes too involved with the current problem you sometimes forget to step back to see if there are other forces influencing the issue at hand. So step back and refer to other issues and give them some investigation and absolve them.
Remember you can get fried out too easily as being the only guy or 1 of 3 or 1 of 2. Take vacation time. Take time out for you. Do whatever, but your mental health is just as important as your skill sets when troubleshooting.
3. Your in charge of a lot more then you think, you have to remember that there are hundreds of responsibilities and thousands of tasks with running an IT Infrastructure and maintaining their systems. You do not work in a Large Corporate structure where you have a given scope of responsibilities and duties, where you report at 7, finish your day's routines by 11:14AM and spend the rest of the day meeting and philosophizing about what "Ideal IT" is.
Sometimes things are not going to be the result of another problem's having cascading effect --if at all. You may have your Exchange Server go down one minute and then an applet at a website your sales people always go won't work. Keep perspective: Start out with basic troubleshooting rather then looking at the least likely like the DMark.
4. Remember that this job really is more then just working with Computers, it is how you can balance in an ever changing environment (most of it in the control of your users hands, a tiny portion in your control and the remainder of control in the hands of outside entities --remember that when a virus pays you a visit or an upgrade turns in to a nightmare.)
Maintaining your cool and confidence in what got you to where you are today; being honest with your capabilities (remember IT is NOT about Ego it is about Computer Technology --NO ONE in this industry knows everything, NO ONE does, and those who claim they do are loose canons.)
Never be afraid to say to your Boss I do not know but I will find out --he hired you knowing your limitations and he expects you to grow, so take this chance and run.
5. Remember, the less resources or people there are to support a Network the more things will go wrong as the systems become neglected. Keep the Manpower Ratios (Server to Manpower, Users to Manpower, Maintenance to Manpower, and Workstations to Manpower) always in Mind. You always should be proud of what you accomplish even when you feel you are not doing much.
OK? That's the pep talk. Now lets trouble shoot your problems. Tell me about the DMark again:
A. What kind of hardware do you have? Give as much facts as you can.
B. What kind of DHCP is running (appliance or Software?)
C. Post good snapshots of the DMark on a page on a website and perhaps someone will be able to instantly see an issue.
D. What sort of maintenance have you done? If the hardware has fans are they clean and running --that sort of thing.
E. Have you tried configuring and swapping in/out new or similar hardware?
F. Do not be afraid to list your level of expertise with the hardware as someone may give you "advice" such as a good book or a beneficial course to help get you to where you need to be supporting your environment.
Consider joining a local HelpDesk Chapter -although they are geared to Helpdesks it is beneficial for Administrators like us to meet and Network with others [http://www.thinkhdi.com/]
List all of the variables and give your picture color with the make and model information because there are geeks out there that could tell you similar woes with a product or what they did to get things running.