It's not a Host issue, since when I snap the vm's back pre upgrade they work fine. It's surely something screwey in the OS. What would cause a Windows Server 2008 to think it has only "Local" connectivity? What *smart* service does this monitoring?
Thanks! jlc From: Richard Stovall [mailto:[email protected]] Sent: Friday, May 29, 2009 10:26 AM To: NT System Admin Issues Subject: RE: Windows 2008 Networking Issue I haven't used vSphere yet. We're still happily chugging along with 3.5u4. That said, it sounds like the virtual switches might have become mangled somehow. Can you ping vm to vm on the same host? On different hosts? From: Joseph L. Casale [mailto:[email protected]] Sent: Friday, May 29, 2009 12:10 PM To: NT System Admin Issues Subject: Windows 2008 Networking Issue Working on an issue with the developer of the vmxnet3 driver at vmware and I could use some guidance here. After an upgrade to vSphere, if I delete the e1000 nic from a 2008 server and add a vmxnet3 nic, all the servers think they only have "Local" connectivity? In the Network and Connection Sharing Center, there is a red "x" between the domain name and the internet. The dns server and gateway and subnet are all correct, everything matches the old settings? I even deleted the hidden non present nic... Anyone seen this, and know wtf is going on? Thanks, jlc ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
