Discussion Locked

NT4 Login Problem

0 helpful
16 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
In a network of around 500 PC's runing NT4 (sp5) and with NTSE installed, some workstations (around 5 and growing) are starting to have problems. When they boot up the Ctrl Alt Del login screen does not appear. Pressing the keys doesn't work, repairdisk doesn't work, the machine doesn't appear on the network. The machine is not accessable on or off the LAN. It just sits there and needs to be rebuilt. Help! As the network grows if the problem 'spreads' rebuilding a PC every time is not exactly an efficient way of doing things. Has anyone come accross this problem before? Any help would be much appreciated! Thanks.

16 replies

by ckaylam

HI
Manage such large scale LAN is not a easily job.First , What is NTSE(NT Server Enterprise)? I have no idea about this.

First Question about the LAN.Do the troublesome computer are in the same network segment?in a subnet?

Assumethe sample case is in the same doamin without subnet and all the PC are the same model.
Try this simple solutions first. Find a same model computer(100% without such problems). Then take out the harddisk to the suspectable PC , reinstall the lan card driver again . Then test again the same problem appear or not
If the problem gone , then the problem mostly due to the software(Mostly I think)
Please also try load the default setup in BIOS.

If the problem still exist, the only way to change hardwares one by one to see

About the disappear from the Network mean?
You can ping the PC and dont able to browser the computer through Network neighbour? or even not able to ping the PC (assume the network is in good condition)
If the later case, please check the network setting or the lan card.
If the first case, try this
1)Make sure that PC name is unique among networks
2)Make sure that PC is configured at proper Workgroup. If the domain name is ABC. Please make sure the workgroup is also ABC.
3)Try to install WINS and configure the client to use WINS for name resolutions

4)Last methods,Remove the PC from PDC,then create PC account on the client by providing Administrator password. Mostly this will work

Contact me through Email to have further discussion about yourcase

by dsavage87

Thanks for your reply,

The SE in NTSE stands for Security Enhanced. It's an additional component the client required for the network. The PC's are in the same subnet. Bios is configured correctly, although I will be trying to reinstall the network card drivers from a second disk.

When the problem occurs on a PC it cannot be accessed remotely and doesn't appear in the network and can't be pinged. The PC name is unique, network is configured correctly and we don't use WINS. We've also tried your 4th point without success.

The PC's that have this problem become redundant and have to be rebuilt. Faulty network cards are the main suspect so far. More machines are to be rolled out soon which is why I need to find the fault quickly. Thanks for your help so far.

by greywolffe

Not to sound too much like a MS tech support rep (lol) have you attempted to upgrade to SP6 for TSE? I've done it and it has eliminated some quirky login probs I've had in the past.

Just a thought.

ps...to first answer TSE is Terminal Server Edition.

by dsavage87

Upgrading service packs is not an option, service agreements and testing(!) of the current system have been concluded and approved. The contract is for the system as it is. Nice try but i wish it was that simple!

by allan

Are these machines being built from scratch or they being created from an "Image" ?
If they are being built from an Image the SID for the machines is probably in the image.
I believe that Ghost uses a utility called "SIDWalker" for changing them but I believe the SID should be removed before creating the Image (SysPrep utility)
If the machines hang during boot up the workstation and Server services are probably not starting and you will not be able to see or access them from the network. Youmay be able to ping them though and that would help answer the questions about the NIC working.
Is someone building and/or providing these boxes for you ?
Can you verify the hardware they are using is on the HCL ?
Just seems weird to have multiple boxes with the same failure.

by dsavage87

The machines are being built from an image. But the network SID was removed before machines were being cloned with it. If the workstation and server services had stopped would this prevent the Ctrl Alt Del screen from appearing?

All the components are in the HCL. Weird doesn't even come close to describing this one! Once the machine has been re-cloned everything works so i can't see it being a hardware fault.

by redeyes

Can you get to the BIOS?

I realize you mentioned that RDisk doesn't work, but are you not even able to boot any of these machines using a DOS boot disk?

Also, have you considered the "virus- possibility?"

My apologies for the "questions only" format.

by dsavage87

BIOS can be accessed but i'm not sure what help that is? Everything is set up to default.

Again, the machines are NT4 with NTFS so i'm not sure what help DOS is. Although i know very little about DOS it has to be said. The DOS boot disk just boots the machine to the command prompt off the floppy.

Virus is unlikely. None of the users have access to the internet and policies ristrict what they can do severly. No a: or CD-Rom drive access for instance and no email so where it could come from i don't know.

by mpdcsup

Still having this problem?

This definitely sounds like a service start-up failure. The problem is going to be finding out which service.

My first line of attack would be to get to the event log of one of the affected machines. Try leaving a machine on (waiting for Ctrl-Alt-Del) for a day or two (in case a time-out occurs somewhere that will let you in).

Try removing the NIC in one machine and boot-up stand-alone (the NIC device driver failure may circumvent the failure you are experiencing) still attempting to get to the event log.

Try any other means you can think of to get to the event log (including performing a *careful *repair from cd installation).

by daven71

Can't promise this will fix issue going forward, but this idea is a good place to start troubleshooting. When NT boots, subsystems must start (including to get logon dialog box). When working properly the order goes: windows subsystem (controls all I/O's and access to video screen...called csrss) automatically( starts winlogon.exe and that starts the Local Security Administrator (lsass.exe), which then starts all other vital subsystems. You may want to make sure you have all these subsystems inplace. Registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\SubSystems. Within that subkey are all the exe's and devices that start on bootup within the subsystems. I would power off machine, restart and select Last Known Good Configuration when prompted and once in, check the registry. Also, go to control panel and view start values of device drivers by clicking on devices option. Again, this will help you discover your problem and hopefully will get you closerto finding the reason why it's "suddenly" happening.

by daven71

By the way, forgot to mention... if anyone of the tasks in these intial subsystems fails during boot-up, the OS will consider it a failed boot and won't start any services or .exe files it could find during boot, so it will hang, which will not giveyou the logon dialog box. Also, during the subsystem check, it also looks for valid device drivers... if any of this is bad it will not be considered a good boot. I didn't read other to see, but have you cloaned these machines? If so, are you using the same devices with the same device drivers on all of them? If not, then that could be where issue is steming from.

This discussion is closed to new replies.