Discussion Locked

Network Printer and Share Drives Access

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

We have Windows NT/2000 servers on our network. The Windows NT servers are the primary domain controllers. Windows 2000 servers do not have activie directory installed and are not domain controllers. Problem:

When the Microsoft Security Rolluppatch or the Microsoft Windows 2000 SP3 is installed to a PC, the user cannot access (access denied) the printers or the share drives (all of which are on Windows 2000 servers). They can access printers or share drives if they are on Windows NT servers. However, the administrator can access the printers and share drives if logged in on the PC. Not sure if the mixed (Windows NT/2000 servers) environmnet is causing this problem. I guess it might be better to go with all Windows 2000 servers instead (this would take a little time to implement).

7 replies

by dao251

there is no enough info in your description...

I would only guess you have to re-join your 2K servers into NT domain.
Probably your "administrator" password is just the same for local admin of member servers and Domain administrator.

Dima.

by abubin

did you install sp3 on the win2k server as well? Have you tried removing all the shared printers and then re-install? Make sure to use the same share name so that you don't need to change anything on the workstations.

by mjamell

Did you put sp3 on the server as well? Is there a login script running when a normal user logs in and not one when the administrator logs in? Sounds like the authentication is not being passed accross to the 2000 server with normal users. Have you tried as a test to change the 2000 client with sp3 to login to a workgoup with a normal user id and password and then trying to access the 2000 server? This won't log you into the nt4 domain but it would eliminate if the nt4 server is causing a problem. You would still have access to the resources on the nt4 domain.
Also, are you running wins? Try accessing the 2000 server by ip address. put the server ip address in the run box and see if it shows the shares \\ip.address.goes.here makesure you use back slashes. If it works by ip address you are having a name resolution problem.

This discussion is closed to new replies.