I am posting this in order to help those of you with some additional things you may not know about.
When troubleshooting a problem:
Step 1: Look at This would be the best place to start to see if there is a posted solution to the given problem.
Step 2: Is it a software issue, ie Arcserve, McAfee or Norton, Check the particular vendors website, this should give you information as to wether or not the problem has been identified and a possible solution.
Step 3: In any of the two seraches above, be creative in your search criteria. Sometimes the specific problem may require you to perform the search using different keywords or arranging the keywords into a different pattern.
Step 4: When posting a problem on the forum, try to be as detailed as you can. Explain or describe the problem to the best of your ability, and some basic configuration information, including software and levels of patches.
Step 5: Correspond with the person who has provided the solution or additonal questions in helping to narrow your issue. (There was an individual who had a NW 3.X server running and after reviewing the Autoexec.ncf, I recognized a line and lo and behold, it was a server that was forgottten about
Step 6: Be patient, there are a handful of professionals that post responses to problems, and we can't be here all the time, but the longest I have seen a post take is about 72 hours. If the problem is off the wall, it may takea bit longer.
Have fun and Enjoy
Mark C. Greenwood, CNE
m_jgreenwood@yahoo.com
CNE 4.11 and CNE 5 certified. BS Degree in MIS. Working in the industry for 8 years.
I work with NT servers, NDS for NT as well.
When troubleshooting a problem:
Step 1: Look at This would be the best place to start to see if there is a posted solution to the given problem.
Step 2: Is it a software issue, ie Arcserve, McAfee or Norton, Check the particular vendors website, this should give you information as to wether or not the problem has been identified and a possible solution.
Step 3: In any of the two seraches above, be creative in your search criteria. Sometimes the specific problem may require you to perform the search using different keywords or arranging the keywords into a different pattern.
Step 4: When posting a problem on the forum, try to be as detailed as you can. Explain or describe the problem to the best of your ability, and some basic configuration information, including software and levels of patches.
Step 5: Correspond with the person who has provided the solution or additonal questions in helping to narrow your issue. (There was an individual who had a NW 3.X server running and after reviewing the Autoexec.ncf, I recognized a line and lo and behold, it was a server that was forgottten about
Step 6: Be patient, there are a handful of professionals that post responses to problems, and we can't be here all the time, but the longest I have seen a post take is about 72 hours. If the problem is off the wall, it may takea bit longer.
Have fun and Enjoy
Mark C. Greenwood, CNE
m_jgreenwood@yahoo.com
CNE 4.11 and CNE 5 certified. BS Degree in MIS. Working in the industry for 8 years.
I work with NT servers, NDS for NT as well.