<?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: xdmcp problem in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/xdmcp-problem/m-p/4888022#M562483</link>
    <description>Try to connect with an X terminal or eXceed or ... just in case the reflection X is not messed up.&lt;BR /&gt;&lt;BR /&gt;- Bob</description>
    <pubDate>Fri, 25 Feb 2005 10:49:33 GMT</pubDate>
    <dc:creator>B. Hulst</dc:creator>
    <dc:date>2005-02-25T10:49:33Z</dc:date>
    <item>
      <title>xdmcp problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/xdmcp-problem/m-p/4888015#M562476</link>
      <description>Hello&lt;BR /&gt;&lt;BR /&gt;since 2 days we have problems to establish CDE sessions on a zx6000 (11.23) with ReflectionX. The same problems appear with a suse-9.1-box while there are no problems with 2 old hp-ux-boxes (10.20). the Xerrors file in /var/dt shows &lt;BR /&gt;&lt;BR /&gt;error (pid 4000): Server open attempt #0 failed for xxx.intern:0, giving up&lt;BR /&gt;&lt;BR /&gt;or&lt;BR /&gt;&lt;BR /&gt;error (pid 4056): display xxx.intern:0 could not be initialized, server may be grabbed.&lt;BR /&gt;&lt;BR /&gt;I checked all the previous issues here with similar problems but couldn't get a solution.&lt;BR /&gt;&lt;BR /&gt;any good ideas?  &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 25 Feb 2005 06:58:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/xdmcp-problem/m-p/4888015#M562476</guid>
      <dc:creator>Michael Koops_1</dc:creator>
      <dc:date>2005-02-25T06:58:45Z</dc:date>
    </item>
    <item>
      <title>Re: xdmcp problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/xdmcp-problem/m-p/4888016#M562477</link>
      <description>try restarsting the dtlogin.rc in HP-UX.&lt;BR /&gt;&lt;BR /&gt;#/sbin/init.d/dtlogin.rc stop&lt;BR /&gt;#/sbin/init.d/dtlogin.rc start&lt;BR /&gt;&lt;BR /&gt;regards&lt;BR /&gt;Govinda.&lt;BR /&gt;</description>
      <pubDate>Fri, 25 Feb 2005 07:07:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/xdmcp-problem/m-p/4888016#M562477</guid>
      <dc:creator>Govinda_1</dc:creator>
      <dc:date>2005-02-25T07:07:45Z</dc:date>
    </item>
    <item>
      <title>Re: xdmcp problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/xdmcp-problem/m-p/4888017#M562478</link>
      <description>Hi Govinda&lt;BR /&gt;&lt;BR /&gt;i did several times.&lt;BR /&gt;&lt;BR /&gt;Michael</description>
      <pubDate>Fri, 25 Feb 2005 07:14:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/xdmcp-problem/m-p/4888017#M562478</guid>
      <dc:creator>Michael Koops_1</dc:creator>
      <dc:date>2005-02-25T07:14:15Z</dc:date>
    </item>
    <item>
      <title>Re: xdmcp problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/xdmcp-problem/m-p/4888018#M562479</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;When you are sure no one is logged onto the server then kill -9 all the running processes called dtsession. Then stop &amp;amp; start as suggested above. :-)&lt;BR /&gt;&lt;BR /&gt;If that does not work, then brute force:&lt;BR /&gt;&lt;BR /&gt;#/sbin/init.d/dtlogin.rc stop&lt;BR /&gt;&lt;BR /&gt;ps -ef | grep dt&lt;BR /&gt;kill all the process left running there&lt;BR /&gt;which have dt in the begin name (dtlogin, dtsession, etc... You can find more suggestion in /usr/dt/bin/dt*&lt;BR /&gt;&lt;BR /&gt;#/sbin/init.d/dtlogin.rc start&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Bob</description>
      <pubDate>Fri, 25 Feb 2005 10:14:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/xdmcp-problem/m-p/4888018#M562479</guid>
      <dc:creator>B. Hulst</dc:creator>
      <dc:date>2005-02-25T10:14:05Z</dc:date>
    </item>
    <item>
      <title>Re: xdmcp problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/xdmcp-problem/m-p/4888019#M562480</link>
      <description>Can you resolve  xxx.intern properly?? to and fro?? Also run dr_dt and check for errors.&lt;BR /&gt;&lt;BR /&gt;What does ~/.dt/errorlog and startlog says??&lt;BR /&gt;&lt;BR /&gt;Anil</description>
      <pubDate>Fri, 25 Feb 2005 10:29:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/xdmcp-problem/m-p/4888019#M562480</guid>
      <dc:creator>RAC_1</dc:creator>
      <dc:date>2005-02-25T10:29:52Z</dc:date>
    </item>
    <item>
      <title>Re: xdmcp problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/xdmcp-problem/m-p/4888020#M562481</link>
      <description>This sounds like a name resolution problem. The HP boxes seem to be able to resolve, forward and reverse, the Reflection X box while the zx6000 and the suse box can't.&lt;BR /&gt;&lt;BR /&gt;The hint is the error message "display xxx.intern:0 could not be initialized"&lt;BR /&gt;&lt;BR /&gt;I am not sure if that is a DNS problem or not. &lt;BR /&gt;&lt;BR /&gt;From the Reflection X box just try to telenet to the zx6000 box and if that works do a who -mT to see who the box really thinks you are. Name and address. Verify that name and address is correct for your Reflection X box. &lt;BR /&gt;</description>
      <pubDate>Fri, 25 Feb 2005 10:41:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/xdmcp-problem/m-p/4888020#M562481</guid>
      <dc:creator>John Dvorchak</dc:creator>
      <dc:date>2005-02-25T10:41:17Z</dc:date>
    </item>
    <item>
      <title>Re: xdmcp problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/xdmcp-problem/m-p/4888021#M562482</link>
      <description>@Bob&lt;BR /&gt;&lt;BR /&gt;i rebooted the machine several times to get clean processes but it didn't help&lt;BR /&gt;&lt;BR /&gt;@Anil&lt;BR /&gt;&lt;BR /&gt;the name resolution works in both directions without problem. dr_dt shows no warnings and no errors. the ~/.dt/-logs didn't show anything because i didn't get a login-screen.&lt;BR /&gt;&lt;BR /&gt;thanx&lt;BR /&gt;Michael</description>
      <pubDate>Fri, 25 Feb 2005 10:45:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/xdmcp-problem/m-p/4888021#M562482</guid>
      <dc:creator>Michael Koops_1</dc:creator>
      <dc:date>2005-02-25T10:45:01Z</dc:date>
    </item>
    <item>
      <title>Re: xdmcp problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/xdmcp-problem/m-p/4888022#M562483</link>
      <description>Try to connect with an X terminal or eXceed or ... just in case the reflection X is not messed up.&lt;BR /&gt;&lt;BR /&gt;- Bob</description>
      <pubDate>Fri, 25 Feb 2005 10:49:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/xdmcp-problem/m-p/4888022#M562483</guid>
      <dc:creator>B. Hulst</dc:creator>
      <dc:date>2005-02-25T10:49:33Z</dc:date>
    </item>
    <item>
      <title>Re: xdmcp problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/xdmcp-problem/m-p/4888023#M562484</link>
      <description>@John&lt;BR /&gt;&lt;BR /&gt;telnet works and who -mT shows xxx.intern, so everything seems to be as it should&lt;BR /&gt;&lt;BR /&gt;thanx&lt;BR /&gt;Michael</description>
      <pubDate>Fri, 25 Feb 2005 10:52:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/xdmcp-problem/m-p/4888023#M562484</guid>
      <dc:creator>Michael Koops_1</dc:creator>
      <dc:date>2005-02-25T10:52:06Z</dc:date>
    </item>
    <item>
      <title>Re: xdmcp problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/xdmcp-problem/m-p/4888024#M562485</link>
      <description>Not sure if this will work but ...&lt;BR /&gt;&lt;BR /&gt;cp /usr/dt/config/Xconfig -&amp;gt; /etc/dt/config/Xconfig ...&lt;BR /&gt;&lt;BR /&gt;vi -&amp;gt; set&lt;BR /&gt;&lt;BR /&gt;Dtlogin*grabServer: False&lt;BR /&gt;&lt;BR /&gt;Dtlogin*terminateServer: True&lt;BR /&gt;&lt;BR /&gt;wq!&lt;BR /&gt;&lt;BR /&gt;restart X .... any difference ?&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 25 Feb 2005 10:52:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/xdmcp-problem/m-p/4888024#M562485</guid>
      <dc:creator>Alex Glennie</dc:creator>
      <dc:date>2005-02-25T10:52:46Z</dc:date>
    </item>
    <item>
      <title>Re: xdmcp problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/xdmcp-problem/m-p/4888025#M562486</link>
      <description>@Bob&lt;BR /&gt;&lt;BR /&gt;we tried from every reflX-equipped pc and some linux-boxes and got always the same hangup&lt;BR /&gt;&lt;BR /&gt;Michael</description>
      <pubDate>Fri, 25 Feb 2005 11:00:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/xdmcp-problem/m-p/4888025#M562486</guid>
      <dc:creator>Michael Koops_1</dc:creator>
      <dc:date>2005-02-25T11:00:09Z</dc:date>
    </item>
    <item>
      <title>Re: xdmcp problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/xdmcp-problem/m-p/4888026#M562487</link>
      <description>What is there in /var/adm/inetd.sec file??&lt;BR /&gt;Any restrictions there??&lt;BR /&gt;&lt;BR /&gt;Anil</description>
      <pubDate>Fri, 25 Feb 2005 11:09:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/xdmcp-problem/m-p/4888026#M562487</guid>
      <dc:creator>RAC_1</dc:creator>
      <dc:date>2005-02-25T11:09:07Z</dc:date>
    </item>
    <item>
      <title>Re: xdmcp problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/xdmcp-problem/m-p/4888027#M562488</link>
      <description>Hi everybody&lt;BR /&gt;&lt;BR /&gt;friday evening i tried to login from my home-pc (via isdn and router). absolutely no problems!!! this morning i got in on the second attempt. my collegues were successful too after some attempts. i didn't change anything in the configuration compared to friday afternoon. in my view it looks like a timing problem, but who is to slow or to fast? keep in mind that we have no problems with our old hpux-boxes.&lt;BR /&gt;&lt;BR /&gt;greetings&lt;BR /&gt;michael&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 28 Feb 2005 03:56:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/xdmcp-problem/m-p/4888027#M562488</guid>
      <dc:creator>Michael Koops_1</dc:creator>
      <dc:date>2005-02-28T03:56:12Z</dc:date>
    </item>
    <item>
      <title>Re: xdmcp problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/xdmcp-problem/m-p/4888028#M562489</link>
      <description>@anil&lt;BR /&gt;&lt;BR /&gt;just one line in inetd.sec:&lt;BR /&gt;&lt;BR /&gt;dtspc allow&lt;BR /&gt;&lt;BR /&gt;michael</description>
      <pubDate>Mon, 28 Feb 2005 04:06:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/xdmcp-problem/m-p/4888028#M562489</guid>
      <dc:creator>Michael Koops_1</dc:creator>
      <dc:date>2005-02-28T04:06:51Z</dc:date>
    </item>
    <item>
      <title>Re: xdmcp problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/xdmcp-problem/m-p/4888029#M562490</link>
      <description>@alex&lt;BR /&gt;&lt;BR /&gt;the changes in Xconfig didn't make any difference&lt;BR /&gt;&lt;BR /&gt;michael</description>
      <pubDate>Tue, 01 Mar 2005 11:37:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/xdmcp-problem/m-p/4888029#M562490</guid>
      <dc:creator>Michael Koops_1</dc:creator>
      <dc:date>2005-03-01T11:37:56Z</dc:date>
    </item>
    <item>
      <title>Re: xdmcp problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/xdmcp-problem/m-p/4888030#M562491</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Try using a network sniffer to see what actually is going between the two hosts.&lt;BR /&gt;&lt;BR /&gt;For example ethereal has good analyzing capabilities to see perhaps why the connection does not get establish.&lt;BR /&gt;&lt;BR /&gt;It helped me a few times.&lt;BR /&gt;&lt;BR /&gt;Just put a laptop with windows ethereal and listen the two hosts' traffic. And then start search in the output for port 6000 (the standard X11 port)&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Bob</description>
      <pubDate>Wed, 02 Mar 2005 02:20:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/xdmcp-problem/m-p/4888030#M562491</guid>
      <dc:creator>B. Hulst</dc:creator>
      <dc:date>2005-03-02T02:20:17Z</dc:date>
    </item>
    <item>
      <title>Re: xdmcp problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/xdmcp-problem/m-p/4888031#M562492</link>
      <description>Hi everybody&lt;BR /&gt;&lt;BR /&gt;yesterday we solved our problem:&lt;BR /&gt;&lt;BR /&gt;we found out that one of our routers runs a dns-server with factory default configuration. this dns-server responds to reverse lookup requests and provides wrong hostnames so that reflectionX couldn't work properly.&lt;BR /&gt;&lt;BR /&gt;thank you all for your assistance&lt;BR /&gt;Michael</description>
      <pubDate>Fri, 04 Mar 2005 03:12:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/xdmcp-problem/m-p/4888031#M562492</guid>
      <dc:creator>Michael Koops_1</dc:creator>
      <dc:date>2005-03-04T03:12:51Z</dc:date>
    </item>
    <item>
      <title>Re: xdmcp problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/xdmcp-problem/m-p/4888032#M562493</link>
      <description>see above</description>
      <pubDate>Fri, 04 Mar 2005 03:16:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/xdmcp-problem/m-p/4888032#M562493</guid>
      <dc:creator>Michael Koops_1</dc:creator>
      <dc:date>2005-03-04T03:16:11Z</dc:date>
    </item>
  </channel>
</rss>

