VMware Workstation 3.2 Troubleshooting Troubleshooting In most cases, the simplest approach is to configure your virtual machine to use NAT. Workstation does not support non-Ethernet network adapter cards - including Token Ring, FDDI, CDDI and ATM adapters - in a bridged network. If you have a non-Ethernet network adapter, you can also use host-only networking. To provide a connection to an external network on a Windows host, you can use Windows Internet connection sharing or third-party proxy server or routing software on the host computer. On a Linux host, you can use IP masquerading to connect to non-Ethernet networks. The driver included with the PCnet Family Software for Windows NT 4.0/2000 at AMD's Web site may work slowly or not at all when run within a virtual machine. If you are using networking in a Windows NT virtual machine, make sure to install the AMD PCNET Family Ethernet Adapter driver version 4.15 included on the Windows NT 4.0 CD-ROM. You cannot use bridged networking if your host has a wireless NIC installed. If you want to run virtual machines on a host that uses wireless NICs, you need to configure your virtual machines to use NAT. If you are strictly using bridged networking for your virtual machines, and you do not foresee a need to use NAT or host-only networking, then you can disable or remove these adapters. This is considered changing your networking configuration. Look for the instructions appropriate to your host operating system under Disabling and Removing NAT and Host-Only Adapters at www.vmware.com/support/ws3/doc/network_ws.html. There is a media sense feature in Windows Me and Windows 2000 that can erroneously report a "Cable Disconnected" state when in fact the VMware Workstation networking is still functioning. When this networking feature is disabled in the guest, these erroneous disconnections do not occur. In your Windows Me guest, do the following:
In your Windows 2000 guest, you must edit the Windows Registry to disable the media sense feature. Instructions on how to do this can be found in the Microsoft Knowledgebase at support.microsoft.com/default.aspx?scid=kb;en-us;Q239924. When you are installing Workstation on a Windows XP host, a dialog box may appear asking if you want to configure virtual networking. This should happen in cases where your host computer has two or more network adapters connected to networks. Occasionally, this dialog box appears on a Windows XP host when it should not, and when you click Yes to designate which adapter should be used in virtual networking, the list of devices includes entries that do not represent the physical network adapters on the host computer. If this happens, after you click Yes to configure virtual networking, take these steps.
If Workstation attaches to the wrong device, you must uninstall the Workstation software, then reinstall it. The host-only and NAT network adapters (VMnet1 and VMnet8) are configured by DHCP. To reconfigure the IP address for the host-only or NAT adapter, modify it in vmnetdhcp.conf, located in your system32 folder. In addition, if you are reconfiguring the NAT adapter (VMnet8), you must change the IP address in vmnetnat.conf. You can find the IP address under [host]. On a Windows 2000 or Windows XP host, you also need to modify the value "HostIpAddress" in the the registry key HKLM\SYSTEM\CurrentControlSet\Services\VMnetDHCP\Parameters\VirtualEthernetSegments\1 for VMnet1, the host-only network adapter, or in the registry key HKLM\SYSTEM\CurrentControlSet\Services\VMnetDHCP\Parameters\VirtualEthernetSegments\8 for VMnet8, the NAT adapter. After you modify the registry, restart the VMnetDHCP service and, if you reconfigured the NAT adapter, the VMware Nat service. VMware Workstation was unable to communicate with the host-only network adapter that should be installed on your host computer. Verify that you have an adapter installed. On a Windows NT host, go to the Network control panel (Start > Settings > Control Panel > Network) and select the Adapters tab. An entry should be present for VMware Virtual Ethernet Adapter (basic host-only support for VMnet1). On a Windows 2000 host, go to the Network and Dial-up Connections control panel (Start > Settings > Control Panel > Network and Dial-up connections). An entry should be present for VMware Virtual Ethernet Adapter (basic host-only support for VMnet1). On a Windows XP host, go to the Network and Internet Connections control panel (Start > Control Panel > Network and Internet Connections > Network Connections). An entry should be present for VMware Virtual Ethernet Adapter (basic host-only support for VMnet1). If no entry is present, you need to add one. On Windows NT, click Add and select the entry VMware Virtual Ethernet Adapter (basic host-only support for VMnet1) from the scrolling list, then click OK until the control panel prompts you to reboot the system. Note that adding a network adapter requires rebooting Windows NT. On a Windows 2000 or Windows XP host, you need to restore the default VMware Workstation networking settings. Make sure all your virtual machines are shut down or suspended, and all virtual machine windows are closed. Go to the Programs folder in the folder where you installed VMware Workstation (for example, C:\Program Files\VMware\VMware Workstation\Programs), and run the InstNetwork.bat script. This cleans up the host and installs the default network components for VMware Workstation.
The most common reason for this is that the guest and host operating systems have IP addresses that are on different subnets. To find the IP address assigned to the host-only adapter, on the host computer open a command prompt and run Are your virtual machines using host-only or NAT networking and on a Windows host? Networking performance on your host may slow down when browsing your Windows host and network. VMware Workstation's virtual networking installs two virtual Ethernet interfaces on the host so that your host can access the host-only and NAT virtual networks, which in turn allow your host to access the virtual machines running on those networks and allows those virtual machines to access the host. If you are already connected to a network, you may notice that it takes a little longer to find all the machines on your physical network because the host checks the virtual networks for any virtual machines that may be running. If your virtual machines are not using NAT or host-only networking or are not running at the moment, you can disable the virtual network adapters to improve your host's networking and browsing capabilities. Steps follow for each supported Windows host. Disabling the Virtual Network Interfaces on a Windows XP Host
Disabling the Virtual Network Interfaces on a Windows 2000 Host
Disabling the Virtual Network Interfaces on a Windows NT Host
The most likely cause is that the network adapter in the host computer is having problems when Workstation tries to set it to promiscuous mode. Try running tcpdump (as root) on the host operating system. If the host computer crashes, the most likely explanation is that the network adapter cannot handle promiscuous mode. Try an updated driver for the network adapter on the host or use a different network adapter that does support promiscuous mode. Once you can get tcpdump to work on the host, the virtual machine should work in bridged mode, as well. Workstation does not allow the virtual Ethernet adapter to go into promiscuous mode unless the user running Workstation has permission to make that setting. This follows the standard Linux practice that only root can put a network interface into promiscuous mode.
When you install and configure Workstation, you run the installation as root, and the installer creates the VMnet devices with root ownership and root group ownership. It also gives those devices read/write access for the owner root only. For a user to be able to set the virtual machine's network adapter to promiscuous mode, the user who launches Workstation needs to have read/write access to the VMnet device One way to do this is to create a new group, add the appropriate users to the group, then give that group read/write access to the appropriate device. These changes need to be made on the host operating system as root (su). For example:
chgrp <newgroup> /dev/vmnet0 where <newgroup> is the group that should have the ability to set vmnet0 to promiscuous mode. If you want all users to be able to set the virtual network adapter (/dev/vmnet0 in our example) to promiscuous mode, you can simply run the following command on the host operating system as root. chmod a+rw /dev/vmnet0
|
