[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference noted::pwv50ift

Title:	Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server
Notice:	Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server
Moderator:	CPEEDY::KENNEDY

Created:	Fri Dec 18 1992
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	4319
Total number of notes:	18478

4165.0. "Net logon on server gives "error 86"" by RTOMS::KARNBAUMW () Thu Feb 20 1997 09:33

    hi,
    
    customer has problems with synchronisation between PDC and BDC
    all PW V5.0D ECO3.
    Sometimes BDC loose synchronisation, although network traffic
    seems to be not too heavy. I checked all LM accounts and VMS
    accounts with him, also the time on the different servers.
    The BDC does not seem to be authenticated by the PDC during
    changing serverrole from standalone to backup controller.
    As the BDC is in Standalone mode, he can logon within VMS
    as any user except with the username of the server.
    $ net logon servername password
    gives "error 86 the network password is incorrect"
    We set a new password and even deleted and recreated the
    account - always with the same error.
    Is there anything else i can check, as i do not really want
    to create a new 'accounts.lmx' because customer would loose
    permissions for the shares on this computer.
    
    thanks for any input
    
    Walter Karnbaum
    
    (CSC Munich)

T.R	Title	User	Date	Lines
4165.1	GUEST password needs resetting	VMSNET::P_NUNEZ	`Thu Feb 20 1997 10:04`	12
	Walter, Just for grins, try: $ @sys$startup:pwrk$define_commands $ lmuser -mp "" guest $ net logon <server> <pswd> I duplicated the error 86 like you did (net logon <server>), cleared the guest account password, and tried again - it worked. Paul
4165.2	now gets NET3210 on BDC	RTOMS::KARNBAUMW	`Fri Feb 21 1997 03:10`	27
	Hallo Paul, thanks for your reply. I set the guest account on BDC and PDC with 'lmuser ...' , but the problem was, that the file 'accounts.lmx' did not get updated for nearly 2 minutes. As the revision date changed, the standalone controller logged you on, of course without validation. Now the problem still exists, as the BDC cannot start the Netlogon Service. "NET3210 failed to authenticate with PDC" I set up the Server accounts on BDC and PDC with same passwords and in group servers. Still the problem exists and the LM account of the BDC gets login fails on the PDC. Also on the PDC it takes nearly 2 minutes till the accounts.lmx gets updated. Can there be a timeout problem or any other BDC trying to validate the BDC ? There are 3 BDC in the net. How can i troubleshoot this any further ? (debug=yes) in lanman.ini ? thanks for any advise Walter
4165.3	Look for clues...	VMSNET::P_NUNEZ	`Fri Feb 21 1997 09:55`	32
	Walter, Check for NETLOGON/UAS errors reported by $ ADMIN/ANALYZE and $ NET ERROR /REVERSE on both the PDC and BDC. Is the PDC or the BDC in a cluster? There are known problems with starting NETLOGON in a cluster and with account replication (but I'm not sure if those apply only if the PDC is WinNT). These are fixed in v5.0E. I believe they also recently discovered a problem in this area if using DECnet over FDDI... Finally, the output from $ NET HELPMSG 3210: NET3210: Failed to authenticate with *, the domain controller for domain *. EXPLANATION This server was denied access to the user accounts database at the primary domain controller. Until this problem is corrected, the server can't synchronize user account information with the primary domain controller. ACTION Stop and restart the Netlogon service at this server. Paul