NT Bugs

Last Updated -[Mon Apr 13 23:00:42 1998 by cxh]-

Here's a IMHO short list of why NT is not ready for prime time. If anyone has real solutions that are available now for these problems, let me know.

You cannot log in from a NT machine onto a Unix host without typing your Unix password in cleartext, or having a .rhosts file on your Unix machine. The real fix is to use SSH or Kerberos

NT is not an interactive multiuser operating system. One user sitting at a keyboard can start multiple jobs under different user names. However, a remote user cannot run a job and display the results graphically. There are addons that can do this, but out of the box, NT 4.0 cannot. If there is no one sitting at the machine, then the CPU is not being used. However, the files can be shared.

It is difficult to install Apps on a central server and run them on clients without sitting at each client and installing the software by hand.

NT has security logging, but it appears that there is no way to send the logs to a remote machine. If the security of a machine is compromised, then the local logs are suspect.

To change the NT domain name of a NT server, you must reinstall NT. To me, this is a bug. My guess is that it will be fixed eventually.

Back to my NT page

Send comments to cxh at eecs.