>
> /etc/krb5.conf
>
> [libdefaults]
> default_realm = XXX.XXX
> dns_lookup_realm = false
> dns_lookup_kdc = false
> ticket_lifetime = 24h
> forwardable = yes
> default_tkt_enctypes = arcfour-hmac-md5 aes256-cts-hmac-sha1-96
> aes128-cts-hmac-sha1-96
> default_tgs_enctypes = arcfour-hmac-
>
> Nick,
>
> I would suggest looking at your available encryption types available to
> Solaris. We ran into this before and this bug supplied a work around
> that fixed us.
>
> http://bugs.opensolaris.org/bugdatabase/printableBug.do?bug_id=6534506
>
> If you want to find out the encryption
I'm running Windows Server 2008 and trying to connect to Samba 3.0.37 on
Opensolaris. The Samba system is a member of a Windows Server 2008-based
Active Directory domain - it was able to join the domain just fine - and
Windows XP, Windows 2000, Windows Vista, and Windows 7 can connect, but Wind
>>> On 2010/08/09 at 11:25, Stefan Onken wrote:
> Hello,
>
> I have some users using sometimes Windows XP and sometimes Windows 7. In
> my smb.comf I only have one profile section, now Samba is creating both
> "profile" and "profile.V2" in the /home/ directory. Resulting in
> using twice the
>
> Try setting the required names to be "sticky" (i.e. infinite ttl) in the
> wins.dat file
> that nmbd reads on startup.
>
> Jeremy.
Apologies in advance for the ignorance...what's the best way to go about doing
that??
Thanks,
Nick
This e-mail may contain confidential and privil
As previously posted, I've migrated my WINS server over to Samba. I've run
into one issue, and have one question, about WINS functionality:
- The default expiration time for WINS entries is 6 days. For my client
systems, this isn't a problem, as most of them reboot, renew DHCP leases, etc.,
o
I have a Windows NT4 domain that I'm considering migrating to Samba. It has
three domain controllers, all of which are WINS servers, about 350 computers
and around 250 users. It also has a trust relationship with an Active
Directory domain. I'd be migrating to three Samba servers backed by LD
Various versions - 3.3.x, for the most part, I believe. Are you running Server
2008 or Server 2008 R2?
>>> On 2010/07/01 at 12:30, Indexer wrote:
> On 02/07/2010, at 3:34 AM, Nick Couchman wrote:
>
>> We have several Samba systems of varying versions joined to our W
We have several Samba systems of varying versions joined to our Windows
Server 2008 Active Directory domain. I don't recall having to do
anything special to get it working.
-Nick
>>> On 2010/06/30 at 09:23, wrote:
> Hi,
>
> We have installed Samba version 3.3.7 on AIX server.
> So we use AIX
Nick,
>
> Is it possible that Suse has backported the fix for Bug #7104
> <https://bugzilla.samba.org/show_bug.cgi?id=7104> into your version?
> I believe the lowest version from samba.org with this fix is 3.3.11
> <http://www.samba.org/samba/history/samba-3.3.11.html>
I've recently upgraded a server and am having an issue with symlinks that used
to work but are now broken. The links are on one of the filesystems shared by
Samba, but point to directories on an NFS-mounted volume. The permissions and
export on the NFS volume are such that both root and normal
>>> On 2010/05/27 at 08:48, "Nick Couchman" wrote:
> I'm having trouble getting a host to join an ADS domain/realm. I have
> smb.conf set correctly, with the workgroup, realm, and security = ads
> specified. However, when I try to join with the command: ne
I'm having trouble getting a host to join an ADS domain/realm. I have smb.conf
set correctly, with the workgroup, realm, and security = ads specified.
However, when I try to join with the command: net ads join -U Administrator, I
simple get the message "Aborted" and it does not join the domain
> if it going on for all printers add to smb.conf
> cups options = "job-hold-until=indefinite"
I don't mean to be difficult, but, if I read the smb.conf man page correctly,
this means that all jobs printed through Samba to CUPS will be held
indefinitely. This is not the behavior I'm looking
> The -o job-hold-until=when option tells CUPS to delay printing until the
> "when" time, which can be one of the following:
Well, I found the option in the Printing Preferences under the Windows
driver, but setting it has no effect - the job prints immediately. Something
else I need to do?
> for printer queue holding managed by cups so can be deployed on any printer.
> have a look at the following cups options
> Holding Jobs for Later Printing
> The -o job-hold-until=when option tells CUPS to delay printing until the
> "when" time, which can be one of the following:
> * -o jo
>
>>
>> the whole point of using CUPS is to get rid of the broken drivers in the
>> first place
>>
>> all PPD options are passed though to the windows client
>> http://svn.easysw.com/public/windows/trunk/x64/
>> http://svn.easysw.com/public/windows/trunk/i386/
>>
>
This may just work, excep
> Ricoh-Aficio_MP_C4500 supports postscript and has a manufacture ppd so there
> are no issues like that here
>
> http://www.openprinting.org/printer/Ricoh/Ricoh-Aficio_MP_C4500
>
Yes, and I actually have the PPD installed for the MP C6501SP that I'm using.
However, the PPD doesn't seem to inc
> Which driver are you referring to? Does the driver not have options to
> disable printer communication?
It's a driver for a Ricoh Aficio MP C6501SP. No, there is no option to disable
bi-directional printer communication. My Canon imageRunner drivers do have
this option, and even let you sp
>>> On 2010/05/20 at 13:43, Damien J Dye wrote:
> Why are you not using the cups printer drivers in the cups enviroment there
> are both x64 and i386 versions and gets round the issues with broken drivers
> and allows cups features to be passed to windows.
>
There are several "special" functi
>
> Have you looked at granting rights like:
>
> net -U"ADuser" rpc rights grant "ADdomaingroup" SePrintOperatorPrivilege
>
> There are several different privileges that can be granted in this manner.
Thanks, Mike,
I actually figured out the issue, thought I'm not sure why this is the case.
I'm attempting to configure Samba with CUPS as a centralized print server.
I've done this in the past - my current production server is running Samba
3.2.14. On my current production server, I have several users set up as either
"admin users" or "print admin" users so that they can manage the
bug report, unless sommeone can tell me that
this behavior is intentional.
Thanks,
Nick Couchman
On Tue, 2006-10-17 at 12:43 -0600, Nick Couchman wrote:
> Well, I'm attempting to migrate my old NT4-based domain to Samba3. I've
> got Samba set up with an LDAP backend, I've exte
Well, I'm attempting to migrate my old NT4-based domain to Samba3. I've
got Samba set up with an LDAP backend, I've extended my NDS schema, and
I've got users in this new domain set up successfully and authenticating.
I've decided that the best, most seamless way to migrate my domain is to
create
24 matches
Mail list logo
