similar to: Noob question about cached credentials

Being that you SAMBA developers had to work so hard to reverse engineer the AD protocols. Will there soon be improvements and more full featured functionality in SAMBA now that you have access to more documentation? Is anything on the order of a fully feature AD clone in the works. Also, how do you dance around patented protocols? Can you still implement them? Do you have to avoid them?

I'm running Samba 2.27 on RH8 system. I've got samba as the print spooler for Windows XP clients and using winbind as the user validation against my Win2K DC. Permissions on the spool directory are root root with the sticky bit on. Clients can delete their own jobs from the que, but the spool directory is not being expunged of print jobs and the last job constantly displays in the client

I have the Win2000 client(s) in a Samba domain. Domain authentication works fine, my "homes" share works fine, remote profiles work fine. Using 3.0.1Pre1 I would like to add people to "someshare" through the Security tab, and control their access through windows ACL's. How should I setup a share as a basis for doing this? The share below (someshare) in this email

I'm trying to establish a two way non-transitive trust between a W2003 A/D box and our SAMBA domain. We are using smbldap so we can log in on any of the linux boxes with the same passwd. Samba is version 3.0.33 on Redhat Enterprise. It's easy to create the trust on the Windows side with AD Domains and Trusts but on the Linux side I'm not sure if I need to put the machine account

I have ACL's enabled and am getting a new error, in the Samba log (V 3.0.1Pre1, when attempting to set permissions on a file through Win2000: get_domain_user_groups: primary gid of user [terry] is not a Domain group ! get_domain_user_groups: You should fix it, NT doesn't like that Do I need to create a group on the windows(2000) side? The entries in the domaingroup.map

Hi we are using a recent samba server in an AD W2003 domain. The AD DC's are located at the main location. The samba member servers (file-servers) are located at the outside locations. A User is able to logon to his Workstation, even if the Domaincontroller is not available, if he has already logged on to this workstation earlier (the clients caches the credentials). But the client is

Hallo, I wonder if cached credentials local logins are expected to work with samba. I have users with notebooks that I want to be domain members. If the notebook is in the wild I want the users to use their profiles (either local or roaming) stored on the notebooks. But once disconnected from the network the users can't login. I found a thread:

Hi! Winbind is rather suboptimally reacts to networking changes. I use my notebook in at least 3 different network settings, in one of them I have very probabilistic access to DCs (cisco vpn client is a crap). An nss lookup sometimes takes very looong, sometimes even returns failure. Sometimes I have to login as root and restart winbind to get to my X session past the screensaver. This is far

Hello all, I'm setting up a domain using Samba 3.0 as PDC, with WinXP clients. One of these clients is a laptop, which should be able to use cached profiles of the domain users. Online logon is working fine, however when the domain server is not available it cannot logon, whereas it should be able to use cached credentials to access the cached profile. Windows says it cannot log on because

On 5/6/2018 1:23 PM, Rowland Penny via samba wrote: > On Sun, 6 May 2018 12:51:33 +0200 > john doe via samba <samba at lists.samba.org> wrote: > >> Hi, >> >> I'm in the process of replacing my samba server 3.6.x (Debian wheezy, >> stable) to samba 4.5.x (Debian stretch, stable). >> >> I'm facing one mageor opstacle: >> >> When

Hello all, I am having some difficulties after migrating the PDC from one server to another cached credentials no longer work. Users used to be able to take their laptops home and then logon using their cached domain credentials. Now when this is attempted now they get the error that the GAUACA domain is not available. All of the group policy settings are set to allow cached logons and

Hello all, I'm setting up a domain using Samba 3.0 as PDC, with WinXP clients. One of these clients is a laptop, which should be able to use cached profiles of the domain users. Online logon is working fine, however when the domain server is not available it cannot logon, whereas it should be able to use cached credentials to access the cached profile. Windows says it cannot log on because

I have modified the native config files both Ubuntu and CentOS systems (laptops) to allow them to be added to a genuine Windows Active Directory domain. When on the network logins work fine. ? Take the systems off the network, and the user, even though their credentials are cached, cannot log in. There are several documented bugs on this for both Ubuntu and RedHat. Some people have posted

Hi, I'm in the process of replacing my samba server 3.6.x (Debian wheezy, stable) to samba 4.5.x (Debian stretch, stable). I'm facing one mageor opstacle: When I do "net view \\<SAMBA-3-SERVER>" a list of the available shares is displayed. But if I do the same command "net view <\\SAMBA-4-SERVER>" I get the following error: "System error 5 has

With Samba v3.x and WinXP, if there is a local profile on the users PC when the user logs on while hooked to a Samba DC, should the PC check for the DC profiles password prior to checking the local profiles password? I have a client PC, originally with no local profile, the user logs in to the Samba domain, his profile is downloaded to the PC. I have his group policy set so it won't

My win2000 laptop caches the domain credentials so I can log into the computer when disconnected from the network. However, Windows XP SP2 laptops cannot. I get a "domain unavailable error" even though the local security profile on the laptop is set to allow domain credential caching. My other client, with XP laptops and a Windows 2000 server, has no problem. Is this a Samba 3.0.8

I have three Windows XP (All SP2) machines that won't cache credentials with a Samba DC. A Debian Sarge system with Samba 3.0.10 is the domain controller. It has three users and three machine accounts. The three users all are simple Unix users, with no mapping to Windows users. We use DHCP (entirely different server) and DNS, but local IPs do not resolve. The configuration files for Samba

I am running Samba 3.5.5 on Solaris 10. I have one machine as a PDC, one as a BDC. If I logon to the domain from a Windows 7 Pro (64-bit) laptop, hibernate the machine, unplug the network cable and wake the machine, I can not unlock the screen. I will get the message "There are currently no logon servers available to service the logon request." Other users have reported this.

Greetings, I'm working on the infrastructure of a medium size client/server environment using an Active Directory running on Windows Server 2003 for central authentication of users on linux clients. Additionally OpenAFS is running using Kerberos authentication through Active Directory as well. Now I want to grant users remote access to their AFS data by logging in into a central OpenSSH

Il 18-09-2015 01:50 Jeremy Allison ha scritto: > > Currently a Samba member server must contact the DC > for authentication even if a krb5-PAC is presented. > > This is a bug, and one I'm working on fixing (it > is a regression from earlier behavior). Hi all, sorry for resurrecting this very old thread, but I would like to know if the situation improved over time. In