After entering the DIAG context, the GUI command opens a IE browser window and scans the local computer and network. Expanding the Network Adapters node show a number of useful checks such as wether the Default IP Gateway and DNS Server can be pinged and what the response time was.
This looks like a nice addition to my toolbox. Anybody using it much now?
Discussion on:
View:
Show:
I believe I will be playing around with this to see what all it is capable of doing. YES!! the GUI in the Diag portion is very nice .. found it very interesting.
One quick comment about the gui. If you just type "netsh diag gui" in the Run dialog box it will open the gui only.
Hope this helps some.
Hope this helps some.
All I get is a WMI error.
The only thing it IDs is Outlook Express.
A typical Windows product-It doesn't work.
The only thing it IDs is Outlook Express.
A typical Windows product-It doesn't work.
I would like to see more command line tips and tricks for troubleshooting problems.
Thanks,
Dan
Thanks,
Dan
when you are at the netsh diag command line type gui and you will get a nice tool that you can use. It is so easy to use that I don't even have to explain how to use it.
You can also get to the GUI interface in WinXP by selecting "Help and Support" on the Start menu. Under "Pick A Task," choose "Use Tools to view your computer information and diagnose problems" and select "Network Diagnostics" from the list of tools. You can also find a handy command line reference list in the list of tools.
Windows XP networking is a challenge.
I have followed every instruction I can find anywhere and still have the traditional problem that computer A cannot 'see' computer B on the network, nor vice versa.
Any help to resolve much appreciated.
TAG
I have followed every instruction I can find anywhere and still have the traditional problem that computer A cannot 'see' computer B on the network, nor vice versa.
Any help to resolve much appreciated.
TAG
Are you using XP on both PCs? If one is '98 you will have to add in NETBEUI protocol to both, but helps if both are XP also(see Microsoft KB for adding Netbeui to XP).
Hope it helps!
Hope it helps!
If you're tried all of the usual diagnostic tricks (checking ip addresses, workgroup / domain names, protocols etc.), you might still be hung up by a firewall. I've had Zone Alarm trip me up a few times because I usually set the program permissions and then forget about network connectivity when ZA is on its High security setting. Check the firewall settings on both computers to see if either of them are set too high. In Zone Alarm, you would want to keep the High security setting for your Internet connection, but specify specific IP addresses on your LAN as Trusted computers which will use the Medium security settings.
Are both computers in the same workgroup? If not, you may need to rename the one you prefer to the same workgroup. Also, check your firewall settings - if you're using NIS you may need to allow it & also make sure you have shared folder permissions set on both to reflect the same. One other thing, do both have SP2? If not, you may want to install it to eliminate future problems. A final tip, use a program called "Registry First Aid", just do a search for it - I believe the company that has it is Rosecity Software & run it on the one machine (or both) that may be giving you (or has been giving you) problems in the past. It's a very useful tool & can correct a lot of problems you're experiencing & make things work right.
Although NetBEUI is not natively supported in Windows XP, you can add it manually from the Valueadd directory on the XP installation CD-ROM.
Remember, NetBEUI is not routable -- can't use it on networks that use routers and can't use it to connect to the Internet.
Remember, NetBEUI is not routable -- can't use it on networks that use routers and can't use it to connect to the Internet.
I have identifed a problem with Windows XP (SP2) using the internal firewall. The symptoms are that you cannot browse the workgroup. You get access denied or some such.
The reason is that the first machine on the network becomes the master NETBIOS broswer but it cannot see (blocked by the firewall) its own broadcast addresses. The firewall log together with Ethereal showed the behaviour.
The cure is to go to the firewall settings and change the scope for the four ports for file/printer sharing from Own Network to custom and enter your own network address e.g. 192.168.1.0/255.255.255.0
If you have a thrird party firewall that diables the Windows XP firewall then you don't see this behaviour.
The reason is that the first machine on the network becomes the master NETBIOS broswer but it cannot see (blocked by the firewall) its own broadcast addresses. The firewall log together with Ethereal showed the behaviour.
The cure is to go to the firewall settings and change the scope for the four ports for file/printer sharing from Own Network to custom and enter your own network address e.g. 192.168.1.0/255.255.255.0
If you have a thrird party firewall that diables the Windows XP firewall then you don't see this behaviour.
Windows XP networking is a challenge.
I have followed every instruction I can find anywhere and still have the traditional problem that computer A cannot 'see' computer B on the network, nor vice versa.
Any help to resolve much appreciated.
TAG
I have followed every instruction I can find anywhere and still have the traditional problem that computer A cannot 'see' computer B on the network, nor vice versa.
Any help to resolve much appreciated.
TAG
I have done this at home, and it is working (usually).
Fire an email to me at eghorst @ cableregina.com (no blanks), putting "TechRepublic Help" in the title so I know it is not spam. I have 1 pc with XP and 1 with 98SE and they can see each other.
Ed
Fire an email to me at eghorst @ cableregina.com (no blanks), putting "TechRepublic Help" in the title so I know it is not spam. I have 1 pc with XP and 1 with 98SE and they can see each other.
Ed
Shoot me off an email with a description of your setup and I am sure I can help you out. I do remote network support for a living and many times even for small, home networks. scott
headgamez.org
//email edited to deflect spam
-Scott
//email edited to deflect spam
-Scott
I work in a area that used to use just ping or tracert this command is just the tool we needed, to help us in our daily tasks.
- Keyboard Shortcuts:
- Prev
- Next
- Toggle









































