What to use on Windows Server 2008 since NETDIAG isn't supported?
Seems like the relevant tests that were part of netdiag were moved to other diagnostics components. I know dcdiag does a set of DNS tests specific to necessary functionality on domain controllers. Other tools like ping, nslookup, ipconfig, etc. may help with the other things netdiag did in its all encompassing diagnostics check.
We had some DNS issues recently, and were able to resolve them by simply using dcdiag and the other commands mentioned above.
Related videos on Youtube
03 : 02
02 : 27
02 : 59
12 : 15
07 : 59
SqlRyan
My name is Ryan McCauley, and I'm a database/reporting manager for a mid-size cable company. I spent a number of years as a .NET developer (mostly of the VB.NET variety), but now largely focus on T-SQL and the reporting with the Microsoft BI stack. On my own time, I build small apps to help get things done a little better, and have a couple posted at Codeplex: SQL Space Map - if you have some large SQL Server databases and you'd like a visual picture of which tables and indexes are taking up that space, it's the tool for you. SQL Server Contention Monitor - watches as may SQL Servers as you want and alerts you to blocked SPIDs, showing you the block tree (which process is blocking which, an what others are affected). It's still in a pretty alpha-ish phase, but it despite some instability at times, it gets the job done. Check them out and let me know what feedback you have!
Updated on September 17, 2022Comments
-
SqlRyan over 1 year
I need to troubleshoot some DNS issues on a Windows 2008 domain controller, but I see that NETDIAG isn't supplied or supported anymore. I could just copy it from a Server 2003 DC, but it looks like the output wouldn't be reliable. Everywhere I look online, people quickly say "It's not supported anymore" without giving a replacement for the functionality.
What can I use to do the same type of DNS/network diagnostics since I can't use NETDIAG?