Recently I built an NPS server for Radius authentication, and had to dual home it with one NIC in the DMZ and one on the production network. I wanted to firewall everything on the DMZ interface but not affect the production interface. That way I could then allow the traffic I wanted to enable on…
This simple Powershell script will carry out a quick check against each IP in a 24 bit subnet and return a value of true or false dependent on whether or not it receives a reply. It’s similar to using an IP scanner or a ping script.
|
1 2 |
[cc lang="powershell"]$subnet = "10.20.6." 1..254 | Foreach-Object {write-host "$Subnet$_…" (Test-Connection -ComputerName "$Subnet$_" -Quiet -Count 1 ) }[/cc] |
It’s simple and does the job as it…
I recently used this on a Hyper-V build. It should provide enough network connectivity to add your server to the Active Directory domain. Find connected NICs and interface names
|
1 |
[cc lang="powershell"]Get-NetAdapter[/cc] |
Configure IP address
|
1 |
[cc lang="powershell"]New-NetIPAddress -InterfaceAlias "NIC1" -IPAddress 10.20.0.141 -AddressFamily IPv4 -PrefixLength 24 -DefaultGateway 10.20.0.1[/cc] |
Configure DNS Servers
|
1 |
[cc lang="powershell"]Set-DnsClientServerAddress -InterfaceAlias "NIC1" -ServerAddresses 10.20.0.133[/cc] |
Configure the suffix search list
|
1 |
[cc lang="powershell"]Set-DnsClientGlobalSetting -SuffixSearchList corp.contoso.com[/cc] |