The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024

Latest message you have seen: (ukha_d) Re: Off Topic Posts (Again)


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Re: [Help!!!!] Local Logon Problem


  • To: <ukha_d@xxxxxxx>
  • Subject: RE: Re: [Help!!!!] Local Logon Problem
  • From: "Ian Lowe" <ian@xxxxxxx>
  • Date: Mon, 22 Oct 2001 13:20:44 +0100
  • Delivered-to: mailing list ukha_d@xxxxxxx
  • Mailing-list: list ukha_d@xxxxxxx; contact ukha_d-owner@xxxxxxx
  • Reply-to: ukha_d@xxxxxxx

Andy,

This is a common problem..

Netlogon is not starting, almost certainly because the dependencies are
not met, because there is no NIC in the system.

It's good practice on a PDC to have the MS Loopback Adapter installed,
with a PAS address (192.168.0.1 or whatever) so that at least one
"nic"
always loads, enabling the services to start correctly. Which doesn't
help for this one, but might in future..

For this one: (if there's a more elegant way, I have not found it)

Install a second copy of NT4 to the same partition, install it to
"C:\STUB" or whatever, but *NOT* "C:\WINNT" make this
an absolute zero
install, nothing except the base NT. Don't install drivers for
*anything* except the NIC.

Launch Regedt32, go to HKLM, and do a load hive.
Navigate to c:\winnt\system32\config and load the "system" file
(this
the HKLM of your non-working NT4 install) call it "othernt" or
something

Here's a trick, once a hive is loaded using regedt32, you can export and
import specific keys using regedit.

Using another PC, have a look at the inf file for your Network Card.
This will details all of the keys changed during installation of the
NIC.

You need to export the structures for the card from your "live"
registry
to a .reg file, edit this using notepad, and change the path from (for
example) HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet to
HKEY_LOCAL_MACHINE/othernt/SYSTEM/CurrentControlSet

Merge it back in, and it will add the required registry structures to
your dead NT to allow it to load the NIC Driver. You will also need to
do things like set an IP address under the Services/Tcpip/parameters
structure.

You also need to copy the actual driver files (also in your .inf file)
to the correct locations from C:\STUB\drivers to C:\WINNT\Drivers

If you are not happy with this process, my advice would be to get a
consultant in with some Disaster recovery experience. (and take
references)

Moving an installation of NT from one hardware to the next is a
difficult process, and one where it's *really* easy to get tied in
knots.

Oh, one more thing: write protect your backup now. :) you don't want the
backup job on your newly restored server kicking off and destroying your
security now ;)

Ian.

-----Original Message-----
From: Andy Powell [mailto:ukha@xxxxxxx]
Sent: 22 October 2001 12:38
To: ukha_d@xxxxxxx
Subject: [ukha_d] Re: [Help!!!!] Local Logon Problem



> OK, I'm assuming this is NT4 Server.
Yep..
>  Is it set as PDC, BDC or stand-alone?
PDC

> Do you have a domain in your network?
Yep

> What error(s) are you getting when
> trying to configure network card?  What do you get when you use
User Manager
> rather than the domain version?

Access denied!

*sob* *snif*

Andy





Home | Main Index | Thread Index

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.