<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dhcp on Evan Hoffman</title><link>https://evan.wtf/tags/dhcp/</link><description>Recent content in Dhcp on Evan Hoffman</description><generator>Hugo</generator><language>en-US</language><copyright>Evan Hoffman</copyright><lastBuildDate>Wed, 23 Feb 2011 10:29:22 +0000</lastBuildDate><atom:link href="https://evan.wtf/tags/dhcp/index.xml" rel="self" type="application/rss+xml"/><item><title>VMware Workstation 7 - virtual ethernet fails to start after changing vmnet8 subnet</title><link>https://evan.wtf/2011/02/23/vmware-workstation-7-virtual-ethernet-fails-to-start-after-changing-vmnet8-subnet/</link><pubDate>Wed, 23 Feb 2011 10:29:22 +0000</pubDate><guid>https://evan.wtf/2011/02/23/vmware-workstation-7-virtual-ethernet-fails-to-start-after-changing-vmnet8-subnet/</guid><description>&lt;p&gt;After my recent wipe of my laptop, I reinstalled VMware Workstation and my Win XP VM was working fine. The one wrinkle I faced was that the subnet for the vmnet8 (NAT) vnic had changed from 192.168.250.0/24 to 173.16.132.0/24. The host machine had been 192.168.250.1 so rather than reconfiguring everything on the guest to point to a new IP for the host I figured it would be easier to change the subnet for vmnet8. I went into the Virtual Network Editor and just changed the subnet. Seemed to work correctly, but after doing a release/renew in Win XP I couldn&amp;rsquo;t get an IP.&lt;/p&gt;</description></item></channel></rss>