whats up with the network diagnostics ? sometimes its just better to
manually go to device manager and remove/add the device to get the bindings
working.

Anyone else seeing inconsistent behavior of netdiag and needing to do steps
as i described?

On Tue, 8 Jan 2008 07:40:30 -0800, "Paul Russell"
wrote:

whats up with the network diagnostics ? sometimes its just better to
manually go to device manager and remove/add the device to get the bindings
working.

Anyone else seeing inconsistent behavior of netdiag and needing to do steps
as i described?

Paul,

The problem with netdiag is that it diagnoses the protocols and transports used
by Windows Networking under Windows Vista. It doesn't diagnose hardware
problems, nor does it diagnose file sharing permissions problems.

Removing / adding a device, under Device Manager, may or may not work either.
One of the problems here is that folks report symptoms here, and other folks
advise them to try one fix or another, without any idea what the problems are.
http://nitecruzr.blogspot.com/2005/06/background-information-useful-in.html
http://nitecruzr.blogspot.com/2005/0...useful-in.html

Many problems can cause similar symptoms, and the symptoms, as reported by many
computer owners, don't tell the helpers what the problems are. Some folks here
have multiple problems, and they have to fix each problem one at a time.
http://nitecruzr.blogspot.com/2005/08/solving-network-problems-tutorial.html
http://nitecruzr.blogspot.com/2005/0...-tutorial.html

--
Cheers,
Chuck, MS-MVP 2005-2007 [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.

Not netdiag.exe ... was just referring network diagnostics in vista ..

I was asking if anyone else is seeing that the stuff in vista is not working
and people fall back on doing other rudimentary steps as I described
earlier.



"Chuck [MVP]" wrote in message
...
On Tue, 8 Jan 2008 07:40:30 -0800, "Paul Russell"
wrote:

whats up with the network diagnostics ? sometimes its just better to
manually go to device manager and remove/add the device to get the
bindings
working.

Anyone else seeing inconsistent behavior of netdiag and needing to do
steps
as i described?

Paul,

The problem with netdiag is that it diagnoses the protocols and transports
used
by Windows Networking under Windows Vista. It doesn't diagnose hardware
problems, nor does it diagnose file sharing permissions problems.

Removing / adding a device, under Device Manager, may or may not work
either.
One of the problems here is that folks report symptoms here, and other
folks
advise them to try one fix or another, without any idea what the problems
are.
http://nitecruzr.blogspot.com/2005/06/background-information-useful-in.html
http://nitecruzr.blogspot.com/2005/0...useful-in.html

Many problems can cause similar symptoms, and the symptoms, as reported by
many
computer owners, don't tell the helpers what the problems are. Some folks
here
have multiple problems, and they have to fix each problem one at a time.
http://nitecruzr.blogspot.com/2005/08/solving-network-problems-tutorial.html
http://nitecruzr.blogspot.com/2005/0...-tutorial.html

--
Cheers,
Chuck, MS-MVP 2005-2007 [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.

On Fri, 11 Jan 2008 05:49:12 -0800, "Paul Russell"
wrote:

"Chuck [MVP]" wrote in message
.. .
On Tue, 8 Jan 2008 07:40:30 -0800, "Paul Russell"
wrote:

whats up with the network diagnostics ? sometimes its just better to
manually go to device manager and remove/add the device to get the
bindings
working.

Anyone else seeing inconsistent behavior of netdiag and needing to do
steps
as i described?

Paul,

The problem with netdiag is that it diagnoses the protocols and transports
used
by Windows Networking under Windows Vista. It doesn't diagnose hardware
problems, nor does it diagnose file sharing permissions problems.

Removing / adding a device, under Device Manager, may or may not work
either.
One of the problems here is that folks report symptoms here, and other
folks
advise them to try one fix or another, without any idea what the problems
are.
http://nitecruzr.blogspot.com/2005/06/background-information-useful-in.html
http://nitecruzr.blogspot.com/2005/0...useful-in.html

Many problems can cause similar symptoms, and the symptoms, as reported by
many
computer owners, don't tell the helpers what the problems are. Some folks
here
have multiple problems, and they have to fix each problem one at a time.
http://nitecruzr.blogspot.com/2005/08/solving-network-problems-tutorial.html
http://nitecruzr.blogspot.com/2005/0...-tutorial.html

Not netdiag.exe ... was just referring network diagnostics in vista ..

I was asking if anyone else is seeing that the stuff in vista is not working
and people fall back on doing other rudimentary steps as I described
earlier.

Paul,

The network diagnostics in Windows Vista, while obviously lacking in several
ways, are way better than they were in Windows XP, and earlier. The biggest
shortcoming I see is that network problems often involve two (or three)
computers, not just one. Unfortunately, Windows Vista network diagnostics focus
on one client at a time, and have no way of involving others.

Need I point out the obvious - that if a computer could reliably run diagnostics
and query another client for additional diagnostics, there would be no need to
run diagnostics in the first place. And you can't automate diagnostics
involving the cKI, which frequently is the primary cause of network problems.

There will always be a need for rudimentary diagnostics. And I fear that, as
people get used to sophisticated diagnostics, they will loose the ability to
execute and interpret rudimentary diagnostics.

But your point is well made - Windows Vista is not mature yet, and until it is,
many networks will continue to rely upon Windows XP. And some will continue to
use Windows 98, Windows 2000, etc.

--
Cheers,
Chuck, MS-MVP 2005-2007 [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.