john pfeiffer
  • Home
  • Categories
  • Tags
  • Archives

netsh

I first learned about netsh as a fix for repairing a broken windows firewall - actually I was fixing a network connection: netsh firewall reset netsh winsock reset

netsh interface ip show config netsh -c interface dump > c:\netsh-output.txt //in context interface netsh -f filename.netsh netsh -r lab10 interface show interface //remote computer netsh -r 10.0.0.10 interface ip dump netsh interface ip set address "Local Area Connection" dhcp set dns "local" static 192.168.0.250 set wins "local" static 192.168.0.250

netsh interface ip set address name="local area connection" static 192.168.0.100 255.255.255.0 192.168.0.1 1

/ How to get MAC/IP address pairs from a domain / netsh dhcp server dump //show ip for dhcp server netsh dhcp server 10.0.0.6 show scope //shows scopes for this server netsh dhcp server 10.0.0.6 scope 10.0.0.0 show clients //shows clients for this server

use AD to get every authorized dhcp server in the domain?

netsh dhcp show server netsh routing ip relay

note: you could have a "script" file netsh pushd dhcp

aaaa //authetication,authorization, accounting, auditing (for IAS.mdb & RRAS) bridge dhcp diag interface
ipsec ras routing rpc wins

http://technet2.microsoft.com/windowsserver/en/library/61427fbd-de1f-4c8a-b613-321f7a3cca6a1033.mspx?mfr=true


  • « network security
  • MS SQL server 2005 report select statement switch case »

Published

Feb 6, 2010

Category

research

~178 words

Tags

  • netsh 1
  • research 199