Windows cannot load network driver (even after re-installation of the tools)

Discussion in 'Windows Virtual Machine' started by Jayfp61, Jun 23, 2011.

  1. Jayfp61

    Jayfp61 Bit poster

    Messages:
    2
    I have a fresh installed MacBook Pro with a fresh installed Windows 7 32Bit on a boot camp partition. I installed parallels desktop 6 but got no network connection. In the device manager windows says that the device driver for the network adapter is not installed.

    I removed parallels tools and reinstalled parallels tools. I moved from shared mode to bridged mode and back but windows does not detect the network driver.

    Any ideas?
     
  2. ManogT

    ManogT Bit poster

    Messages:
    2
    Try this...

    Coincidentally I have just loaded parallels 6 today as well onto my new Macbook Pro (2011 version) and got the same problem with the intel driver. After a bit of experimenting have finally got this to work by re-installing the intel chipset drivers.

    I am new to Mac OSX so please take this info as a suggestion and not expert advice.

    I am using 64Bit Windows 7 but I guess should work on 32 bit.

    Also I imported the Boot Camp image prior to trying this, and performed the changes on this virtual image to make sure I did not mess up the actual installation of windows 7 on the Boot Camp partition.

    You will need the Mac OSX installation disk or the files that you downloaded to create your bootcamp installation.
    Here are detailed instructions if needed...

    1. Start up the Imported Windows 7 VM
    2. Open up the device manager (right click and select 'manage' from 'my computer)
    3. Find the problem Intel network device driver and de-install it
    4. Run setup.exe from D:\Boot Camp\Drivers\Intel\Chipset to re-install the intel chipset drivers (where D: is your DVD or USB drive containing the bootcamp files)
    5. Reboot as required
    6. Use shared networking if you plan to use the macbook and windows 7 internet at the same time (I found that setting up a bridged airport meant you could no longer use airport for OSX at the same time. In the case of Bridged default adapter, I found I got IP address conflicts as I guess both 'machines' contend for the same IP address??). If anyone knows any different - please share...

    should start working, and not encountered any more problem so far. hope this helps
     

Share This Page