Before I begin, I'm aware of all the issues that can arise from installing VMWare server on a DC. I did it anyway for a learning experience.
- Ethernet Controller Driver Windows 7 64 Bit
- Ethernet Controller Driver Microsoft
- Vmware Ethernet Controller Driver Windows 2008 R2 64
Re: Windows 2008 - Ethernet controller splat VirtualNoitall Jun 21, 2007 10:40 AM ( in response to trdavis55 ) OK, I did not have to do anything with the nic though. If reinstalling tools doesnt work, i would suggest changing the virtual network adapter to the E1000. I have not had any driver problems with the E1000 on 2k3, 2k8 or 2k8 R2, drivers included in the OS. If the VM is using a static IP you should note down the ip address/subnet mask/default gateway and dns servers first. Update: SVGA Drivers on Windows 2008 R2 and Windows 7 March 28, 2010 By Josh Townsend 3 Comments (Updated: June 29, 2013) I posted an article in December on how the SVGA driver included with VMware Tools caused the guest VM to freeze.
In the initial days of virtual machines, this was in fact not even possible. In this post we will tell you how to install Windows Server 2008 R2 x64 on VMware 7.0. Note: These instructions can also help in the installation of the 32-bit version of Server 2008. There is no Windows Server 2008 R2 driver that I can find for that model ethernet adapter, so see if the W7 Pro x64 driver from your notebook support page works, by manually installing it using the same procedure with 7-zip that you tried with the Intel one.
I'm trying to run a linux distro on my DC so I need to virtualise rather than run another box. My domain is pretty small so I'm not worried about load issues but the virtual network adapters VMware creates are affecting my DNS and generating all sorts of errors.
I'm not 100% sure but it looks like VMware requires the virtual adapters to work properly so there's no way of avoiding that issue. However, I might be able to disable the connections from registering with DNS.
edit:
VS creates a series of virtual network adapters which register as actual NICs in Windows. Since the machine is a DC, it will register these into DNS and may cause confusion when trying to resolve the server's name. I'm aware of the problem but am desperately trying to avoid having to migrate the DC/exchange to a virtual machine to get everything working in the one box. Therefore, I'm after some possible solutions to this problem.
atomicharri
atomicharriatomicharri
2 Answers
The correct thing to do here would have been to have virtualised the entire server with something like esxi and then installed the DC and the linux partition side-by-side.
However, if you insist on stepping over to the dark side, you need to go to each one of those virtual NICs in the Network Connections screen, go to properties, then properties for the connection, then properties for TCI/IP v4, then Advanced, then DNS, and un-check 'Register this connection's address in DNS'
Repeat and rinse for all the virtual network cards. I doubt this is the only issue that you'll encounter, but it should get you past this hurdle.
Mark Henderson♦Mark Henderson
Also, go into DNS manager, and set the DNS server to listen on only the real (non-vmware) interfaces. Make sure you uncheck all the vmware IPv4 and IPv6 addresses. That should stop A record lookup for the server name or domain name returning the vmware interface addresses, among other problems.
Ethernet Controller Driver Windows 7 64 Bit
![Controller Controller](/uploads/1/2/6/4/126433566/491555548.jpg)
Depending on the VM network settings, this may break their DNS resolution. I think you will be better off finding another way to fix that (manual settings; altering the vmware dhcp settings, if poosible; etc.).
Ethernet Controller Driver Microsoft
AdamAdam