Technical article 109484

Windows NT systems can no longer see the AFPS Domain Controller after AFPS has been removed and reinstalled.

OpenServer 5.0.0OpenServer 5.0.2OpenServer 5.0.4OpenServer 5.0.5OpenServer 5.0.6UnixWare 7.0.0UnixWare 7.1.0UnixWare 7.1.1Open UNIX 8

Written · Last revised

Problem

When I try to log in to an AFPS domain from Windows NT, I get an error similar to the following:

A domain controller for your domain could not contacted

Cause

If you have removed and reinstalled AFPS you will need to go
through the following steps to re-create the Security ID (SID)
on the NT system.  The process of removing and reinstalling AFPS
removed the Security ID (SID); therefore, the AFPS system and the
Windows NT system no longer share the same Security ID information.

Solution

Take these steps on the NT system:

1. Click on "Start" -> "Settings" -> "Control Panel".

2. Double-click on "Network".

3. The "Identification" tab should be in the foreground. If not, click on it to bring it to the foreground.

4. Click on the "Change" button.

5. The "Computer Name" is the name of the NT system and should not be changed.

6. Click on "Workgroup" and enter the name of the AFPS Domain.

7. Click on "OK".
8. If you see the following:

Removing this computer from the <afps_domain_name> domain will result in loss of access by domain user accounts.

Are you sure you want to remove this computer from this domain?

Click on "Yes".

9. Click on "OK" when the Welcome screen comes up.

10. You should now be back to the "Network" screen. Click on "Close".

11. Click on "Yes" when prompted to restart the computer.

12. Windows will now restart.
=================================================================

When Windows restarts, log in and do the following to "re-setup" the Domain information:

1. Click on "Start" -> "Settings" -> "Control Panel".

2. Double-click on "Network".

3. The "Identification" tab should be in the foreground. If not, click on it to bring it to the foreground.

4. Click on the "Change" button.

5. Click on "Domain" and enter the name of the AFPS Domain.

6. Click on "Create a Computer Account in the Domain", enter "administrator" for the "user name" and enter the administrator password for "password".

7. Click on "OK".

8. Click on "OK" when the Welcome screen comes up.

9. Click on "Close" when the Network screen comes up.

10. Click on "Yes" to restart the computer.

=================================================================

You should now be able to log in to the AFPS Domain when the system restarts.

NOTES:    If the above fails, be sure that AFPS is running by doing the
          following:
# ps -ef | grep lmx
You should see the following processes:
lmx.ctrl
lmx.srv -s 1
lmx.dmn
lmx.browser

If these processes do not show up, try typing:

# /usr/bin/net start server  <Enter>
You should see:
Advanced Server starting...
After you get the prompt back, wait a minute or two to ensure
that AFPS is fully started (it is probably still starting up
after the prompt is returned).  Then type:
# ps -ef | grep lmx  <Enter>

You should now see the lmx processes listed above.

NOTE:     Check also the other servers in the domain to ensure that other BDC's
          networking is correct. ie. ensure that multiple NIC's in a BDC aren't
          configured with the same network information otherwise the AFPS PDC
          may not be able to update the SAM information to the other BDC's and
          cause the "lmx.ctrl" process to consume a large quantity of CPU time.

See also

ta100062, "Windows 95 clients get 'can't find domain controller' when logging in to SCO AFPS/NT domain."

From the Xinuos technical article database, record 109484. Reproduced with permission. The original is at www.sco.com/ta/109484, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.