2000 Server, Domaincontroller - can't access printerdrivers through \\servername\print$

  • Thread starter Thread starter T. Kaestner
  • Start date Start date
T

T. Kaestner

Hello!

I've got the following problem:

Since I reinstall our domaincontroller I cannot connect to the printershares
with a simple doubleclick. I've worked on this problem a while now.

I this happens because I can't acces the network share where windows
searches for the printer-drivers: \\servername\print$ If I try to connect to
this share I see nothing. If I do the same on an nearly identical Server
which is not a domain controller I can access it.

Is there a way to get acces to this share even on a domain controller?

Thanks for every answer!!

Greetings,

T.Kaestner
 
When you run the command net share on the domain controller do you see the
printer share?? What happens when you try to access the print share - does
it say can not find or access denied? Can you access the sysvol share on the
domain controller through My Network Places?? Any domain user should be able
to see and access the sysvol share. --- Steve
 
Thank you for your answer Steve,

after net share I can see the printer share
(output: print$ C:\WINNT\system32\spool\drivers Druckertreiber).
It's a german version.
All appears to be correct. I can access the sysvol share without errors.
If I try to connect to the printer share a window opens with no file or
directory in it. If I try to create something (e.g. a directory) it says
"The system cannot find the denoted file."

We've got a second domain controller. I tried to share a printer in this
server (it's 2000 server, too) and the same error occurs.

This is why I think it is some domain-controller-security issue...any idea?

Thank you,

Thomas Kaestner
 
Hmm.

Does anything show as a warning or error in the logs shown via Event Viewer
on the domain controllers that may be related? I did a quick Google search
of "The system cannot find the denoted file" and did not find much of
anything. I don't know if this will help by try restarting the print spooler
service. Can you connect to that share while logged onto the domain
controller itself using \\server\print$ in the run box to try and see if it
is a networking or other issue? Double check the permissions to the share
itself and the folder NTFS permissions to make sure they are correct and
compare to a server that is working and verify that you can access folder
locally. I would also run the support tools netdiag, dcdiag, and gpotool on
your domain controllers to see if any problems are found which may or may
not be related. --- Steve
 
Back
Top