<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Enabling Enhanced VMXNet</title>
	<atom:link href="http://blog.scottlowe.org/2008/12/15/enabling-enhanced-vmxnet/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.scottlowe.org/2008/12/15/enabling-enhanced-vmxnet/</link>
	<description>The weblog of an IT pro specializing in virtualization, storage, and servers</description>
	<lastBuildDate>Wed, 08 Feb 2012 17:13:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: John</title>
		<link>http://blog.scottlowe.org/2008/12/15/enabling-enhanced-vmxnet/comment-page-1/#comment-43926</link>
		<dc:creator>John</dc:creator>
		<pubDate>Fri, 20 Mar 2009 22:00:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2008/12/15/enabling-enhanced-vmxnet/#comment-43926</guid>
		<description>Another caveat: I also had the same problem with network connections being created, as well as: 1) the &#039;old&#039; AMD NIC not being removed and requiring command-line configuration of Device Manager to remove the old NIC (later realized this could have been avoided by removing the NIC before taking it out of inventory but then I would not have been able to log on to it again); 2) creation of addtional IP addresses for the server(s) within DNS, causing all kinds of unexpected problems.
Solution: This method can be used but you must plan for several extra steps and time for making sure the old NIC is removed and that your DNS doesn&#039;t get mucked about with, you have to clean out any DNS entries that do not belong, also do this multiple times if you have more than 1 DNS server in your LAN.</description>
		<content:encoded><![CDATA[<p>Another caveat: I also had the same problem with network connections being created, as well as: 1) the &#8216;old&#8217; AMD NIC not being removed and requiring command-line configuration of Device Manager to remove the old NIC (later realized this could have been avoided by removing the NIC before taking it out of inventory but then I would not have been able to log on to it again); 2) creation of addtional IP addresses for the server(s) within DNS, causing all kinds of unexpected problems.<br />
Solution: This method can be used but you must plan for several extra steps and time for making sure the old NIC is removed and that your DNS doesn&#8217;t get mucked about with, you have to clean out any DNS entries that do not belong, also do this multiple times if you have more than 1 DNS server in your LAN.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://blog.scottlowe.org/2008/12/15/enabling-enhanced-vmxnet/comment-page-1/#comment-43922</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Fri, 20 Mar 2009 13:07:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2008/12/15/enabling-enhanced-vmxnet/#comment-43922</guid>
		<description>I also discovered that this removed my existing network connection and created a new one which had to be re-configured. I know this is obvious to someone like you, but a note should be added just to be safe.

Also for some reason after adding the vmxnet NIC I had problems with Outlook 2003 the next day.</description>
		<content:encoded><![CDATA[<p>I also discovered that this removed my existing network connection and created a new one which had to be re-configured. I know this is obvious to someone like you, but a note should be added just to be safe.</p>
<p>Also for some reason after adding the vmxnet NIC I had problems with Outlook 2003 the next day.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://blog.scottlowe.org/2008/12/15/enabling-enhanced-vmxnet/comment-page-1/#comment-43915</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Thu, 19 Mar 2009 19:27:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2008/12/15/enabling-enhanced-vmxnet/#comment-43915</guid>
		<description>I had to directly log in to the host via VIC to get it to let me specify enhanced vmxnet for Win2k3 Enterprise...using VIC via VC threw errors and would not let me create the VM...</description>
		<content:encoded><![CDATA[<p>I had to directly log in to the host via VIC to get it to let me specify enhanced vmxnet for Win2k3 Enterprise&#8230;using VIC via VC threw errors and would not let me create the VM&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Randy Robertson</title>
		<link>http://blog.scottlowe.org/2008/12/15/enabling-enhanced-vmxnet/comment-page-1/#comment-43487</link>
		<dc:creator>Randy Robertson</dc:creator>
		<pubDate>Sat, 31 Jan 2009 09:39:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2008/12/15/enabling-enhanced-vmxnet/#comment-43487</guid>
		<description>In response to the previous question, I believe it was just a matter of testing bandwidth.  This should be rectified as of the latest shipping ESX3.5 updates.  Advanced should be an option on all guest OSes where it would work, including Windows Server 2003 Standard.</description>
		<content:encoded><![CDATA[<p>In response to the previous question, I believe it was just a matter of testing bandwidth.  This should be rectified as of the latest shipping ESX3.5 updates.  Advanced should be an option on all guest OSes where it would work, including Windows Server 2003 Standard.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: NiTRo</title>
		<link>http://blog.scottlowe.org/2008/12/15/enabling-enhanced-vmxnet/comment-page-1/#comment-43097</link>
		<dc:creator>NiTRo</dc:creator>
		<pubDate>Tue, 30 Dec 2008 16:33:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2008/12/15/enabling-enhanced-vmxnet/#comment-43097</guid>
		<description>Hi,

Someone knows why Windows Server 2003 Enterprise Edition but not standard ?</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>Someone knows why Windows Server 2003 Enterprise Edition but not standard ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: slowe</title>
		<link>http://blog.scottlowe.org/2008/12/15/enabling-enhanced-vmxnet/comment-page-1/#comment-42796</link>
		<dc:creator>slowe</dc:creator>
		<pubDate>Tue, 16 Dec 2008 01:23:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2008/12/15/enabling-enhanced-vmxnet/#comment-42796</guid>
		<description>Wade,

Thanks for the information. I&#039;ve updated the post accordingly.</description>
		<content:encoded><![CDATA[<p>Wade,</p>
<p>Thanks for the information. I&#8217;ve updated the post accordingly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wade Holmes</title>
		<link>http://blog.scottlowe.org/2008/12/15/enabling-enhanced-vmxnet/comment-page-1/#comment-42793</link>
		<dc:creator>Wade Holmes</dc:creator>
		<pubDate>Mon, 15 Dec 2008 22:35:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2008/12/15/enabling-enhanced-vmxnet/#comment-42793</guid>
		<description>Hi Scott, 

Enhanced VMXNet adapter is a vCenter selectable option for 32-bit Windows Server 2003 Enterprise Edition along with 64-bit. I have used it successfully to allow jumbo frames to 32-bit Windows 2003 Enterprise Edition VM&#039;s.</description>
		<content:encoded><![CDATA[<p>Hi Scott, </p>
<p>Enhanced VMXNet adapter is a vCenter selectable option for 32-bit Windows Server 2003 Enterprise Edition along with 64-bit. I have used it successfully to allow jumbo frames to 32-bit Windows 2003 Enterprise Edition VM&#8217;s.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

