<div>
<div class="content wysiwyg-content">
My only DC /DNS server passes almost every test except the NetDiag /test:defGW. &nbsp;It comes back with failure stating no default gateway is found. &nbsp;The server can reach everywhere in building and reaches the internet so I'm not sure why I am receiving this. &nbsp;I do know, that pings to the internal interface of router/firewall (default gateway) fail from any and all machines. &nbsp;Does this test use ping? &nbsp;If not what could be going on and should I just ignore that test?<br />
---SM
</div>
</div>


My only DC /DNS server passes almost every test except the NetDiag /test:defGW.  It comes back with failure stating no default gateway is found.  The server can reach everywhere in building and reaches the internet so I'm not sure why I am receiving this.  I do know, that pings to the internal interface of router/firewall (default gateway) fail from any and all machines.  Does this test use ping?  If not what could be going on and should I just ignore that test?
---SM

netdiag-DefGW failure

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).

Windows Server 2003

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.