Hi guys, Hunter Pitelka solved our problem. We were missing a group entry for the roughshark host in the /etc/dhcpd.conf file.
Tashi was doing everything correctly, we just didn't have dhcp configured properly. It's all good now. Thanks! Dave -- David O'Hallaron -- Prof of CS and ECE, Carnegie Mellon University -- contact: http://www.cs.cmu.edu/~droh On Tue, Aug 2, 2011 at 2:20 PM, David O'Hallaron <[email protected]> wrote: > Hi guys, > I was able to characterize my problem better, but I'm still not sure > why it is happening: > > For any instance created on one particular host (called roughshark), > the instance boots up OK and gets a valid IP address. But for some > reason, the DNS thinks it has a different IP address: For example: > > Instance test-00.vmnet has a true IP address of 192.168.1.134 > (confirmed by ifconfig in the console), but DNS thinks it's IP address > is 192.168.1.251 (via nslookup test-00.vmnet). > > It only happens on roughshark, it happens to every instance created on > roughshark, and it never happens on other hosts. > > Does this sound like a host configuration issue to you? > > Thanks! > Dave > > -- David O'Hallaron > -- Prof of CS and ECE, Carnegie Mellon University > -- contact: http://www.cs.cmu.edu/~droh > > > > On Mon, Aug 1, 2011 at 7:55 PM, Michael Stroucken <[email protected]> wrote: >> David O'Hallaron wrote: >>> >>> Thanks guys. I'll take a look at the console . >>> >>> -- David O'Hallaron >>> -- Prof of CS and ECE, Carnegie Mellon University >>> -- contact: http://www.cs.cmu.edu/~droh >>> >> >> I think both Richard and I mean attaching to the VMs console using VNC. >> >> Greetings, >> Michael. >> >
