netsh

I am looking for some good windows troubleshooting tools, and started messing around with the

netsh

command - as i am playing with this, I got the impression that this might be a good way to look into networking problems.
if this is a good assumption, what are the best netsh commands to use when looking into networking problems?
LVL 1
JeffBeallAsked:
Who is Participating?
 
duncanb7Commented:
take a look at this
http://technet.microsoft.com/en-us/library/cc725935(v=ws.10).aspx

And could you write us what the networking problem you have now ?

Dunan
0
 
JeffBeallAuthor Commented:
"And could you write us what the networking problem you have now ?"

I'm not having problems. I just want to build an arsenal of tools when I do have problems.
so i was wondering if people have used the netsh command, and what they have found to be the most useful.
0
 
QlemoBatchelor, Developer and EE Topic AdvisorCommented:
Nope, netsh is no good for diagnostics or troubleshooting. Too many bugs, syntax changing with each OS, and such.
Network issues are so diverse it is impossible to name any tool being able to help in most of them. E.g. often you'll need a network capture - WireShark, MS NetMon or MS Message Analyzer are good stuff here, but you need to know "something" (in the sense of "second to all") about the networking protocols involved.
Of course you'll need IPConfig, route print in addition, but that is built-in.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
JeffBeallAuthor Commented:
ok, but that is kind of what i was looking for. because i learned that netsh wouldn't be a good tool, but for example, i haven't heard of ms netmon. so i could look at that.
i have used ipconfig a lot. but i like to have a few different tools. for example, if i have 3 tools, and for some reason, tool number 1 doesn't work, i can switch to tool number 2.
0
 
QlemoBatchelor, Developer and EE Topic AdvisorCommented:
It is always a good idea to have another tool able to show similar or same info. But netsh syntax is too complex to be able to remember the proper commands if you need them.
Well, the built-in tools should always work, else you are in trouble anyway.
0
 
JeffBeallAuthor Commented:
so i started playing with netmon, is this like wireshark?
0
 
McKnifeCommented:
Jeff, diagnosing network problems does not really work like that. There is no tool you start and see "ah, that's it". To find the problem, first step is to identify the ISO/OSI-Layer and to rule out physical defects. After having ruled that out, in the majority of cases, it will be faulty or misconfigured software, mostly security software (AV scanners, software firewalls, hardware firewalls as well). Also quite often: old or faulty drivers.

Sure, I use ipconfig from time to time, and I am familiar with netsh, but I would never recommend to learn netsh for troubleshooting, it's simply too rare that it would amount to anything.
0
 
JeffBeallAuthor Commented:
I didn't intend for it to sound like i thought there was a tool that would find everything i might run into.
I mostly use, ping, then ipconfig
and they for the most part, give me a picture of what is happening. My goal was to see if there were other tools that i'm not familiar with that i could add to my "toolbox", like I mentioned earlier

"i learned that netsh wouldn't be a good tool, but for example, i haven't heard of ms netmon. so i could look at that."

so I might have found another helpful tool in ms netmon.
0
 
QlemoBatchelor, Developer and EE Topic AdvisorCommented:
NetMon is the predecessor of Message Analyzer, and like WireShark,

I agree to what McKnife wrote. Having a set of tools like a screwdriver and a hammer is good, but not worth much without some deep insight into the mechanics, and sophisticated knowledge of diagnostic methods.
0
 
McKnifeCommented:
:) Sure, understood.
There are some that one has to know:
telnet.exe, nslookup.exe, Portqry.exe, portping.exe instantly come to my mind. The latter from here: http://www.tkolb.de/portping-13-36.html , the othes built-in/Microsoft.
0
 
JeffBeallAuthor Commented:
Thank you!
I forgot to mention nslookup, but i am also not familiar with portqry
also, I agree

"Having a set of tools like a screwdriver and a hammer is good, but not worth much without some deep insight into the mechanics, and sophisticated knowledge of diagnostic methods"

what I do is, for something like nslookup, yesterday I was googling best practice using nslookup and that led to DNS. So not only do I learn about nslookup, but also about DNS. So I will just do the same for portqry, and probably discover new insights into how windows uses ports.
0
 
JeffBeallAuthor Commented:
thank you for the help
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.