26 replies
by guy
1) Are you truly sure that q234655 is the cause of your problem?
2) Look in the Event Viewer for more clues as to why the NETLOGON service is not starting.
3) Go to the Control Panel, Services, and try and Stop and Start the Netlogon Service.
by brat
Maybe u can get on another NT server, and start the NetLogon service remotely by using server manager, or use event viewer from that NT server and look at the event log remotely. If you don't have any other NT station, install them on a win9x PC from the resource kit or NT Server CD and install NT server tools..
Otherwise, you can use the recovery tools found at www.winternals.com
by brat
Four ideas.
1. Problem could be a wrecked registry,and the system can't find the location of the services file is lost, goto REGEDIT.COM and download a copy of REGCLEAN.
if that doesn't work try this.
2. Since you've modified the boot ini, goahead and do the repair, login to the network and install sp6. or
3. Put your NT Workstaion cd in and do an upgrade (even though it's the same version).
4.Finally, install a new version of NT into a separate directory (DON'T FORMAT THE DRIVE)and attach to the network, download SP6. Now the choices are to work with it from there or delete the new install and work with the old install and apply the sp6 you downloaded.
by brat
by calves
By booting through your CD, you should get to Windows then apply the SP. Also, you can copy the system files to a diskette by booting off a WIN9x startup disk (I hope your system partition is not NTFS), and then copy the system files.
Good Luck!
by brat
by salexiev
Just two suggestions,
1)This error could be due to start of another PDC of this domain – if it is so, just stop this PDC (or its Net Logon service);
2)If the boot sector is lost you can try to fix it, using NT native tools (boot from CD orthe three disks, without recovering Registry, if you haven’t fresh copy).
Good luck
by brat
by mickbowen
by brat
by jun1cez1
To Brat,
If the server would'nt let you log on because the NETLOGON service is not running, why don't you log on locally with an Administrator account and do the fix locally. Perhaps you can stop and start the NETLOGON service from the control panel\services\netlogon. Regarding the user, go to system policy editor and see if there is any overriding policy against the user/users. Its usually at winnt\system\Repl\import\scripts (NTCOFIG.POL) and I assume you know that already. Now,if you want to make a complete repair of the SAM, make sure you have the most recent ERD and perform a complete repair from the backup then install the SP6a.
Warning about the SAM file, you cannot use a clients SAM against a Server's SAM. You'll just make it worst.
Hope this helps.
Jun
by brat
by mphoffar
by brat
I am not sure if you have provided enough exact detail for a perfect solution to this problem, but there are a few simple steps you could undertake.
I am guessing from the error that this server is infact domain controller of some type (PDC or BDC). The most obvious reason that this server has gone belly up is that the network card device driver is not starting, hence the reason that you get a netlogon error when trying to log on locally as the administrator. This was probably created eitherthrough driver corruption at power down, or you selected to replace the third party driver during your repair, and the card is infact not supported by the default NT driver provided.
Your course of action to resolve the problem now depends on theHDD configuration. If you haven't setup software RAID then this is the easiest solution.
As stated above, install NT into a new directory eg winntdrp, just do a vanilla install. This will allow you to access and transfer the data to another network device. It's not a
by brat
by salexiev
Hello,
When using the correct driver for EtherExpress (from Intel, not from Microsoft) you will have installed Intel Diagnostics – you could use it for testing NIC, cables and Ethernet connectivity. If it shows that all is ok, check if there are any errors in typing domain name, admin user name and password, It is good to check PDC log for Security errors – they could help you to find the problem.
Best wishes
by brat
by rastatech
by brat
by m42
OK, i guess we have two problems here:
1 - Data cannot be lost
2 - User cannot logon to system
As for #1 i recommend getting a copy of a disaster-recovery utility called Tiramisu for WinNT it can read trashed FAT/FAT32/NTFS partitions AND copy the data to another media, do a search on your favorite search engine with "Tiramisu" and "Windows".
As for #2, i suggest making a full backup of the system and then reinstall NT to another directory, choosing "Standalone Server" so you can work locally on the machine, recover your data/files/whatever. After this you can try booting your initial NT install and see if it's OK, else go on and rebuild everything from scratch...
Good luck
by brat
by mlovelady
by brat
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending