You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running Windows Core Series, viewing the network routing table.
When running these commands or using them in scripts keep in mind that some may become deprecated in future versions of Windows. Best practice is to use the PowerShell commands, when possible, to future proof any script that use these commands. These commands were run on Windows Server 2012R2.
When running Windows Server 2012+ without a GUI note that the GUI can be reinstalled via PowerShell (Install-WindowsFeature) and a reboot.
Running Windows Core Series, viewing the network routing table.
When running these commands or using them in scripts keep in mind that some may become deprecated in future versions of Windows. Best practice is to use the PowerShell commands, when possible, to future proof any script that use these commands. These commands were run on Windows Server 2012R2.
When running Windows Server 2012+ without a GUI note that the GUI can be reinstalled via PowerShell (Install-WindowsFeature) and a reboot.
From Windows Server core command prompt:
C:>ROUTE PRINT
C:>Netstat -r
C:>POWERSHELL
PS C:>Get-Netroute
C:>POWERSHELL
PS C:>gwmi Win32_IP4RouteTable|Select Destination,Mask,NextHop,Metric1,InterfaceIndex|FT *
If you know any other interesting ways of getting this information from a Windows Server core installation post below.
The text was updated successfully, but these errors were encountered: