After I upgraded from ESX 3.5 to 4.0 I also upgraded the virtual hardware from V4 to V7. That meaning the some of the virtual hardware in the vm had to be reinstalled. In Windows 2008 server it installed a new NIC called “Local Area Connection 2″ with the E1000-driver. Some services like DNS did not like that. I fixed it by adding another NIC (VMXNET3) and adding the former IP. Then I deleted the E1000-NIC.
Poll
Are you a VCP?
- Yes, i am VCP3 (43%, 3 Votes)
- No (29%, 2 Votes)
- Yes, i am VCP4 (28%, 2 Votes)
Total Voters: 7
Loading ...
VMware RSS feed- Connecting View Manager to vCenter Server fails (1024596) July 30, 2010
- Troubleshooting User Connection Issues in Virtual Desktop Manager (1003642) July 30, 2010
- VMware Workstation Full License Not Overriding Evaluation License (1447) July 30, 2010
- Starting View Composer service fails with the error: The service did not respond to the start or control request in a timely fashion (1024376) July 30, 2010
- FAQ: Supported/Unsupported Devices and Configurations (1184) July 30, 2010
- Enabling VT on Intel EM64T Systems for ESX Server 3 (3282933) July 30, 2010
- Obtaining a VMware Converter 3.0 Enterprise License (1000041) July 30, 2010
- Update Manager Client becomes disabled randomly (1007099) July 29, 2010
- Changes in software and hardware iSCSI configurations require you to reboot your host (7372490) July 29, 2010
- Cleaning up damaged restore points in VMware Data Recovery (1013387) July 29, 2010
Leave a Reply