Base | Lab | MCSE | Servers | Server01
Networking up and running
Soon after trying to do the first thing that involved networking (connecting from the host to the guest using Remote Desktop, to be precise) I found out that networking was not operational.
The first thing that I did was to configure the VMWare networking subsystem. Sort of like a virtual machine provides a machine's hardware, there is a service installed that provides the machine's networking environment. This means a NIC inside the virtual machine, but also one or more NICs on the host. VMWare is able to act as a bridge, connecting the virtual 'internal' network to actual outside NICs, thus providing virtual machines with connectivity to the rest of the world, beyond the host.
I opted for host-only networking (which effectively disables outside access for the virtual machine; the concept is like plugging a cable into a router that is local to this small network.
To avoid confusion between the private IP range on my home network and the private IP range on the host-based network, I set the DHCP range to use the 10.0.0.0 network.
Apparently, newly configured Windows 2003 servers don't even bother looking for a DHCP server, so I changed the TCP/IP properties to 'Obtain an IP address auomatically'. I have often wondered why Microsoft don't just call this option 'Use DHCP when available', which would be a much more accurate description of what it actually does. Oh, well, it works anyway.
With the NIC disabled and re-enabled, Server01 has now got an IP address that is actually on the network it is on and I can ping the box from the host. Strangely enough, I couldn't seem to do that the other way around at first. Then it hit me that I usually have Norton Internet Security running, which is (among other things) a firewall, which undoubtly blocks incoming ICMP messages.
I say undoubtly, because making sure is just too much work to find out. I reckon I won't be using that product for very much longer, especially when XP SP2 comes out with its vastly improved built-in personal firewall. NIS seems to be wanting to do the right thing (configure all applications exactly according to their needs and only allowing incoming traffic when there is a corresponding application running) but the interface is so incredibly clunky that I can't seem to deal with it. Also, it appears to have a very hard time remembering settings. But that is the topic of another rant, another time.
After disabling the firewall and bouncing the host NIC (to get the right IP address from the reconfigured DHCP server) I had connectivity in two directions and I was able to set up a Remote Desktop session.