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

Conference iosg::all-in-1

Title:	ALL-IN-1 (tm) Support Conference
Notice:	Please spell ALL-IN-1 correctly - all CAPITALS!
Moderator:	IOSG::PYECE

Created:	Fri Jul 01 1994
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	2716
Total number of notes:	12169

2550.0. "invalid password" by GRITS::WILLIAMS_T () Mon Mar 03 1997 18:39

    Hello, 
    
    I have a customer that has Allin1v3.1, and Teamlinks v2.7 clients. The
    Teamlinks users can not logged into one node in the 3 node cluster they
    receive a error invalid username or password. The same user can used
    the vt client and logged into Allin1 with no problem. The Allin1
    account name and vms name are the same. The problem node was create by
    using backup/image from another system (the user copied files, no
    installation was done on the problem node). The customer tried
    reinstalling tlc on the server and still receive the same error. The
    file cabinet server has been stopped and restarted. This note will also
    be place in the Teamlinks conference. Any ideals 
    
    Thanks 
    
    
    Tommy Williams

T.R	Title	User	Personal Name	Date	Lines
2550.1	Do the nodes have a common system disc?	IOSG::PYE	Graham - ALL-IN-1 Sorcerer's Apprentice	`Tue Mar 04 1997 08:51`	7
	Is this a common environment cluster, i.e. sharing a common SYSUAF? It's not supported otherwise. Graham PS Please spell ALL-IN-1 correctly.
2550.2		AIMTEC::ZANIEWSKI_D	Taking bids on Andrew's Alphatraz cell	`Tue Mar 04 1997 13:03`	3
	Check intrusion records for the PC node name. Dave Zaniewski
2550.3	Standalone....Not A Cluster	OASS::MARGETSON_M		`Tue Mar 04 1997 16:42`	17
	I just spoke with the customer. Both the good node and bad node are standalones. They are both running ALL-IN-1 3.1 and VMS 6.2-1H3. Customer did the image backup of the good node and copied this information to the bad node. Had him search for the original node on the problem node. Also had him delete and recreate the file cabinet server. We also tried renaming a user's filecab.dat and try the connection again. Still received the 'password expired' error. I am dialing into the customer's system to see if there is anything else I am missing. Melinda
2550.4	SYSUAF.DAT was the problem...	OASS::MARGETSON_M		`Tue Mar 04 1997 18:30`	12
	Found out the customer's problem was with the SYSUAF.DAT file. On the good node, there was one copy of this file in the sys$common area. On the problem node, there were two copies of SYSUAF.DAT, one in the sys$root area and one in the sys$common area. There was also a file SYSUAF.; in the sys$common area. Had customer rename this file and also the SYSUAF.DAT file in the sys$root area to resolve the problem. Melinda