mabuhay

That has been the audit policy all along in user manager. It's checked, but still no record in the security event log.

Our PDC is not logging all failed logon attempts any longer. It used to log any attempt by anyone to logon to the network if it failed due to bad user name or bad password. Now it only logs failed attempts if you try to logon to the network at the PDC, but not for clients who try to logon. I can't see anywhere that this setting can be changed--it used to be all users at all PCs showed up in this log. It still logs successful logons from all users, but not unsuccessful logons, and it logs it if the user account gets locked out due to too many bad attempts. Is it possible that the system has been hacked to turn this off, if so, how to fix it? Thanks

Our PDC is not logging all failed logon attempts any longer. It used to log any attempt by anyone to logon to the network if it failed due to bad user name or bad password. Now it only logs failed attempts if you try to logon to the network at the PDC, but not for clients who try to logon. I can't see anywhere that this setting can be changed--it used to be all users at all PCs showed up in this log. It still logs successful logons from all users, but not unsuccessful logons, and it logs it if the user account gets locked out due to too many bad attempts. Is it possible that the system has been hacked to turn this off, if so, how to fix it? Thanks

I have one Win 2000 laptop that won't join the domain ('test'). When I do the network identification wizard, it says "domain name 'test' is either invalid or does not exist". Why? All other PCs/laptops join this domain with no problem. I have uninstalled and reinstalled TCP/IP, but no luck. Even though it won't jon the domain, I can browse the network by using start- run- path name. Any help would be appreciated.

I have to install Win NT 4 server on a Compaq Deskpro. We've put in a RAID 1 array with 2 SCSI hard drives, 73 GB each. When I run the NT 4 installation, it gets through the first install disk and crashes on the 2nd disk, with the error "inaccessible boot device". there's no viruses, I've created new install diskettes, even changed the floppy drive out, but no luck. The SCSI configuration shows the mirrored hard drives, but I just can't get it to complete the installation. Any suggestions?

One user on our NT domain sometimes shows up in server manager with many excel files open as soon as he logs on, when in fact he has not opened any of these files. It's not consistent--sometimes it does it and sometimes it doesn't. He's on Windows XP. Can anyone explain why it does this? Thanks

On our NT 4.0 network, we use roaming profiles. Some of the user profiles have a temp folder, and these can get very large (up to 1 GB), all of it junk, which makes for very slow logon. Other profiles do not have temp folder at all. Questions (1) what determines whether or not there is a temp folder in the roaming profile? (2) how to automatically delete temp files so they don't ever get into the profile before up[censored] to the server? Thanks

No to all of the above--the files are spreadsheets, docs, etc that are used all the time, no viruses. This has happened before--it just seems to go away for no apparent reason.

Yes, get an access point and connect it to your LAN. Use the SSID from the access point in your PCI card configurations. This USUALLY works right the first time if SSID matches on all units. Sometimes communication can be really flakey, though, and may require tweaking the settings (channel, RTS threshold, etc.) Good luck!

This morning the Open Resources (files in use) on our server (NT 4.0)showed one user with about 50 open files from the server shared directory. This was preventing others from editing the files. In reality, he didn't have ANY of these files open on his system. I forced them closed, but why would they show up in use if no one is using them? Thanks

How can I find all static IP addresses in use on Windows NT server? We have several printers and PCs with static addresses, but they are not in the "Reservations" list, and do not show up in the "Active Leases" because they don't use DHCP. I want to be sure I don't assign the same static IP address to some new wireless units we just got, but, other than trial and error through pinging addresses, I'm not sure how to do it. Thanks for any help.

Yes, the permissions are all set the same as all the other profiles that do work right.

Have WinNT4 server w/Win2k clients. All have roaming profiles set up the same way on their local machine and on the server. Two of them get the message "Cannot update roaming profile" when they log off. All others work properly. Have checked Microsoft support; their recommendation was to install latest SP, which had already been done. Any suggestions on how to fix this? Thanks

We've got an XP client on Win NT 4 server network. She logs on fine when on the LAN, can get to all the correct folders, internet, etc. When she dials up from outside the office, the shared folders that are supposed to get mapped during the logon script don't get mapped, and she can't get to the internet at all. It seems like she's getting authenticated, because she can open network folders through the START RUN window, and all the permissions are correct. I've got the dial up session set to logon to the domain (as far as I can tell), so why is it not mapping correctly? What could be causing it to fail to go to the internet? Our Win95 and 98 clients can logon to the domain and internet remotely with far fewer problems. Where the heck is winipcfg command in W2K and XP???? Thanks

Problem description: WinNT4 server won’t boot after putting in a new mirror hard drive; message says: “A kernel file is missing from the disk. Insert a system disk and restart the system.” If I put in the NT system disks and go through the repair option, it gives me the following message: “STOP: c000026c {Unable to load device drivers} \device\floppy0\ntfs.sys device driver could not be loaded. Error status was 0xc0000221. Restart and set the recovery options in the system control panel or the /crashdebug system start option. If this message reappears, contact your system administrator or technical support group” I finally got it to boot from the original boot disk, but don’t want to shut it down again and try to fix it until I understand what’s wrong with it. Microsoft gives several suggestions for both of these messages; however, none of them work because when I try to fix the kernel error during bootup, using the emergency repair disks, it crashes on the ntfs.sys device driver. Can’t see how to get past the ntfs.sys problem and get to the system control panel or the /crashdebug option. Any suggestions? Thanks