For Windows 7 RTM (7600) go here : http://www.archy.net/2009/08/10/vmware-workstation-nat-problem-on-windows-7-rtm/ 

Vmware workstation 6.5.1 build-156735 can be installed on Microsoft Windows 7 RC Build 7100 without any problem. I was able to open all my VM but I had an issue with the network nat translation. All my VM didn’t had internet access through the host nat (Windows 7). Since the Windows 7 Beta Build 7057 a new network address has been used to establish communication between VMWare Workstation and Microsoft Windows 7 (192.168.137.0/24)

Here come a short article to help you to go through :

1. Run the Virtual Network Editor as Administrator (Use RunAS or right click and Run as Administrator on vmnetcfg.exe)
2. Goto Host Virtual Adapters and remove all VMNet instances (VMNet1 and VMNet8 typically).
3. Click Apply.
4. Add New and Assign it the new adapter to VMnet1.
5. Click Apply.
6. Select the Host Virtual Networking tab.
7. Click the > next to VMnet1 and change the address and subnet to the ICS network (192.168.137.0 / 255.255.255.0)
8. Click Apply.

(more…)

53 186

  • Pingback: Vmware Workstation NAT problem on Windows 7 Beta | ArchY.net()

  • jack

    im using a win7 host with centos guest unfortunately this doesnt work for me

  • Hi jack,

    Maybe you should tell us a bit more, what have you done, what is configure, we can maybe bring you some help

  • jack

    i did exactly what your instructions said and i cant get it to work.
    i did change my router ip address from 192.168.1.1 to 192.168.0.1 and now i cant access my router (unless i reset it to factory defaults)

  • Askard

    It is working. Thanks ArchY

  • Wow

    Wow. Wonderful!

    I works like a charm!

    Thanks buddy for great info 🙂

  • Thanks,

    It works now. 🙂

  • jack

    since i have teamviewer installed, does it have any affect why i dont have any internet access?

  • Jack : I don’t know teamviewver, but if this software install a virtual network card, you have to share the internet access with it instead of your main network card. maybe…

  • Tiago

    Nice solution.
    But it’s a pain in the ass if you, just like me, use diferent connections all the time.

    From the network card, to wireless, to 3G…

    I have to re-select the conection been shared all the time.

    VMWare or MS needs to work it out.

  • Thanks!

    Works great with RC7100 x64 host and XP SP3 guest.

  • Kenneth

    Thank you 🙂 This really helped. I got this to work with Suse 10 guest. I had to give the guest a static ip and gateway to make it work.

    Also in Network and Sharing center @ the windows 7 host the VMWnet1 shows up with “No Internet access” after sharing the Local Area connection but it still works. I wanted to mention this incase anyone else got confused by this aswell.

  • Thanks. It really helped. I was having problems with my Windows Xp trying to reconfigure it a hundred times..

  • Julio Cesar

    Thanks a lot! …I had spent several hours untill I found this post …it works for me! …using Windows 7 RC1 build 7137 and vmware-server-2.0

  • Aikidoka

    I can ping my gateway, 192.168.137.1, resolve DNS queries, but cannot load websites. So close, but not quite working.

  • bobbybrown

    I tried this and I haven’t gotten it to work the only thing that I can think of is that I couldn’t find the “Host Only Networking” you mentioned that in one of your steps and I don’t know where that checkbox is.

    Furthermore, I’m running windows 7 build 7100 and on the Sharing tab it does not allow me to specify the VMNet01 as in your screen shot I can only turn on “Allow other network users to connect through this computer’s internet connection” is there a special place I need to go to specify that? Thanks

  • Aikidoka

    Bobbybrown: I still can’t get my web connections working and just tried it all again. After step 18, you can close the Virtual Network Editor. Step 19 doesn’t mention that you run VMWare Workstation at that point, edit the VM, select Network Adapter, and THEN check host-only.

    As for your sharing issue. Did you do that last? VMNet 1 will not be an option until you have added it in Virtual Network Editor. If you have added it there, make sure you actually see it as a network connection on the Windows 7 host.

  • Aikidoka

    Just got it working!!! Turned off the Windows Firewall on the host and rebooted. Still took the VM a minute or so to make the first connection. Now I have to get the proper firewall rules in so I can turn it back on.

  • ok, well, if you need some more help just post in here, I’ll try to bring some light

  • Joris Kempen

    I really stuck at point 20. :

    20. Enable ICS (Internet Connection Sharing) on the Windows 7 Host network card that provides connectivity. Select VMNet1 as the network card that needs access.

    My window looks different and i CANNOT choose the other VMNET1 to be accessed. The option is just missing.

    It is the same problem as BobbyBrown mentions…

    I also tried this solution of bridging the 2 connections, but is also not working for me..

    http://anordinarything.com/2009/05/windows-7-rc-7100-nat-not-working-in-guest-fix/comment-page-1/#comment-15

    Any ideas???

  • bobbybrown

    Aikidoka: Thanks for your help I’m much closer now but still no dice.

    When I go to “change adapter settings” and then go to the properties of “Local Area connection” then “sharing” there is no where to specify the VMnet1. Do I need to set anything else up or go somewhere else to select the connections that are allowed to use the ICS to connect out?

    My linux vm is now able to ping the 192.168.137.1 ICS network and my host computer can ping the VM which is 192.168.137.128. But the vm cannot reach the internet. I believe it’s because I have not explicitly specified that it is allowed to use the host network connection to reach out. Thoughts?

  • Joris Kempen

    still having the same problem… just can’t choose a NIC in step 20…

    and don’t know how to google on this problem!!

  • Silver0066

    I could not get it to work. Before following the instructions I could connect to my network but not the network in my XP Pro SP3 Guest running Win 7127 Host.

    Now, the guest has “limited on no network connectivity”.

    I am using a static IP on my host. Any suggestions how that might affect your intructions?

    Many thanks,

    Silver

  • Silver0066

    In my previous post, I mean I could connect to my Win7 network from the guest but not the Internet.

    Silver

  • Rik

    Hi,

    I managed to get internet working on my VM’s but now they can’t see each other.
    I’m in the 192.168.137.0 subnet and i have 2 vm’s (192.168.137.131 and 192.168.137.132) when i try to ping from one to the other it doesn’t work.
    They are able to ping 192.168.137.1 and the internet.

    How can i make it work so they can ping each other?

  • Hi Rik
    By following this how to, you configure your VM in host only mode, which mean your VM can communicate only with your host (your workstation) two VM are nbot able to communicate between eatch other.

    The Windows 7 RTM will soon be out and I’m sure VMWare will deliver a new version of their product to fixe this issue.

  • Rik

    Hi Stephane,

    I found a working solution:
    http://florianlr.wordpress.com/2009/07/09/5/

    This way the VM’s see each other AND have access to the internet. Just as it should be 🙂

  • Steps 19 and 20 could use some clarification, but this guide really saved my butt. Thanks!

  • GREAT! this worked superb for me (i am using win7 rtm + vmware workstation 6.x)

    thanx a lot

  • DoesntWork

    This absolutely does not work. I followed the instructions step by step. I am using Windows 7 build 7100 and the latest production version of VMWare Workstation.

    Before I messed with the settings, I could ping external hosts and websites but could not access them via the browser.

    Now I cannot ping anything outside and I still can’t use the browser.

    As others have mentioned, I do not have the ICS option of specifying VMNet 1 adapter. And yes, I already added the adapter in and it DOES show up in Windows.

  • DoesntWork

    Selecting Bridge Mode for the host adapter step (#19) works for me, selecting Host Mode does not.

  • DoesntWork

    PS – I figured out the reason ICS doesn’t show the same as the screenshot — it doesn’t show if you only have one VMNet adapter. By default you have two (VMNet1 and VMNet8). If you leave it so you have those two, it does show up in the screenshot. Figuring out how to select one or the other is a different story.

  • Nacho

    It worked for me, but I disable the NAT so I have under the network adapter in VMWare
    custom: VMNet1 (Host-Only)….

    I did all that is described here but under NAT VMnet host: Disable

    also, I remove all the vmnets on regedit.
    under computerHKEY_LOCAL_MACHINESOFTWAREVMWARE,INC.VMNETCONFIG

    because somehow all the changes I was doing under virtual network editor were not displayed under the summary tab… after i delete it i was able to change the ip address of the virtual adapter and it worked like a charm….

  • eco

    Thanks much ArchY!!! — Your procedure worked like a champ after I had attempted alot of different alt vnet approaches to get this working today on my win7 host .. Been using vmware workstation since 2003 yet this was still a very useful exercise & it allowed me to get my mint7 & win2k8 vmz net connected up nicely in about 10 mins after finding your post!!! Thank you sir ..

  • you’re very welcome 🙂

  • John

    Your page is great but it didn’t quite work for me.

    As others have said, I did not see the name of the connection when sharing my internet connection (ICS) on the host machine (Win7 RC1-7100). I’m not surprised since I only have one VMnet left.

    I tried NAT in the guest + ipconfig release and renew, no luck. I tried Specific and selected VMnet1 + release and renew, no luck. I tried Host-Only + release and renew, no luck. Tried Bridged + release and renew and it worked!!!!!!! YEAH!!!!!!

    Actually, to be clear, on the guest VM settings that did not work, I did always get an IP address in the expected range but I could never open a website. Bridged was the only way to get it to work for me.

    Man, that was frustrating but your post made it way, way easier. Thanks a million.

  • mood

    if you pls send me that link to dowdnload vmware which is work on win7 rc build 7100

  • Witcher

    THANKS!!!

    IT WORKS

    You people really helped me.

    ;-D

  • MadFrog

    Thanks a lot! This is a lifesaver.

    Works great with win7 7100 and vmplayer 2.5.2 with ubuntu 9.04.

    A pity this article doesn’t show up in the vmware forum search.

  • Karol

    Thanks !!

    This trick works with Windows 7 Ultimate RC (Build 7100) as host and Fedora 11 Linux as guest.

  • Sergio Moreno

    Thanks!!

    Saved my life!!

  • Chris

    Thanks, it worked.

  • Ant75

    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!

  • Rablam

    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 🙂

  • Mogel

    Thank u so much. It works great. 🙂

  • Tearsfall

    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.

  • Rajeev Borborah

    Works excellent step by step information

    Thanks
    Raj

  • Somewhere in Asia

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

  • from italy

    It worked, thanks!

  • lijo

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

  • s@m

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

  • Paul

    Thank you very much, that helped a lot.

  • Cado

    Thanks a lot for the info, really helpful.

    The only one that worked!!!!!

    Awesome!!!!