Windows Forum

Ask something
Discussion Locked

WindowsNT4.0 + Windows2000

0 helpful
8 replies

by hanankz

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
My network is based on WindowsNT domain, and I have scripts that are executed when the users login to the network to map some network folders on their computers. Everything was working fine with Windows98 machines, but we have switched recently to Windows2000 professional and we have begun to receive an error message during the execution of the script; it says: System Error 53. Any hint.

8 replies

by hanankz

Just to clarify myself, the server is still running a WindowsNT 4.0 and we have switched from Windows98 to Window2000 professional on the users PCs only.

by valachi

Please check the resolution process on the W2K computers. While in NT they were using primarily WINS for resolving the names, in W2K they are using the DNS. If they are not able to resolve the DC name (PDC, BDC etc) where they have their script, they are giving you this error.

by allan

It depends on what the script is trying to do.
W2K clients have a lot of Operating System areas that have restricted access.
If the script is trying to write to the client for example, you need to make sure the folder permissions will allow it.
I've also had to go in and change perissions in the registry to get things to work.
Again, it depends on what the script is trying to do.

by randygraham

I would have to agree with Allan@ross.org It sounds like a permission or even a user access level for the local W2K local account (under users in the control panel.) here is a knowledge Article. ID: Q259878. Hope that helps.

This discussion is closed to new replies.