OK - here's what I did, and it seems to have worked - but it's really brutal, and I *don't* recommend it:
I used the IP address I manually resolved to start the updates again. They timed out - hung on installing something or other, so I cancelled the updates. The updates didn't actually cancel, however, so I initiated shutdown. Shutdown hung, too, so I killed some processes. It still hung. So, I got really brutal and just powered off the VM, then powered it back up again and did a checkdisk. I then had DNS resolution going again, and started the patching process once more, and it proceeded just fine after that. All patches installed cleanly. I suppose I should patch ESX, but I'm actually on a day off right now, so will look into that after I get back into the office... On Thu, Aug 19, 2010 at 04:12, Joseph L. Casale <jcas...@activenetwerx.com> wrote: > Yeah, I thought maybe you had multiple nics in a team/trunk from the vm's > vswitch to the physical switch. > Sorry, no idea:( > jlc > > -----Original Message----- > From: Kurt Buff [mailto:kurt.b...@gmail.com] > Sent: Wednesday, August 18, 2010 7:59 PM > To: NT System Admin Issues > Subject: Re: The arrrgghhhness of it all... > > I have 3 adapters for the VMs, and two for management - network > failover is set for link detection only, no load balancing, no notify > switches, no failback. > > vswitch0 is the service console, vswitch1 is the virtual machine port group. > > Don't know if that answers the trunking question or not. > > Kurt > > > ---------- Forwarded message ---------- > From: Joseph L. Casale <jcas...@activenetwerx.com> > Date: Wed, Aug 18, 2010 at 18:34 > Subject: RE: The arrrgghhhness of it all... > To: NT System Admin Issues <ntsysadmin@lyris.sunbelt-software.com> > > > I saw something very similar a while ago:) > What's your esx vswitch and nic config and if you're using trunking, > what switch and how's it configured? > jlc > > -----Original Message----- > From: Kurt Buff [mailto:kurt.b...@gmail.com] > Sent: Wednesday, August 18, 2010 6:14 PM > To: NT System Admin Issues > Subject: The arrrgghhhness of it all... > > I'm trying to install Win2k3 R2 SP2 in an ESX3.5 VM, from scratch. > It's blowing up on it big time, and I am really unhappy with it right > now. > > Sitrep: > > Install Disk1 (Win2k3 R2 SP2), reboot, then Disk2, then install the > VMWare tools, reboot, then join doimain - no problem. > > Install first round of 90+ patches from the MSFT site, minus IE8 and > the malicious software removal tool, and plus a few optional goodies, > such as .NET framework updates, reboot - no problem > > Install the second round of 43 updates, and no more DNS name > resolution. Error in the event log 11167 Dnsapi - I've looked at that, > and several other eventlog entries that probably stem from that. (17 > W32tm, 1010 MsGina, 1053 Userenv in particular) > > I've scratched the machine twice and started over, and it's the same > each time. I can resolve NetBIOS names, but it barks on any FQDN. > "Ping request could not find host ad.example.com. Please check the > name and try again." > > EventID.net isn't much help, as I've tried everything on there I can > see, and it doesn't resolve the issue. > > Anyone run into this? It's terribly weird... > > Kurt > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
