info america

info america, z-plate, zplate

Posts Tagged ‘Configuring Networking’

Configuring Networking

Posted by admin on June 4th, 2009

Configuring Networking

Now let’s configure networking for our server. First let’s run ipconfig /all and see the server’s current networking settings:

C:\Windows\System32>ipconfig /all
Windows IP Configuration
  Host Name . . . . . . . . . . . . : LH-3TBCQ4I1ONRA
  Primary Dns Suffix  . . . . . . . :
  Node Type . . . . . . . . . . . . : Hybrid
  IP Routing Enabled. . . . . . . . : No
  WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
  Connection-specific DNS Suffix  . :
  Description . . . . . . . . . . . : Intel 21140-Based PCI Fast Ethernet Adapter (Emulated) 

  Physical Address. . . . . . . . . : 00-03-FF-27-88-8C
  DHCP Enabled. . . . . . . . . . . : Yes
  Autoconfiguration Enabled . . . . : Yes
  Link-local IPv6 Address . . . . . : fe80::c25:d049:5b0c:1585%2(Preferred)
  Autoconfiguration IPv4 Address. . : 169.254.21.133(Preferred)
  Subnet Mask . . . . . . . . . . . : 255.255.0.0
  Default Gateway . . . . . . . . . :
  DHCPv6 IAID . . . . . . . . . . . : 67109887
  DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
  fec0:0:0:ffff::2%1
  fec0:0:0:ffff::3%1
  NetBIOS over Tcpip. . . . . . . . : Enabled 

Tunnel adapter Local Area Connection*: 

  Connection-specific DNS Suffix  . :
  Description . . . . . . . . . . . : isatap.{}
  Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
  DHCP Enabled. . . . . . . . . . . : No
  Autoconfiguration Enabled . . . . : Yes
  Link-local IPv6 Address . . . . . : fe80::5efe:169.254.21.133%3(Preferred)
  Default Gateway . . . . . . . . . :
  DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
  fec0:0:0:ffff::2%1
  fec0:0:0:ffff::3%1
  NetBIOS over Tcpip. . . . . . . . : Disabled

Note that ipconfig /all displays two network interfaces on the machine: a physical interface (NIC) and an ISATAP tunneling interface. Before we can use netsh.exe to modify network settings, we need to know which interface we need to configure. To determine this, we’ll use the netsh interface ipv4 show interfaces command as follows:

C:\Windows\System32>netsh interface ipv4 show interfaces

Idx	Met	MTU	State	Name
—–	—–	—–	——	—–
2	20	1500	connected	Local Area Connection
1	50	4294967295	connected	Loopback Pseudo-Interface 1

Open table as spreadsheet

From this, we can see that our physical interface Local Area Connection has index number 2 (first column). Let’s use this information to set the TCP/IP configuration for this interface. Here’s what we want the settings to be:

IP address: 172.16.11.162
Subnet mask: 255.255.255.0
Default gateway: 172.16.11.1
Primary DNS server: 172.16.11.161
Secondary DNS server: none

To do this, we can use two netsh.exe commands as follows:

C:\Windows\System32>netsh interface ipv4 set address name="2" source=static
address=172.16.11.162 mask=255.255.255.0 gateway=172.16.11.1 

C:\Windows\System32>netsh interface ipv4 add dnsserver name="2" address=
172.16.11.161 index=1

Now let’s run ipconfig /all again and check the result:

C:\Windows\System32>ipconfig /all
Windows IP Configuration
  Host Name . . . . . . . . . . . . : LH-3TBCQ4I1ONRA
  Primary Dns Suffix  . . . . . . . :
  Node Type . . . . . . . . . . . . : Hybrid
  IP Routing Enabled. . . . . . . . : No
  WINS Proxy Enabled. . . . . . . . : No 

Ethernet adapter Local Area Connection: 

  Connection-specific DNS Suffix  . :
  Description . . . . . . . . . . . : Intel 21140-Based PCI Fast Ethernet Adapter
(Emulated)
  Physical Address. . . . . . . . . : 00-03-FF-27-88-8C
  DHCP Enabled. . . . . . . . . . . : No
  Autoconfiguration Enabled . . . . : Yes
  Link-local IPv6 Address . . . . . : fe80::c25:d049:5b0c:1585%2(Preferred)  
  IPv4 Address. . . . . . . . . . . : 172.16.11.162(Preferred)
  Subnet Mask . . . . . . . . . . . : 255.255.255.0
  Default Gateway . . . . . . . . . : 172.16.11.1
  DNS Servers . . . . . . . . . . . : 172.16.11.161
  NetBIOS over Tcpip. . . . . . . . : Enabled 

Tunnel adapter Local Area Connection*: 

  Connection-specific DNS Suffix  . :
  Description . . . . . . . . . . . : isatap.{}
  Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
  DHCP Enabled. . . . . . . . . . . : No
  Autoconfiguration Enabled . . . . : Yes
  Link-local IPv6 Address . . . . . : fe80::5efe:172.16.11.162%3(Preferred)
  Default Gateway . . . . . . . . . :
  DNS Servers . . . . . . . . . . . : 172.16.11.161
  NetBIOS over Tcpip. . . . . . . . : Disabled

So far, so good. Let’s move on.

Changing the Server’s Name

Next let’s change the name of our server. When you install a Windows server core server manually from media, the server is assigned a randomly generated name. We want to change that, and we can use netdom.exe to do this. First let’s see what the current name is, and then let’s change it to DNSSRV because we’re planning on using this particular machine as a DNS server on our network:

C:\Windows\System32>hostname
LH-3TBCQ4I1ONRA 

C:\Windows\System32>netdom renamecomputer %computername% /NewName:DNSSRV
This operation will rename the computer LH-3TBCQ4I1ONRA
to DNSSRV. 

Certain services, such as the Certificate Authority, rely on a fixed machine name.
If any services of this type are running on LH-3TBCQ4I1ONRA,then a computer name
change would have an adverse impact. 

Do you want to proceed (Y or N)?
y

The computer needs to be restarted in order to complete the operation. 

The command completed successfully.

We can restart the server using the shutdown /r /t 0 command. Once the machine is restarted, typing hostname shows that the server’s name has been successfully changed: