home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 36 Tips
/
36-Tips.zip
/
NETACC.FAX
< prev
next >
Wrap
Text File
|
1994-11-27
|
5KB
|
110 lines
How to restore the NETACC 3/15/94
The following fax has three valuable tips to assist you in correcting
specific problems with your server or domain controller. Each
procedure solves a specific problem and you need to do ONLY those
that specifically relate to your problem. Read the fax carefully to
determine which procedure is required.
PROCEDURE FOR INITIALIZING NET.ACC (When NET.ACC has been corrupted)
1) Make a backup copy of the current NET.ACC, leaving old backups intact.
Rename d:\IBMLAN\ACCOUNTS\NET.ACC to d:\IBMLAN\ACCOUNTS\NET.BAK, or
if you are running Version 2.0 make a backup of the NET.ACC by typing
the BACKACC command. The BACKACC command is documented in OS/2 Version
2.0 LAN Network Administrator Reference Volume 3: Network Administrator
Tasks, page C-2.
2) ONLY ONE OF THE FOLLOWING STEPS (a, b, or c) will be applicable to your
configuration. DO THAT STEP AND THAT STEP ONLY. Note that the system will
need to be booted from diskette before any of the following steps can be
successfully completed.
a. If a previous, non-corrupted backup copy of the NET.ACC exists, then copy
it into the d:\IBMLAN\ACCOUNTS subdirectory.
b. If a non-corrupt backup does not exist and you are running OS/2 1.3 do the
following:
- Insert one of the following diskettes into drive A:
i. Extended Edition 1.30 installation diskette #7
ii. Extended Edition 1.30.1 installation diskette #6
iii. Extended Edition 1.30.2 installation diskette #6
- Type the following at the command prompt:
UNPACK A:NET.AC@ d:\IBMLAN\ACCOUNTS
c. If a non-corrupt backup does not exist and you are running OS/2 2.0 issue
the following:
COPY d:\IBMLAN\INSTALL\NET.ACC d:\IBMLAN\ACCOUNTS\NET.ACC
3) Only one of the following steps (a or b) will be applicable to your
configuration. Do that step and that step only.
a. If you are running OS/2 1.3 do the following:
- Insert the LAN Server 1.3 installation diskette in drive A:
- Type the following at the command prompt:
UNPACK A:ADDSVRIN.EX@ d:\
b. If you are running OS/2 2.0 issue the following:
COPY d:\IBMLAN\NETPROG\ADDSVRIN.EXE d:\
4) Follow the instructions below to run the ADDSVRIN executable from the
root directory (d:). This will initialize the new NET.ACC file. Note that
the server will need to be booted from the hard drive before the
ADDSVRIN command can complete properly.
ADDSVRIN %1 %2 %3
%1 - The computer name of the server. Located in the ibmlan.ini file.
%2 - Indicates the type of machine.
Enter the number 1 if the server is an additional server.
Enter the number 2 if the server is a domain controller.
%3 - The location of the ibmlan directory eg. C:\IBMLAN
Example: Domain controller with computer name Test1 and the IBMLAN
subdirectory is on C:
ADDSVRIN TEST1 2 C:\IBMLAN
RESYNCHING THE ADDITIONAL SERVER
Under unusual circumstances, the internal password between an
additional server and the domain controller may become unsynchronized.
This can also occur if a backup copy of the file NET.ACC is installed on
the domain controller or additional server. The usual symptom of this is
a NET3062 which indicates that the NETLOGON service has failed to
start, but other errors may occur.
NOTE: In the following steps <Servername> refers to the machine
name of the server, and <New Password> is an arbitrary text string.
<New Password> MUST BE IDENTICAL for all commands that use it.
To avoid possible complications when resynchronizing the server,
temporarily recreate the default administrator ID of USERID with
a password of PASSWORD and use it for the following steps.
The ID should be deleted at the end of the procedure, for security
reasons.
STEP 1:
Ensure that the additional server is listed at the domain
controller. Go to LAN REQUESTER's Full Screen Interface. Select
DEFINITIONS then MACHINE PARAMETERS then ADD (if not listed). r
If it was already listed check UPM (User Profile Management) to
ensure that Server is identified in Group Servers and Userid.
TRY TO START THE SERVER NOW. If it starts without errors, you may
may stop here.
STEP 2: (If errors continue after the above step.)
In order to reset the additional server's internal password at the
domain controller, issue the following at the domain controller:
LOGON USERID /P:PASSWORD
NET USER <Servername> <New Password>
LOGOFF
Go to the Additional server and do the following steps:
LOGON USERID /P:PASSWORD
NET ACCOUNTS /ROLE:STANDALONE
NET USER <Servername><New Password>
The password you set locally and on the domain controller
must be the same. Now reset the role and start NETLOGON.
NET ACCOUNTS /ROLE:MEMBER
NET START NETLOGON
12/31/99