They expose many more configuration options than the typical drivers.
The network adapter properties.ĭid you notice that there are more tabs along the top of this dialog box than other network adapters? That’s the Intel PROSet drivers in action. This will bring up the NIC properties as shown in Figure 3.įigure 3. To manage NIC properties, click the Configure… button directly under the adapter name. You want to manage the properties of the NIC itself, not protocol properties like TCP/IP or NetBIOS. Right-click on the connection that you want to change and then click Properties to bring up the network connection properties as shown in Figure 2.įigure 2. The list of physical and virtual network adapters. This displays the Network Connections list as shown in Figure 1.įigure 1. In the Network and Sharing Center windows, click on Change Adapter Settings in the left pane. Open Control Panel, then click on Network and Sharing Center.
If you’ve not yet done that, you can get the driver installer package from Intel® Download Center. The steps assume that you’ve already installed the Intel PROSet drivers for your Ethernet NIC.
Here’s how to do it when you’re running Windows with an Intel Ethernet NIC. However, you might have the need to change the MAC address on a system. Each address must be unique to the network, and should be globally unique. In the Ubuntu VM, /etc/network/interfaces looks normal:Īnd, eth0 is what shows up in dmesg output:Īnd, lspci output on this VM looks the same as the lspci output on a box that works.Ġ2:00.You probably already know that each network interface card (NIC) on a network must have a media access control (MAC) address. Why would the ethernet interface now be showing up as eth1? Most recently, I made the appropriate changes for an Ubuntu VM (hosted on Windows XP running Workstation 6.04), closed and reopened the UI, and after the VM booted, there was no eth0 interface, instead, the MAC address I assigned for ethernet0 is now showing up on eth1. Given the intermitent behavior, it's probably worth updating the knowledge base article sooner rather than later. When setting static MAC addresses up today on 6 VMs, it worked a few times without having to close the UI (before finding this post). There doesn't seem to be a consistent behavior pattern. Sometimes it works without closing the UI. VirtualHW.productCompatibility = "hosted" Scsi0:0.fileName = "Windows Server 2003 Standard Edition-000001-cl2.vmdk" The only I changes I made were in the lines specified in the KB article:Įthernet0.addressType = "generated" # Didn't origiinally have this, but I tried adding it with = "static", VMware changed it to = "generated"Įthernet0.address = "00:50:56:00:00:23" # My desired MACĮthernet0.generatedAddressOffset = "0" # VMware added this when it didn't like my MAC assignmentĮthernet0.generatedAddress = "00:0c:29:c5:97:c0" # VMware's new generated MAC Here's the vmx from one of the VMs that doesn't see its assigned MAC.