Tuesday, April 29, 2008
Superior Alternatives to Crappy Windows Software
read more | digg story
Whats New Now - WNN
Weekly or Bi Weekly web clip of hot topics around the world.
Whats New Now
This weeks topics: "Apple Updates iMac, Grand Theft Auto IV hits stores, Nokia's "Beautiful to use" Phones, Google's VisualRank and Falcon Northwest's Fragbox 8500 "
1337! 5 Killer PC Games playable on Ubuntu: Hardy Heron
Read up on Kubuntu Hardy Heron
read more
| digg story
Ultra-Long-Endurance Aircraft to Stay Aloft for Years
read more digg story
10 Tips for After You Install or Upgrade Ubuntu
read more | digg story
Microsoft releases the long-anticipated Windows XP SP3
read more digg story
Thursday, April 24, 2008
Monday, April 14, 2008
Using Shared Networking (NAT) with a Windows Server 2003 virtual machine


Normally using Shared Networking is very simple. You just enable it and set the guest operating system to use DHCP - and everything works. This is not the case with a Windows Server 2003 guest though. The problem is that Shared Networking configures the guest operating system to use the same DNS servers as are used by the physical computer. However - all DNS packets are actually returned from '192.168.131.254' - which is the virtual gateway used by Shared Networking.
Windows Server 2003 looks at the DNS packet, sees that it is coming from a source other than the DNS server it requested the information from, and rejects it. A simple fix for this is to manually assign the DNS server inside the virtual machine to 192.168.131.254 - then everything will work just fine.
Cheers,
Ben"
Quoted from: http://blogs.msdn.com/virtual_pc_guy/archive/2005/01/06/347965.aspx
Thanks Ben for the great write up!