Depricate an IP address

Say, a server has a number of IP addresses, but we don't want some addresses to be used as outbound.

ipconfig /all   gives us which address is preferred:

 Autoconfiguration Enabled . . . . : Yes
 IPv4 Address. . . . . . . . . . . : 2.68.18.2(Preferred)
 Subnet Mask . . . . . . . . . . . : 255.255.255.248
 IPv4 Address. . . . . . . . . . . : 2.68.18.3(Preferred)
 Subnet Mask . . . . . . . . . . . : 255.255.255.248

To make an address not preferred, remove it from the interface and recreate it again using the netsh:
 
interface ipv4 add address LAN 2.68.18.2 mask=255.255.255.248 preferredlifetime=0

Dynamic DNS

To prevent windows' DNS server from creating A records on all other interfaces the server might have (such as OpenVPN) to the dynamic DNS list, go to the DNS server's properties and exclude all the interfaces you don't need.

IIS IP binding

If IIS7 does not listen the incoming connections trying to be made to a particular IP address,
even if the binding is set up correctly, check the output of the following command:
netsh http show iplisten

The IP address must be in the list to respond the requests.

To add an IP, type in the following command:
netsh http add iplisten x.x.x.x

It seems, that data is stored in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\HTTP\Parameters

See http://support.microsoft.com/kb/954874 for more detail.

OpenVPN

After a while (some time of not using), the OpenVPN server broke down.
The secured connection istablishes, but IP does not go.

I guess, the problem in the IP routing. I don't know what I did, but after server rebooted, the connection start working.

The routing table on the server looks as below:

C:>route print 10.8*

IPv4 Route Table
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 ff 3d 7b 61 e5 ...... TAP-Win32 Adapter V8
0x10004 ...00 13 72 69 2d 0c ...... Broadcom BCM5708C NetXtreme II GigE (NDIS VBD Client)
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
10.8.0.0 255.255.255.252 10.8.0.1 10.8.0.1 30
10.8.0.0 255.255.255.0 10.8.0.2 10.8.0.1 1
10.8.0.1 255.255.255.255 127.0.0.1 127.0.0.1 30
Default Gateway: 10.0.0.1
===========================================================================
Persistent Routes:
None

There are still questions for me. Why routing to 10.8.0.0 via two gateways - 10.8.0.1 and 10.8.0.2 ?
10.8.0.1 - is the address of the TAP IP interface, but what is 10.8.0.2 then?
The address of the "modem pool"?

Same way, on the client the interface address 10.8.0.6, but 10.8.0.5 - P-t-P - what's that?

Good instructions about setting OpenVPN up are located here:
http://www.runpcrun.com/howtoopenvpn


And don't forget, when you want to connect a machine behind the server it has to have route to the 10.8.0.0 network as well.