Discussion Locked

Win98 account lockout every hour

0 helpful
11 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have two users on a 30 user segment that use windows 98. These two users suffer from automatic account lockouts at what seems to be every hour give or take a few minutes. I must then unlock their accounts, then they must reboot in order to log back in and use their personal shares.

Here's what's going on the AppEvtLog:
-Windows cannot determine the user or
-computer name. Return value (1326).

Here's what's going on in SysEvtLog:
-The DNS server for this DC does not support
-dynamic DNS. Add the DNS records from the
-file '%SystemRoot%\System32
-\Config\netlogon.dns' to the DNS server
-serving the domain referenced in that file.

And, as usual, the security log is eerily empty.
What is causing these users to be locked out unexpectedly, and how do I add that DNS info to the DNS server?

-Timothy Gansert
Systems Admin
Electric Mobility Corp.

11 replies

by pan 13 x

Go to your dns server and set it to allow Dynamic updates. Also delete the Computer account from the PDC and readd the computer back, under active directory users/computers.

Allowing dynamic updates will allow the computers to update the computer registration with the dns server.

If this fails you may need to rename the computer name on the computer itself and update the name on the pdc also.

by tgansert

After I followed these instructions, I still get the error. Even after enabling DynDNS

The error specifies to "Add the DNS records from the file '%SystemRoot%\System32\Config\netlogon.dns' to the DNS server serving the domain referenced in that file."

How do I do this? It seems like the next step.

The UserEnv event went away.
(Windows cannot determine the user or computer name. Return value (1326). )

Oh, update: one of the two user account lockout problems has been solved. User error. But one remains. It is a Win98SE station running autocad. The user does a lot of file transfers between our AS/400 and the 2000 server. We've experienced problems with NT4 workstations with transferring files from NT to AS/400. after a transfer, the AS/400 share becomes disabled and it useless until the workstation is rebooted.

Thanks, TJG

by tgansert

Win2000SVR defaults UseDynamicDns == 0x1 in Machine\System\CurrentControlSet\Services\Netlogon\Parameters

I have tried both enabled and disabled, however, never specifying 0x1, only default.

I've deleted and re-added HDEC14 to ENG-PDC's computer accounts listing, so we'll see.

Thanks for your help.

by taiseermustafa

are they facing the same problem on other machines? If yes then it is not a machine problem.
Try to create a temp account and test it on both machines, if everything went fine then it could be a user profile problem....check the right's and the permissions given for these 2 users...

Good Luck.

by zandy.mcallister

I had a user having this problem. This is what I did last week, so far so good! I opened a dos prompt. typed: net config server The autodisconnect time was set to 15 minutes. I changed it to -1 (Infinity) so that the user wouldn't be disconnected if idle. (net config server /autodisconnect:-1)
This has fixed our problem. I suggest that you read this kb article before changing the autodisconnect time though: Q138365
Good luck!
Zandy

by tgansert

Ok, I found our problem and here is our resolution. After an extensive amount of testing, I found that this is actually a hardware issue. The onboard Intel NIC on the server is not capable of supporting continued transmission at 100MBps.
After sometime, it blinks the hub and the Windows9x machines take this as a disconnect since the server has stopped transmission.
However, the NT computers remain connected because they can resend their credentials after the server goes back online.

This NIC card is the Intel 82558-based Integrated Ethernet with Wake on LAN. It came on a prebuilt server from Infotel (MWMicro). If you have this server and are experiencing this problem, drop your network speed to 10MBps Half Duplex. It's the only configuration that will work beside getting a new motherboard, or using a PCI NIC.

Thanks go to all those that helped.

by estebandelatorre

Think that you have fix the problem in a strange way. I think that the real problem may be between the NIC anf the hub in FULL duplex only. There's a lot of issues, many of them about slow backup's or transfers, and the solution for them is to turn FULL duplex into HALF duplex.
Just an idea...

This discussion is closed to new replies.