Sometimes you just have to give credit…
Earlier today I installed VMware Server on a machine at work and then built a client Windows 2003 server on it. The install went smoothly, but once it was up and running I found I couldn’t get it on the network. In fact, I couldn’t even ping the gateway by IP address.
I installed the VMware tools thinking maybe I was missing drivers, but that didn’t fix it. I spent way too much time messing around with the client’s IP configuration as I was assuming that the issue must be something I’d typed or set wrong. However, after an hour of no progress I had to suck it up and search the web.
Fortunately, I found my answer almost immediately at the #ifdef blog. Turned out to be a VMware Server configuration issue – it was grabbing the Hamachi LAN adapter instead of the Ethernet adapter.
The fix was to force the VMnet0 controller choice rather than allow it to bridge to an automatically chosen adapter. By doing that, the virtual machine was able to get an IP on the LAN.
A few clicks and I was up and networking properly.
I love finding answers on other blogs. Ironically, I searched for something last week and found the answer in a post I’d written here 2 years ago. Kind of embarrassing… I didn’t remember writing about it until I saw the search results!
Possibly Related posts:
Loading tweets...
1 comment
1 ping
Johnny
January 25, 2012 at 2:02 pm (UTC -7)
How do you force the VMnet0 controller choice for VMWare Player 3 and 4?
Vmware Server Bridging Problem
March 16, 2010 at 9:01 am (UTC -7)
[...] with a server running windows 2003. I searched all around on the net and finally came across this [...]