<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>VMware Communities: Message List - Problem w/ 2 NICs on Guest</title>
    <link>http://communities.vmware.com/community/vmtn/server/server1?view=discussions</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    <pubDate>Fri, 25 Apr 2008 11:47:37 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2008-04-25T11:47:37Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>Problem w/ 2 NICs on Guest</title>
      <link>http://communities.vmware.com/message/925626?tstart=0#925626</link>
      <description>We've got a linux VM (redhat 4.5) web server running with 2 nics running on a HP BL460C host with two physical NICs (also running on Redhat 4.5). &lt;br /&gt;
1 nic (eth1) is used for administative purposes so we can reach the machine from within our network. &lt;br /&gt;
The other nic (eth0) is configured so the webserver can be reached from the internet. &lt;br /&gt;
After rebooting only the first nic seems to work properly. I can reach the server from our network. &lt;br /&gt;
The http website cannot be reached. It looks like the request is coming in, but the response is sent to the other card. &lt;br /&gt;
&lt;br /&gt;
After using the command "/sbin/ifup eth0 1" to bring up the second network card the website can be reached, but making a connection to the server from our network is no longer possible.&lt;br /&gt;
eth0 is bridged to vmnet0, which is attached on the host to eth1.286 (VLAN)&lt;br /&gt;
eth1 is bridged to vmnet1, which is attached on the host to eht1&lt;br /&gt;
&lt;br /&gt;
We have a similar setup on another machine, same version same software, same config, but that seems to work quite allright!&lt;br /&gt;
&lt;br /&gt;
It seems like there's a routing issue. Anyone familiar with this problem?</description>
      <pubDate>Fri, 25 Apr 2008 11:41:57 GMT</pubDate>
      <author>rkrewinkel</author>
      <guid>http://communities.vmware.com/message/925626?tstart=0#925626</guid>
      <dc:date>2008-04-25T11:41:57Z</dc:date>
      <clearspace:dateToText>1 year, 7 months ago</clearspace:dateToText>
    </item>
  </channel>
</rss>

