In our network we have a Windows 7 print server. Users connect to this machine by typing \\server_name on their own workstations. The print server and the users` computers are members of Active Directory. In AD, only computers have accounts, users are using local accounts.

Is it possible to configure Windows 7 so that it doesn't ask for login and password when a user tries to access it from computer which is member of domain?

  • 6
    Why would you configure AD in this way? – Tablemaker Nov 16 '11 at 20:17
  • Don't try to print via SMB. Setup IPP/LPR or some other sharing protocol? – Zoredache Nov 16 '11 at 20:23
  • I second what @Shads0 says. Why the hell are users logging in with local accounts on domain-joined computers? That's ridiculous. – MDMarra Nov 16 '11 at 20:58
  • @Shads0 We don't use domain account because we don't need them. Most of network environment is based on Linux. AD is used only for remote Management of workstations south as running startup scripts, software management etc... – user101141 Nov 16 '11 at 22:15
  • @user101141 based on your question, it sure sounds like you need them to me. – MDMarra Nov 16 '11 at 23:37

Since you have AD implemented, you're better off saving yourself a lot of other headaches in the future by giving the users accounts on the domain instead of locally and having them log in this way. The benefits of this vastly outweigh any other type of pieced together solution that is not supported by Microsoft in the firstplace.


The user would have to logon with an AD/network account. Alternatively, you could recreate each users' local user account on the print server (username and password MUST match). In short, not possible.


I might be wrong but it is not possible.

User must be members of the domain to log or access computer of the domain.

With Windows 7, you might be able to store password with the credential manager but still the account need to be a active directory user account.


Creating a user entry in the directory, granting that user to access print server shares, then saving that user's cridentials to all clients should be a solution.

Edit from comments:

When local user tries to access that win7 share, o.s. will perform a login screen. That local user could type the credentials of the user, which you created and edited its permissions of that specific share, and save that information clicking "Remember bla bla".

By doing that, creating a user and cridential saving,

  1. You can have some control over that share.
  2. Local users won't be have to type that user-password info all the time.
  • What does this even mean? "then saving that user's credentials to all clients" That doesn't even make sense. – MDMarra Nov 17 '11 at 2:06
  • Maybe I let that open ended. *Clients trying to access the share *A login box appears *User enters credentials *User can save cridentials – Hasan Manzak Nov 17 '11 at 2:09

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.