Teh Tech » Netsh http://tehtech.com Being an Admin is Hard Enough Wed, 14 Jul 2010 16:14:56 +0000 en hourly 1 http://wordpress.org/?v=3.1 Static and DHCP IP Address Changes Through Scripts http://tehtech.com/static-and-dhcp-ip-address-changes-through-scripts/ http://tehtech.com/static-and-dhcp-ip-address-changes-through-scripts/#comments Sun, 04 Apr 2010 02:54:23 +0000 admin http://tehtech.com/?p=251 I have a office that uses static IP addresses at the location. The manager just got a laptop that he wants to use at the office and at his house the same static address does not work. So I made him two batch files so he can easily switch between a static IP address in the office and a dynamic IP address at home. I was thinking that this could be helpful for making sure everyone in a office is using DHCP and no one is statically assigned. It could also be really useful for changing say the DNS server address on a set of computers automatically through a login script or kaseya.

It is a super simple script. The name of the network adaptor must be changed to match the name of the network adaptor you wish to modify settings for.

DHCP Through a batch/login script:

netsh int ip set address name = “Local Area Connection” source = dhcp
netsh int ip set dns name = “Local Area Connection” source = dhcp
netsh int ip set wins name = “Local Area Connection” source = dhcp

Static IP address through a batch/login script (change the red to match the addresses you need to set. IP is the IP address, SM is the subnet mask, gw is the default gateway, dns1 is the primary dns address, dns2 is the secondary dns address):

@ECHO OFF   

set ip=192.168.1.203
set sm=255.255.255.0
set gw=192.168.1.1
set dns1=4.2.2.2
set dns2=4.2.2.1

netsh int ip set address name = “Local Area Connection” source = static addr = %ip% mask = %sm%
netsh int ip set address name = “Local Area Connection” gateway = %gw% gwmetric = 1
netsh int ip set dns name = “Local Area Connection” source = static addr = %dns1%
netsh int ip add dns name = “Local Area Connection” addr = %dns2%
END

DHCP Set through Kaseya

Script Name: Enable DHCP
Script Description: Enables DHCP on the local area conection   

IF True
THEN
Execute Shell Command
Parameter 1 : netsh int ip set dns name = “Local Area Connection” source = dhcp
Parameter 2 : 1
OS Type : 0
Execute Shell Command
Parameter 1 : netsh int ip set address name = “Local Area Connection” source = dhcp
Parameter 2 : 1
OS Type : 0
Execute Shell Command
Parameter 1 : netsh int ip set wins name = “Local Area Connection” source = dhcp
Parameter 2 : 1
OS Type : 0
ELSE

You can also use this same pattern to set just one line. For example to use kaseya to quickly change the DNS server address on several computers you can use this. (note 4.2.2.2 is a open DNS server but change it to match what you need):

Script Name: Change DNS to Open DNS
Script Description: Sets DNS on Local Area connection to 4.2.2.2 

IF True
THEN
Execute Shell Command
Parameter 1 : netsh int ip set dns name = “Local Area Connection” source = static addr = 4.2.2.2
Parameter 2 : 1
OS Type : 0
ELSE

]]> http://tehtech.com/static-and-dhcp-ip-address-changes-through-scripts/feed/ 1 Change Windows Firewall From Command Line or Batch File http://tehtech.com/change-windows-firewall-from-command-line-or-batch-file/ http://tehtech.com/change-windows-firewall-from-command-line-or-batch-file/#comments Fri, 26 Mar 2010 00:01:24 +0000 admin http://tehtech.com/?p=212 I have a set of scripts I run when I prep a computer for deployment.  At specific points applications require that the windows firewall be turned off in order to install correctly.  This is namely ACT! and imagine time.  They use a bunch of odd ports during install, so their documentation tells you to just turn off the firewall. Well here is what I found with a little research.  From run or in a batch file there is a simple netsh command to disable the firewall and one to again enable it.

For imagine time my install script looks like this

netsh firewall set opmode disable
g:\Imagine_time\IT_SETUP.exe /q /p
netsh firewall set opmode enable

 
Effectively this will turn off the firewall, install the software silently from a share, and then enable the firewall again after install. I found something interesting with this in regards to kaseya too.  Sometimes VNC can’t get through the firewall because it has defaulted or something went wrong.  It turns out that if you run this as “system” you can actually disable the firewall remotely in many cases.  This has been a very helpful script for when a computer shows ‘connectable’ but it just times out when attempting connection.

Script Name: Win Firewall Off

Script Description: Turns off windows firewall

IF True 

THEN

   Execute Shell Command

     Parameter 1 : netsh firewall set opmode disable

     Parameter 2 : 1

         OS Type : 0

ELSE

Additionally,  if you change enable to disable in the above script, you can enable the firewall remotely through kaseya as well.

]]> http://tehtech.com/change-windows-firewall-from-command-line-or-batch-file/feed/ 0