9 replies
by rcsd
This answer is most likely wrong and probably will just tick you off. Nevermind, forget I even started to answer.. Well, while I'm here..
Are you certain that the correct domain name is in your "access control" under "Network Properties"? Sometimes using the NAME of the PDC works, other times you must use the domain name.
Hope this helps.
by crazydave
by cader
Just a few tips.
If you are using TCP/IP make sure all of the IP information is correct (DNS, WINS ect.) Also, if you have information in your workgroup area and the microsoft client installed with the checkbox marked to login to a domain, make sure that both the domain name and workgroup name are the same and in the same case. I have seen this cause some weird problems before. Is there a mandatory user profile in use or a system profile? Are you alowing changes to be made that are "Reset" when rebooting and logging in?
Just some suggestions, Hope they help.
by crazydave
You probably have a system policy (config.pol) in the NETLOGON share of your servers that is forcing you to do user level sharing. If its security provider is set wrong as mentioned above, you will have the same trouble. You want to use the DOMAIN ad a "Windows NT Domain" as the security provider. The only time you would use a single server is if user accounts are setup there and it is not a Domain Controller.
As far as user lists, if users can logon to the system, they're working. The SAM (Security Accounts Manager) stores users and groups for logon and security, and it's what you would be querying to add users to the printer.
by crazydave
by bill.parks
by crazydave
by crazydave
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending