<?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: Clustred servers see remote printer differently in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/clustred-servers-see-remote-printer-differently/m-p/2952102#M577526</link>
    <description>John,&lt;BR /&gt;&lt;BR /&gt;Thanks for the reponse. I found the problem. The particular printer I was trying to reach had a very old default gateway assigned in the network devices control panel in sam. I switched it to the current default gateway and immediately was able to print. Thanks again. - JD</description>
    <pubDate>Tue, 15 Apr 2003 22:04:11 GMT</pubDate>
    <dc:creator>John Donaldson</dc:creator>
    <dc:date>2003-04-15T22:04:11Z</dc:date>
    <item>
      <title>Clustred servers see remote printer differently</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/clustred-servers-see-remote-printer-differently/m-p/2952100#M577524</link>
      <description>I have two clustered K Class servers on one subnet and a printer on another subnet connected via a frame relay link. I have my routers configured correctly so that I can ping and traceroute to the printer from my 2000 workstation, the router, and my secondary HP-UX server that is NOT running the package. I cannot ping or traceroute from the primary server running the serviceguard package and my database that I need to print from. How do I get my primary server to clear and update it's routing table to know the correct route to my other subnet?</description>
      <pubDate>Tue, 15 Apr 2003 20:20:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/clustred-servers-see-remote-printer-differently/m-p/2952100#M577524</guid>
      <dc:creator>John Donaldson</dc:creator>
      <dc:date>2003-04-15T20:20:53Z</dc:date>
    </item>
    <item>
      <title>Re: Clustred servers see remote printer differently</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/clustred-servers-see-remote-printer-differently/m-p/2952101#M577525</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;The only difference might be that your primary server is running a package and could have a package IP address, depending on how you have configured it.  I can't see how that would really make a difference, unless the package IP is conflicting with something else, and that would be pretty obvious.&lt;BR /&gt;&lt;BR /&gt;Do both boxes have the same default route in their routing tables?  Can you give us some examples of IP addresses and maybe the output from 'netstat -rn' from each box?&lt;BR /&gt;&lt;BR /&gt;JP&lt;BR /&gt;</description>
      <pubDate>Tue, 15 Apr 2003 20:30:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/clustred-servers-see-remote-printer-differently/m-p/2952101#M577525</guid>
      <dc:creator>John Poff</dc:creator>
      <dc:date>2003-04-15T20:30:20Z</dc:date>
    </item>
    <item>
      <title>Re: Clustred servers see remote printer differently</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/clustred-servers-see-remote-printer-differently/m-p/2952102#M577526</link>
      <description>John,&lt;BR /&gt;&lt;BR /&gt;Thanks for the reponse. I found the problem. The particular printer I was trying to reach had a very old default gateway assigned in the network devices control panel in sam. I switched it to the current default gateway and immediately was able to print. Thanks again. - JD</description>
      <pubDate>Tue, 15 Apr 2003 22:04:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/clustred-servers-see-remote-printer-differently/m-p/2952102#M577526</guid>
      <dc:creator>John Donaldson</dc:creator>
      <dc:date>2003-04-15T22:04:11Z</dc:date>
    </item>
  </channel>
</rss>

