ICS cannot be enabled ... ICS out of physical NIC

[Febuary]

Hi all,

  I am trying to push the internet through a vm, well two, but this issue happens on one as well ... thru the vm(s) and out of the physical NIC using Internet Connection Sharing (ICS); which will then be connect to a switch.

  However, I get the following error message no matter what I try:

"Internet Connection Sharing cannot be enabled. A LAN connection is already configured with the IP address for automatic IP addressing."

Which box should I run cmd line tests on? The last one on the way out ... using the ICS from the virtual to the physical out or ...?

Here is the following for the last VM in line:

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\User>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : Win7Pro32bit-2
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Mixed
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : mshome.net

Ethernet adapter Local Area Connection 2:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection #
2
   Physical Address. . . . . . . . . : 00-0C-29-A9-35-6D
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::d0fa:9d8a:ca19:9711%20(Preferred)
   Autoconfiguration IPv4 Address. . : 169.254.151.17(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . :
   DHCPv6 IAID . . . . . . . . . . . : 335547433
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-17-7E-9F-0B-00-0C-29-A9-35-63

   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . : mshome.net
   Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
   Physical Address. . . . . . . . . : 00-0C-29-A9-35-63
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::98a4:19c3:256:aa09%11(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.137.108(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Friday, June 29, 2012 2:12:27 PM
   Lease Expires . . . . . . . . . . : Friday, July 06, 2012 2:47:26 PM
   Default Gateway . . . . . . . . . : fe80::fcdb:1f04:7e92:ffe%11
                                       192.168.137.1
   DHCP Server . . . . . . . . . . . : 192.168.137.1
   DHCPv6 IAID . . . . . . . . . . . : 234884137
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-17-7E-9F-0B-00-0C-29-A9-35-63

   DNS Servers . . . . . . . . . . . : 192.168.137.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.mshome.net:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : mshome.net
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 11:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:d3:2a14:3f57:7693(Prefer
red)
   Link-local IPv6 Address . . . . . : fe80::d3:2a14:3f57:7693%13(Preferred)
   Default Gateway . . . . . . . . . : ::
   NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter isatap.{2F7001E9-2D5E-4941-898C-0B2C5C1CEA4C}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

C:\Users\User>

[Febuary]

The router is set to 192.168.1.1

and here is ping -a 192.168.0.1:

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\User>ping -a 192.168.0.1

Pinging 192.168.0.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.0.1:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\User>

Febuary

[Febuary]

The vmnic0 is set to 192.168.1.1-192.168.1.1         the same as the router address used to auto set IPs ... correct?

is this a problem?

I tried to /release and /renew on the box going out and I no longer have internet access! Even after removing and readding the network adapters and restarting!

Any help,

Feb

[weinstein5]

Yes this could be the problem - remember each address needs to be unique on the network - to keep it simple please provide -

Physical router IP address

the number of NICs in the VM and their corresponding IP address, and gateway information

[Febuary]

Thanks weinstein5,

Router IP: 192.168.1.1

Connected Devices (to Router):

PC running vm client: 192.168.1.2

PowerEdge Server running ESXi 4.1: 192.168.1.3

roommates PC: 192.168.1.4

I am just going to connect one VM with one NIC in and another NIC out via ICS ... to keep it simple

so, there are just two nics and two vmnics

the vm connects to the router as : 192.168.1.5

vmnic0: 192.168.1.1-192.168.1.1

vmnic1: 169.254.17.226-169.254.17.226

now it lets me ICS without error

BUT

there was no internet access on the laptop I plugged the ICS cable into

SO

I pulled the cable and plugged it back into the laptop (from the server 2nd nic) and now I get

Another computer on the network has the same IP address as this Computer. ...

Default Gateway on vmnic0 (via ESXi server interface - ip configuration): 192.168.1.1

I dont know how to get any information for the nic1 / vmnic1

Local Area Connection on laptop using the ICS from the server vm:

Autoconfiguration IPv4 Address: 169.254.17.226

IPv4 Address: 192.168.137.1 (Duplicate)

I have seen this address before ... i think when I had the laptop ICSed into the server ... now the router goes into the server (or vice-versa)

And, on the ESXi server config manager ... Test Network Manager shows this address to ping

and the result is:

pinging address 1: 192.168.1.1           OK

pinging address 2: 192.168.137.1       Failed

Resolving Hostname                          Failed

I think you'll have this one figured out right away!

Febuary

[Febuary]

I think I figured this one out!

I got the current problem (with just on vm) solved! What some sleep does for ya, huh!

I realized that ICS turns the out-vm into a dhcp server and that address should be 192.168.137.1. And, since 192.168.1.1 is the routers dhcp server address and all connected to it have a pattern. I set the IPv4 IP addresses manually. I then set the DNS server address to the dhcp server previously in line. I found this by running the ipconfig /all cmd on the vm pushing to the laptop.

Now, back to setting this up the proper way with multiple VMs. I only have enough ram for 2 vms right now and want 3. But, once I prove that I can do what I need to do, I will buy plenty of ram for my enjoyment.

I will post the results after connecting back to 2 vms. This might give me the original error message again. But, I might be able to figure this out now ... with my new knowledge!

Febuary

[Febuary]

NOPE!! Couldn't fix it with multiple VMs.

Here are some details:

Router IP: 192.168.1.1

VM-1

Net IN

IP: 192.168.1.5

Gate: 192.168.1.1

DHCP: 192.168.1.1

DNS: 192.168.1.1

Line OUT - After Shared

IP: 192.168.137.1

Rest: code ... i think because this OUT becomes the gateway and servers ... as seen in VM-2 Line IN

====

VM-2

Line IN

IP: 192.168.137.228

Gate: 192.168.137.1

DHCP: 192.168.137.1

DNS: 192.168.137.1 & 192.168.1.1 (set manually)

Line OUT - Before Share / cant share

IP: 169.254.151.17

sub: 255.255.0.0

rest: coded

=====

Net works on the second VM, but I get the original error message when I try to share the VM-2 Line IN down the OUT. I think it wants to set the Line OUT IP to 192.168.137.1 to work as a DHCP/Gateway/DNS server.

Am I on the right track, guys?

What is the next jump in addressing for another DHCP/Gateway/DNS server in line ... and another one after that?

Thanks Much

Febuary

[Febuary]

I GOT IT!!!

I just had to change the default IP Address for ICS (from MS):

http://support.microsoft.com/kb/230148

Windows 7

To change the IP address that is assigned to the host and the IP address range that is used by the DHCP service on the Connection Sharing host, use Registry Editor to change the following values. These values are located in the following folder:
HKLM\System\CurrentControlSet\services\SharedAccess\Parameters

•(REG_SZ) ScopeAddress
•(REG_SZ) StandaloneDhcpAddress

The ScopeAddress value is set to the address range that you want to use with Connection Sharing. The StandaloneDhcpAddress value is the address range that is used when Virtual Wi-Fi/SoftAP is enabled. For both values, a network mask of 255.255.255.0 is used and is not configurable.

Walla

Febuary