Setup windows test client: Difference between revisions

From MyLVS
Jump to navigation Jump to search
Line 13: Line 13:
*Loopback IP Address: 192.168.2.220
*Loopback IP Address: 192.168.2.220
| valign="top" |  
| valign="top" |  
Overview<br>
Windows Setup in myLVS overview<br>
[[File:myLVS-HL-Windows.png|240px]]<br><br>
[[File:myLVS-HL-Windows.png|240px]]<br><br>
|}
|}

Revision as of 19:05, 10 July 2015




Main

Step by step installation and documentation for Windows (lots of screnn shots).

  • Goal: Adding a Windows test client to our myLVS environment

Requirements

  • Windows Server 2012 (using your own license key)
  • IIS installed
  • Computer name used: myLVS-Win-Client
  • IP Address: 192.168.2.221
  • Loopback IP Address: 192.168.2.220

Windows Setup in myLVS overview



Add a new loop back device

Click on Run
 


Enter mmc devmgmt.msc to open
the Device Manager



Right mouse click on your computer,
select Add legacy hardware


Confirm


Select the advanced option


Select Network adapters


  • Select Microsoft
  • Select Microsoft KM-Test



Confirm
 



Confirm again


Configure the new loop back device

Within Windows, goto the Network connections, with Server 2012 you can run and type ncpa.ctl


Rename the loopback adapter to loopback,
Rename the ethernet adapter to lan


Edit the properties of IPv4 of the loopback adapter
 



Enter the VIP (Virtual IP) = 192.168.2.220/24,
click Advanced
 


Disable Automatic metric,
make the adapter aware of the ARP issue
Enter a high byte number, like 254, click OK



Open an administrative console and enter:

netsh interface ipv4 set interface "lan" weakhostreceive=enabled
netsh interface ipv4 set interface "loopback" weakhostreceive=enabled
netsh interface ipv4 set interface "loopback" weakhostsend=enabled

See this for more information about those commands:



Testing the new loop back device

From the Windows host try to open the URL

From an Network client try to open the URL

The result should be the default IIS Webpage


Goto myLVS and enable the Windows host and


see the connection list: