By: s@m

s@m — Thu, 28 Jan 2010 04:42:10 +0000

THIRION gracias por la contribución, me ha sacado de aprietos.

By: lijo

lijo — Mon, 07 Dec 2009 05:39:19 +0000

can u please help me with ICS configuring for CentOS in Vmware with win7 as my operating system

By: from italy

from italy — Sun, 08 Nov 2009 18:19:45 +0000

It worked, thanks!

By: Somewhere in Asia

Somewhere in Asia — Sun, 01 Nov 2009 19:12:15 +0000

It really helped! I really appreciate you.
I’m using Win7 and Fedora10.
It’s working with Bridged but others.

By: Rajeev Borborah

Rajeev Borborah — Mon, 26 Oct 2009 07:46:37 +0000

Works excellent step by step information

Thanks
Raj

By: Tearsfall

Tearsfall — Sun, 25 Oct 2009 15:08:46 +0000

Windows7 Internet Connection Sharing (ICS) with Ubuntu 9.04 box

Here’s how I did it. Easy steps… 1 – 2 – 3 – 4….

The equipment and platforms:

Dell Dimension 8300 desktop running Win7 and using a USB N-band WLAN adapter as the connection to the internet (the N-band WLAN router is at

the other end of the house and diagonally downstairs). A 5-port networking switch connects the Dell’s 10/100 LAN card via standard CAT5 cables to a homebuilt AMD desktop running Ubuntu 9.04, freshly installed and yet to be updated. Had I not had an available switch sitting around, I would have used a cross-over CAT5 LAN cable – it should provide the same experience as the switch as long as one is only using two systems.

DSL Modem N-Band Router ))) ((( USB WLAN adapter Dell Desktop switch AMD Desktop

Essential Preparations:

The Dell’s WLAN connection was established and verified working and able to browse the internet.

Both the WIN7 and the Linux box have identical “name and password” accounts and are running using those same accounts. Convenience over security has both machines automatically defaulting to the desktop of that account at boot.

The LAN cards on both boxes are lit and seeing the connection between the units. The lights on the switch confirm the network handshake.

ALL connections are set to be automatically assigned an IP and DNS… except for the one exception listed below, and only then if auto mode doesn’t work.

The Necessary Steps:

1) In the system tray of the Dell, I left-clicked the networking icon (right-click would work too). I chose “OPEN NETWORK AND SHARING CENTER” from the bottom of the popup.

2) Under “View Your Active Networks” and to the right of “Connections” (the first one in my case), I left-clicked on “WIRELESS NETWORK CONNECTION”, then chose the “PROPERTIES” button at the bottom of the popup.

3) I chose the “SHARING” tab, then put a check in the first of the two available boxes – that enables ICS. I clicked “OK” on the popup that tells me that it will automatically assign an address of 192.168.137.1 to the LAN connection. I then click “OK” at the bottom of the “SHARING” page. This will bring you back to the NETWORK AND SHARING CENTER where you should see the Wireless and the Local Area connections showing “INTERNET” as each one’s Access Type (it sometimes is delayed a few seconds). If not, try repeating step 2, deselecting the check box and again clicking “OK”, then repeating steps 2 and 3. If it proves stubborn, reboot and try steps 1 through 3 again.

4) Final step: I then turned to the Linux box, opened the Network icon, and left-clicked on its “auto eth0″ connection icon to force it to recognize the new connection. Once reconnected, I could browse the internet and perform updates.

If this still doesn’t work, try turning off any and all virusscan and firewall and anti-spyware software running in the system tray and try again. Your router should provide enough firewall protection until you figure it out. Just FYI, I use the standard WIN7 firewall, AVAST AV, and no anti-spyware program that runs in the background, and needed to turn off nothing for this to work.

If this still isn’t working, check the assigned IP address of the Linux LAN card… it has to be 192.168.137.xxx something – where xxx is NOT equal to “1″. If it is not, try manually assigning a static IP address in that format, and make xxx something between 2-254, subnet 255.255.255.0, default route AND primary DNS 192.168.137.1 each. Then attempt to activate ICS again using steps 1 through 3. This is the “one exception” where automatically assigning IP and DNS may not function correctly – but did in my case.

Be aware and BEWARE – ICS [in the WIN7 RC Build 7100 I have, at least] is very unstable and disconnects a LOT. When it does, remove the ICS on the first machine by following steps 1-2, uncheck, “OK”, then repeat steps 1-3, and it should reconnect – for another short time, at least.

ICS is really only suitable for quick and dirty temporary connections for the purpose of doing experimental work and quickie system updates for friends, for instance, and only when it just isn’t practical to run cable to the main router and the computer you are connecting simply doesn’t have a WLAN card. A cheap and simple WLAN USB adapter would be much much easier. So would a CAT5 connection to the main router if the distance is short. I only used it in this circumstance because the router is all the way on the other side of the house and impractical to stretch a wire to, and my only USB WLAN adapters are not Linux compatible. I had a couple short cables and a switch, so decided to use them. It took me 2 weeks of off and on research and trial and error… it would have been vastly easier to drag the Linux box downstairs or buy something compatible. Just call me stubborn.

By: Mogel

Mogel — Sat, 17 Oct 2009 21:34:02 +0000

Thank u so much. It works great.

By: Rablam

Rablam — Fri, 09 Oct 2009 14:50:49 +0000

Hi,

thanks for this article, it helped me a lot. (I m using Win 7 RTM as host)
But there is a detail which bother me : it’s written to use Host Only in in the setting of each VM that needs NAT, but this setting doesn’t make it work for, and when I use NAT, everything is ok. I dont’ really understand why using Host Only.
If someone can explain this to me. thanks

By: Ant75

Ant75 — Wed, 07 Oct 2009 03:18:52 +0000

Worked for me. Thanks. You need to select the host only network option for each guest in vmware itself. (Important!) It’s in the network properties section of vmware for each installed guest os.

Use automatic network ip settings in the guest os itself and in the host os (Win 7). I confirm an earlier post that Win 7 (the host) will report no internet access in the network and sharing center. But there is internet access and it works!

By: Chris

Chris — Wed, 30 Sep 2009 00:30:25 +0000

Thanks, it worked.

Comments on: Vmware Workstation NAT problem on Windows 7 RC Build 7100