[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| 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 |
4311.0. "Session Setup for PW server Failed to Authenticate" by VMSNET::DMCFARLAND (still TurboMom[tm]...) Fri May 30 1997 18:26
I am bain-dread at this point and need some help. This may not be
the correct notes conference, but I haven't gotten anything else
right today, either...
PW v5.0c eco3 server (yes, it needs upgrading (but this was working
previously...) that is a BDC in a domain with WNT 4.0 as PDC.
The WNT Event Log is getting messages every few minutes.
Event ID: 5722 from Source Netlogon
The session setup from the computer WSA146 failed to authenticate. The
name of the account referenced in the security database is WSA146. The
following error occurred:
Access is denied.
If I try to sync the domain, the same message gets sent to the WNT
Event Log. I found an earlier problem that PWRK$DEFAULT was disusered.
I set that to nodisuser nopassword nopwdexp. Not sure if all that was
necessary. However, before I did this, the WNT Server Manager showed
the PW server--but it was grayed out. After I "fixed" PWRK$DEFAULT,
now the PW server icon shows the proper color...but if I try to sync
the domain the above error occurs.
My thoughts...is this a password or permissions problem for the
account for the PW server (account WSA146)? I set the password for
it on the WNT machine, but could not set it on the PW server. I get
a "SYS0059I: An unexpected network error occurred" when I try.
Suggestions, please!
Many thanx in advance,
Diane
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 4311.1 | Use LMUSER -mp | VMSNET::P_NUNEZ | | Mon Jun 02 1997 09:35 | 15 |
| Diane,
I think you're on the right course - setting the password of the
machine (wsa146) account on both systems. To set it on the BDC,
however, you'd normally need to get it's role to standalone first
(otherwise, LANMAN will want to update the UAS/SAM on the PDC).
But just use the lmuser utility to set the password on the bdc:
$ @sys$startup:pwrk$define_commands
$ lmuser -mp <pswd> wsa146 ! NO quotes necessary around <pswd>
Let us know what how you make out...
Paul
|