<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Strange behaviour with network interface in VI: VMware ESX™ 3.5 Discussions</title>
    <link>https://communities.vmware.com/t5/VI-VMware-ESX-3-5-Discussions/Strange-behaviour-with-network-interface/m-p/836331#M42922</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've found the solution.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In fact my virtual switch was limited to 32 ports and my VM was the 33.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've put 120 virtual ports and rebooted and now all is OK &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 30 Jun 2010 12:05:43 GMT</pubDate>
    <dc:creator>xybal</dc:creator>
    <dc:date>2010-06-30T12:05:43Z</dc:date>
    <item>
      <title>Strange behaviour with network interface</title>
      <link>https://communities.vmware.com/t5/VI-VMware-ESX-3-5-Discussions/Strange-behaviour-with-network-interface/m-p/836328#M42919</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've got a  Strange and probelmatic behaviour with network interface on a VM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I clic in settings "connected at power on" and then boot My VM  (Win 2003 server).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When the VM is booted I see in the settings the first option not checked, so I check "connected" and the I clic OK.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There no messages and all seems OK, then I go again in settings and "connected" is again not checked.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've tried these several times and everytimes the same behaviour .... strange &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a way to avoid this and having a "normal" behavior ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thx &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Jun 2010 09:30:32 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VI-VMware-ESX-3-5-Discussions/Strange-behaviour-with-network-interface/m-p/836328#M42919</guid>
      <dc:creator>xybal</dc:creator>
      <dc:date>2010-06-14T09:30:32Z</dc:date>
    </item>
    <item>
      <title>Re: Strange behaviour with network interface</title>
      <link>https://communities.vmware.com/t5/VI-VMware-ESX-3-5-Discussions/Strange-behaviour-with-network-interface/m-p/836329#M42920</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That is a bit odd, I would start by adding in another network card and see if it has the same behaviour, if it does create another VM, creating a new VMX file then attach your old VMDKs.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Jun 2010 10:32:14 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VI-VMware-ESX-3-5-Discussions/Strange-behaviour-with-network-interface/m-p/836329#M42920</guid>
      <dc:creator>rogard</dc:creator>
      <dc:date>2010-06-14T10:32:14Z</dc:date>
    </item>
    <item>
      <title>Re: Strange behaviour with network interface</title>
      <link>https://communities.vmware.com/t5/VI-VMware-ESX-3-5-Discussions/Strange-behaviour-with-network-interface/m-p/836330#M42921</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have already tried this but this is the same thing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I will try creating a new VM . &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Jun 2010 11:23:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VI-VMware-ESX-3-5-Discussions/Strange-behaviour-with-network-interface/m-p/836330#M42921</guid>
      <dc:creator>xybal</dc:creator>
      <dc:date>2010-06-14T11:23:48Z</dc:date>
    </item>
    <item>
      <title>Re: Strange behaviour with network interface</title>
      <link>https://communities.vmware.com/t5/VI-VMware-ESX-3-5-Discussions/Strange-behaviour-with-network-interface/m-p/836331#M42922</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've found the solution.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In fact my virtual switch was limited to 32 ports and my VM was the 33.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've put 120 virtual ports and rebooted and now all is OK &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Jun 2010 12:05:43 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VI-VMware-ESX-3-5-Discussions/Strange-behaviour-with-network-interface/m-p/836331#M42922</guid>
      <dc:creator>xybal</dc:creator>
      <dc:date>2010-06-30T12:05:43Z</dc:date>
    </item>
  </channel>
</rss>

