Conference noted::pwv50ift

4207.0. " Accounts.lmx not replicating to PW 5.0d member and PW 5.0d backup" by NETRIX::"frais::[email protected]" (frais::arnold) Fri Mar 14 1997 10:21

PRODUCT or COMPONENT:  PATHWORKS for VMS V. 5.0-430D on all Servers
                 OpenVMS(ALPHA) V6.2 on Alpha 400 4/233 128 MB memory
                 MDC's VMS 6.1 on Vax 3100-20 with 32MB memory
                  UCX Version 3.3 ECO 12 on all Systems
                       Decnet Area 10.x on all Pathworks Server
                       designated router is also a VMS system
                       IP Network 172.16.x.x mask:255.255.0.0 on all
                       systems


Customer has a Alpha 400/4/233 as PDC and one BDC and about 20 MDC's on the
Domain Vorstand.
All System running VMS with Pathworks (DECNET and TCP/IP enabled)
and UCX.Every couple of hours or so the BDC or the MDC's lose
 UAS synch with the PDC system and cannot get it back until 
a Pathworks restart on both systems the PDC and the MDC (or BDC).     
When changing the pathworks domain role for example from member
 to standalone and back to member with the command
 $ Accounts /role:member (for example), the NETLOGON service fails
 to start with an Error Message (Service Control is Busy).
Also, even with NETLOGON running on the failing MDC or BDC, using 
$ NET ACCOUNTS /SYNC would not sync with the PDC.
The error reported by NET ERROR is:
NET3210:  Failed to authenticate with AVRZ38, the domain controller
 for domain VORSTAND.                   
I have set the Account Guest, PDChostname, MDChostname to a zero
 password with the command:
AVRZ38> net user GUEST * <return> <return>
AVRZ38> net user AVRZ38 * <return> <return>
AVRZ38> net user VDVV04 * <return> <return>                           
VDVV04> net user GUEST * <return> <return>
VDVV04> net user AVRZ38 * <return> <return>
VDVV04> net user VDVV04 * <return> <return>

AVRZ is the Primary Domain Controller
VDVV04 is one of the Member Domain Controller

If the Systems lose the Pathworks synch. I can connect the PDC and
 the MDC with one Twisted Pair Cable (for example) but the systems
 cannot get the synch. back until a Pathworks restart on both systems.

I have some IRIS trace on FRSAS:: (address 63.139) DECNET Default
 Account.
ADMMEM-B.DWC   I wanted to change the role from the PW Admin Menue
               on node VDVV04 (Failed to start netlogon or no
               synch. Accounts.lmx!!)

MEMBER-B.DWC   I wanted to change the role with the command
               $ Net accounts/role:member on node VDVV04.
               (Failed to start netlogon or no synch. Accounts.lmx!!)

PWREST-B.DWC  I wanted to change the role after a pathworks restart
               on the MDC system (Failed to start Netlogon
               or no synch. Accounts.lmx)
                          
PWREB-B.DWC   I wanted to change the role after a system  reboot
               on the MDC system (Failed to start 
               Netlogon or no synch. Accounts.lmx)                  

Synch-B.DWC  I did a $ Net Accounts/synch on the MDC after reboot it
              doesn't work.

Member-O.DWC I wanted to change the role on the MDC after a pathworks
              restart  on both system the PDC and the MDC. (It works)

Synch-O.DWC  I did a $ Net Accounts/synch on the MDC after a pathworks
              restart on both system the PDC and the MDC. (It works)



thanks in advance for any suggestion.
Stefan Arnold   
A1 mail address FRAIS::ARNOLD
Vaxmail FRSAS::ARNOLD

[Posted by WWW Notes gateway]

    I believe this got fixed in e eco 1.
    I will let Rob E have a look at your note,
    he worked on this.
    
    Adrie

    I'd a quick look at you're problem description but need some more
    details.
    
    	- The exact configuration of the PDC. Is it a cluster,
    	  what ethernet controllers/fddi? 
    	  Multiple controllers ?
    	  Which transports enabled ?
    	  If decnet node number /area numbers
    	  If tcpi subnets/subnet masks
    
    	- Exact config of the bdc/members. Same questions as above.
    
    	- How is the network topologie
    
    	- Enable debug=yes in lanman.ini on the member/bdc wich fails
    	  to start the netlon service.
    	  Get the trace files in the pwrk$lmlogs directory. Make a
    	  corresponding iris trace
    
    	Also escalate this to get the proper attention.
    
    If the bdc/member which fails to authenticate is a cluster then we've a
    solution for this.

Hi,
the Customer has no Cluster. All Pathworks server are
standalone VMS systems.
The Pathworks Servers have only one Ethernet Connection
( No multiple controller, no FDDI connection)
On all Servers are DECnet and TCP/IP transport enabled -
Netbui is not enabled.
All systems are in decnet area 10.x. Designated router
is also a VMS system (I think its a Vaxstation 3100).
All systems running Decnet Phase IV.
The IP network is 172.16.x.x netmask 255.255.0.0
All Pathworks Servers are connected over twisted pair on
a few synoptics repeater. The synoptics repeater are connected
over twisted pair or over fiber optic links on a cisco catalyst.

I hope this help.

regards
Stefan 



[Posted by WWW Notes gateway]

    FRSAS or 63.139 is not reachable, please fix it.
    Rob