<?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: Advanced server 7.3A/B can't find domain controller in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/advanced-server-7-3a-b-can-t-find-domain-controller/m-p/3918946#M80999</link>
    <description>Anton,&lt;BR /&gt;your guess is right, besides the software-updates (VMS-patches) I also installed new network-cards to use LAN failover. The new cards are defined as LLA-0, this has also been modified in the logicals which advanced server uses (PWRK$NBDAEMON_DEVICE and PWRK$KNBDAEMON_DEVICE) to point to LLA0 instead of EIA0 (the KNBDAEMON-process seems to work fine with these settings). This change was also one of my guesses which could have influenced the problem, therefore I have modified it back test-wise, but that didn't succeed.&lt;BR /&gt;In my whole paper documentation about pathworks problems I found an old article about a similar problem (but with an external Windows NT server as domain controller) where the solution was to add a LMHOSTS entry for the PDC. I will try this the next time when I'm able to restart Pathworks (it is used in a 7x24 production area here). In the moment, I can still live with the mentioned workaround.</description>
    <pubDate>Mon, 08 Jan 2007 07:38:30 GMT</pubDate>
    <dc:creator>Michael Kloth</dc:creator>
    <dc:date>2007-01-08T07:38:30Z</dc:date>
    <item>
      <title>Advanced server 7.3A/B can't find domain controller</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/advanced-server-7-3a-b-can-t-find-domain-controller/m-p/3918942#M80995</link>
      <description>As every year, I used the non-production usage time of our servers for updates. I have updated our Alphaserver-VMS-Cluster running V7.3-2 with the actual VMS-Patches (Update-Patch 900 and others) and UCX V5.4 ECO 6. After that, everything works fine except Pathworks/Advanced server. The actual version is V7.3A4 and the problem is that the server can't reach his DC :&lt;BR /&gt;$ Admin show users&lt;BR /&gt;gives "%PWRK-E-DCNOTFND, cannot find Primary Domain Controller for "CSPWRK01" "&lt;BR /&gt;although the server itself has been set up as PDC for that domain.&lt;BR /&gt;I updated Advanced server to V7.3B and also reconfigured it, but that didn't suceed.&lt;BR /&gt;The pathworks-logfiles do not give any special error-message, all required processes are running.&lt;BR /&gt;Only workaround is in the moment that users who want to connect to any share have to use the username administrator (and the password of course).&lt;BR /&gt;Any hints where I can search ?</description>
      <pubDate>Fri, 29 Dec 2006 07:35:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/advanced-server-7-3a-b-can-t-find-domain-controller/m-p/3918942#M80995</guid>
      <dc:creator>Michael Kloth</dc:creator>
      <dc:date>2006-12-29T07:35:30Z</dc:date>
    </item>
    <item>
      <title>Re: Advanced server 7.3A/B can't find domain controller</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/advanced-server-7-3a-b-can-t-find-domain-controller/m-p/3918943#M80996</link>
      <description>Does your domain have either WinXP or Win2K3 machines present that were not there last year ?&lt;BR /&gt;IIRC, Pathworks can only be a member server, not a Domain Controller, in an XP/W2k3 domain.&lt;BR /&gt;Something to do with Ms moving the goal posts and not telling anyone where they were moved to. &lt;BR /&gt;JT:</description>
      <pubDate>Sat, 30 Dec 2006 08:04:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/advanced-server-7-3a-b-can-t-find-domain-controller/m-p/3918943#M80996</guid>
      <dc:creator>John Travell</dc:creator>
      <dc:date>2006-12-30T08:04:42Z</dc:date>
    </item>
    <item>
      <title>Re: Advanced server 7.3A/B can't find domain controller</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/advanced-server-7-3a-b-can-t-find-domain-controller/m-p/3918944#M80997</link>
      <description>Hello John,&lt;BR /&gt;thanks for your answer.&lt;BR /&gt;The pathworks-domain structure we are using is a very simple one : the pathworks-server is set up as PDC for CSPWRK01 (no BDC exists for that domain), there are no other domain members. The XP-clients which want to map a share on this server are member of another domain.&lt;BR /&gt;This configuration worked fine before I made the system updates last week.</description>
      <pubDate>Tue, 02 Jan 2007 09:44:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/advanced-server-7-3a-b-can-t-find-domain-controller/m-p/3918944#M80997</guid>
      <dc:creator>Michael Kloth</dc:creator>
      <dc:date>2007-01-02T09:44:46Z</dc:date>
    </item>
    <item>
      <title>Re: Advanced server 7.3A/B can't find domain controller</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/advanced-server-7-3a-b-can-t-find-domain-controller/m-p/3918945#M80998</link>
      <description>Micheal,&lt;BR /&gt;&lt;BR /&gt;You didn't add or modify any hardware in this update period, do you ?&lt;BR /&gt;There is also no modification made to the netwerk ?&lt;BR /&gt;&lt;BR /&gt;AvR</description>
      <pubDate>Fri, 05 Jan 2007 11:12:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/advanced-server-7-3a-b-can-t-find-domain-controller/m-p/3918945#M80998</guid>
      <dc:creator>Anton van Ruitenbeek</dc:creator>
      <dc:date>2007-01-05T11:12:20Z</dc:date>
    </item>
    <item>
      <title>Re: Advanced server 7.3A/B can't find domain controller</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/advanced-server-7-3a-b-can-t-find-domain-controller/m-p/3918946#M80999</link>
      <description>Anton,&lt;BR /&gt;your guess is right, besides the software-updates (VMS-patches) I also installed new network-cards to use LAN failover. The new cards are defined as LLA-0, this has also been modified in the logicals which advanced server uses (PWRK$NBDAEMON_DEVICE and PWRK$KNBDAEMON_DEVICE) to point to LLA0 instead of EIA0 (the KNBDAEMON-process seems to work fine with these settings). This change was also one of my guesses which could have influenced the problem, therefore I have modified it back test-wise, but that didn't succeed.&lt;BR /&gt;In my whole paper documentation about pathworks problems I found an old article about a similar problem (but with an external Windows NT server as domain controller) where the solution was to add a LMHOSTS entry for the PDC. I will try this the next time when I'm able to restart Pathworks (it is used in a 7x24 production area here). In the moment, I can still live with the mentioned workaround.</description>
      <pubDate>Mon, 08 Jan 2007 07:38:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/advanced-server-7-3a-b-can-t-find-domain-controller/m-p/3918946#M80999</guid>
      <dc:creator>Michael Kloth</dc:creator>
      <dc:date>2007-01-08T07:38:30Z</dc:date>
    </item>
  </channel>
</rss>

