Displaying 5 results from an estimated 5 matches for "jdown".
Did you mean:
down
2011 Jan 12
0
working with the net commands... trouble.
...u or wbinfo -g and get expected results. Every query
I make about the domain works
However, I'm trying to add a domain user (me) to my local Print
Operators group on this freebsd machine.
Using Samba 3.5.6, FreeBSD 8.1 Clean install of everything yesterday.
So, I'm trying to add KRH\jdown to the Print Operators group. It acts
as if the command completed successfully, however, when asked to list
the members of the group, it chops off the domain portion.
freecups-2# net sam delmem 'Administrators' KRH\\jdown
Deleted KRH\jdown from BUILTIN\Administrators
freecups-2# net sa...
2010 Sep 29
1
Hard time installing printers 3.4.8
...valid users = %U
create mask = 0700
directory mask = 0700
read only = No
browseable = no
[printers]
comment = All Printers
path = /var/spool/samba34
create mask = 0700
browseable = no
printable = yes
guest ok = yes
#
[print$]
comment = Printer Drivers
path = /home/PrinterDrivers
#valid users = KRH+jdown
#admin users = KRH+jdown
create mask = 0755
directory mask = 0755
read only = No
2011 Jan 14
1
SAMBA / CUPS Printserver
Okay, I've got some progress now. Have fairly decent printserver
working. I've been able to reproduce the same postive and negative
results in two physical servers and now (finaly destination) a vmware
server.
What's working:
ADS integration, this is a domain member
Printer driver installation (for a few drivers)
Printer installation / removal
Printing.
What's not working:
2011 Jan 17
1
samba shares fail after active directory reboot
We have a samba server that uses active directory security. We have three active directory servers and use a dfs namespace (test.local) to encompass those three servers. We currently are using password server = TEST.local, but have had all three AD servers listed, but it has not helped.
Whenever ANY of those servers go down for maintenance, the samba shares do not come up and restarting the
2011 Aug 25
2
Puppet Error during Yum execution
Every time a client checks in with the puppetmaster, I receive the
following error in the client logs:
Wed Aug 24 19:55:27 +0000 2011 Puppet (notice): Starting Puppet client
version 0.25.5
Wed Aug 24 19:56:05 +0000 2011 Puppet (err): Could not prefetch
package provider ''yum'': Execution of ''/usr/bin/python /usr/lib/ruby/