<?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: bind X to another network interface in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/bind-x-to-another-network-interface/m-p/3516422#M219115</link>
    <description>How could I simply bind it to localhost?</description>
    <pubDate>Fri, 01 Apr 2005 14:52:12 GMT</pubDate>
    <dc:creator>jamesps</dc:creator>
    <dc:date>2005-04-01T14:52:12Z</dc:date>
    <item>
      <title>bind X to another network interface</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bind-x-to-another-network-interface/m-p/3516420#M219113</link>
      <description>How do I bind the X server to another interface? It is currently bound to my primary nic which is lan0. When this interface loses connectivity, CDE hangs and I am trying to avoid that. I could bind it to localhost and never have the same problem again. Any advices? Thanks!&lt;BR /&gt;&lt;BR /&gt;James.</description>
      <pubDate>Fri, 01 Apr 2005 13:47:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bind-x-to-another-network-interface/m-p/3516420#M219113</guid>
      <dc:creator>jamesps</dc:creator>
      <dc:date>2005-04-01T13:47:36Z</dc:date>
    </item>
    <item>
      <title>Re: bind X to another network interface</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bind-x-to-another-network-interface/m-p/3516421#M219114</link>
      <description>&lt;BR /&gt;I personally would replace my primary nic card if I was having that many problems.&lt;BR /&gt;&lt;BR /&gt;live free or die&lt;BR /&gt;harry d brown jr</description>
      <pubDate>Fri, 01 Apr 2005 14:24:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bind-x-to-another-network-interface/m-p/3516421#M219114</guid>
      <dc:creator>harry d brown jr</dc:creator>
      <dc:date>2005-04-01T14:24:06Z</dc:date>
    </item>
    <item>
      <title>Re: bind X to another network interface</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bind-x-to-another-network-interface/m-p/3516422#M219115</link>
      <description>How could I simply bind it to localhost?</description>
      <pubDate>Fri, 01 Apr 2005 14:52:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bind-x-to-another-network-interface/m-p/3516422#M219115</guid>
      <dc:creator>jamesps</dc:creator>
      <dc:date>2005-04-01T14:52:12Z</dc:date>
    </item>
    <item>
      <title>Re: bind X to another network interface</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bind-x-to-another-network-interface/m-p/3516423#M219116</link>
      <description>&lt;BR /&gt;Are you using cde on the console?&lt;BR /&gt;&lt;BR /&gt;if not, then you must replace your nic card, cable, or switch ports.&lt;BR /&gt;&lt;BR /&gt;how are you starting CDE?&lt;BR /&gt;&lt;BR /&gt;live free or die&lt;BR /&gt;harry d brown jr</description>
      <pubDate>Sat, 02 Apr 2005 07:10:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bind-x-to-another-network-interface/m-p/3516423#M219116</guid>
      <dc:creator>harry d brown jr</dc:creator>
      <dc:date>2005-04-02T07:10:24Z</dc:date>
    </item>
    <item>
      <title>Re: bind X to another network interface</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bind-x-to-another-network-interface/m-p/3516424#M219117</link>
      <description>Xwindows is critically attached to networking, not a specific NIC. As long as you are using DNS, loss of your network will hang CDE, regardless of whether you are just working locally. To reduce your dependence on networking, edit the /etc/nsswitch.conf file and change the order of hostname resolution:&lt;BR /&gt; &lt;BR /&gt;hosts:          files   [NOTFOUND=continue UNAVAIL=continue] dns [NOTFOUND=retur&lt;BR /&gt;n UNAVAIL=continue TRYAGAIN=return]&lt;BR /&gt; &lt;BR /&gt;Since /etc/hosts should have both localhost and   loopback (127.0.0.1) as well as your hostname, loss of the network should only affect remote access.</description>
      <pubDate>Sat, 02 Apr 2005 21:22:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bind-x-to-another-network-interface/m-p/3516424#M219117</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2005-04-02T21:22:07Z</dc:date>
    </item>
    <item>
      <title>Re: bind X to another network interface</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bind-x-to-another-network-interface/m-p/3516425#M219118</link>
      <description>I am using CDE on the local console. CDE starts at boot normally via dtlogin.rc script. Everything works normally.&lt;BR /&gt;&lt;BR /&gt;The problem I was experiencing was for example when I unplugged the network cable. I wanted the CDE to "use" the localhost instead of "looking out" for the external lan0 interface.&lt;BR /&gt;&lt;BR /&gt;I will try changing the nsswitch.conf as Bill suggested.&lt;BR /&gt;&lt;BR /&gt;Thank you all for your replies!&lt;BR /&gt;&lt;BR /&gt;James</description>
      <pubDate>Mon, 04 Apr 2005 11:24:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bind-x-to-another-network-interface/m-p/3516425#M219118</guid>
      <dc:creator>jamesps</dc:creator>
      <dc:date>2005-04-04T11:24:11Z</dc:date>
    </item>
  </channel>
</rss>

