I'm fairly new to this particular forum (although not to networking), but have noticed a LOT of initial posts omit some basic info that is essential to getting effective responses. It seems like it takes anywhere from 5-10 posts before we get enough info to really start making headway.
My first tip should help shorten the time it takes for the forum to resolve your problem. In short, include the following info (as applicable) in your initial posts:
* Your type of Internet connection and ISP
* Number of PCs
* OS on each PC
* NIC cards used (incl. manufacturer and model)
* Type of networking equipment used (hub, switch, router, bridge, etc., incl. manufacturer and model)
* Routing or firewall software in use; installed on which machines.
* CLEAR descriptions of how devices are currently connected.
* COMPLETE listing of configuration settings for applicable devices, software, or services (ex: Network Control Panel setting for t-shooting Windows networking services)
* Basic diagrams are VERY helpful, but not necessary.
As an additional tip, make sure your post does the following:
* States all the SPECIFIC functions and services desired in the network (ex: file & printer sharing, shared Internet access, etc.)
* Documents any error messages your receive, and lists in DETAIL erroneous functions on the network.
* Outlines ANY and ALL troubleshooting steps you have already completed to try to resolve this problem.
And one final tip:
Read The Manual...or the ReadMe.txt or at least search for info about the problem you are having on the manufacturer's web site. In just the last few days, I've counted no less than 15 different posts that were all answered (in plain English, no less) by existing documentation stored in Microsoft's TechNet Knowledgebase
EVERYONE, feel free to submit tips, which I will add to this initial post (with credit, of course). C'mon Spidey, Woodie, I know you have got a few in ya!
BTW: All these tips are SOP by my technical staff, to make sure that when we are trying to resolve a problem, we have eliminated as many possible variables and narrowed the scope through research BEFORE we try to test possible solutions or call manufacturer tech support (especially when the call costs $$$). In fact, all of my employees quake in fear at the only thing that truly pisses me off: Troubleshooting an error on a system that was outlined, explained, or resolved in a "ReadMe" or "Release Note" that somebody failed to read! GRRRRRR!
My first tip should help shorten the time it takes for the forum to resolve your problem. In short, include the following info (as applicable) in your initial posts:
* Your type of Internet connection and ISP
* Number of PCs
* OS on each PC
* NIC cards used (incl. manufacturer and model)
* Type of networking equipment used (hub, switch, router, bridge, etc., incl. manufacturer and model)
* Routing or firewall software in use; installed on which machines.
* CLEAR descriptions of how devices are currently connected.
* COMPLETE listing of configuration settings for applicable devices, software, or services (ex: Network Control Panel setting for t-shooting Windows networking services)
* Basic diagrams are VERY helpful, but not necessary.
As an additional tip, make sure your post does the following:
* States all the SPECIFIC functions and services desired in the network (ex: file & printer sharing, shared Internet access, etc.)
* Documents any error messages your receive, and lists in DETAIL erroneous functions on the network.
* Outlines ANY and ALL troubleshooting steps you have already completed to try to resolve this problem.
And one final tip:
Read The Manual...or the ReadMe.txt or at least search for info about the problem you are having on the manufacturer's web site. In just the last few days, I've counted no less than 15 different posts that were all answered (in plain English, no less) by existing documentation stored in Microsoft's TechNet Knowledgebase
EVERYONE, feel free to submit tips, which I will add to this initial post (with credit, of course). C'mon Spidey, Woodie, I know you have got a few in ya!
BTW: All these tips are SOP by my technical staff, to make sure that when we are trying to resolve a problem, we have eliminated as many possible variables and narrowed the scope through research BEFORE we try to test possible solutions or call manufacturer tech support (especially when the call costs $$$). In fact, all of my employees quake in fear at the only thing that truly pisses me off: Troubleshooting an error on a system that was outlined, explained, or resolved in a "ReadMe" or "Release Note" that somebody failed to read! GRRRRRR!
Facebook
Twitter