similar to: Samba 3, Windows 7 and printer drivers

Displaying 20 results from an estimated 9000 matches similar to: "Samba 3, Windows 7 and printer drivers"

2016 Apr 26
2
primary group gets set to 100 on Samba AD server after a while
I had similar (ish) issues. Are you using winbindd and rfc2307 UIDs/GIDs? I had to implement both of the above on my DC to resolve this. (Neither of which I /wanted/ to do.. but since switching over and running 'net cache flush' etc., the problem hasn't reoccurred) On 26 April 2016 at 09:14, Gerben Roest <g.roest at grepit.nl> wrote: > Hi, > > using Samba 4.4.2, on
2016 Apr 28
2
primary group gets set to 100 on Samba AD server after a while
I did some experimenting on my raspberry pi with samba-4.4.2 as AD server (fresh install, no upgrade), and adding a new user: samba-tool user add grepit --gid-number=513 --login-shell=/bin/bash and then checking it: root at pi6lan:/etc# wbinfo -i grepit ROEST\grepit:*:3000017:100::/home/grepit:/bin/bash root at pi6lan:/etc# id grepit uid=3000017(ROEST\grepit) gid=100(users)
2016 Apr 29
1
primary group gets set to 100 on Samba AD server after a while [SOLVED]
On 29-04-16 08:45, Rowland penny wrote: > On 28/04/16 23:12, Gerben Roest wrote: >> I did some experimenting on my raspberry pi with samba-4.4.2 as AD >> server (fresh install, no upgrade), and adding a new user: >> >> samba-tool user add grepit --gid-number=513 --login-shell=/bin/bash >> >> and then checking it: >> >> root at pi6lan:/etc# wbinfo
2016 Apr 20
2
Samba 4.4.2 as AD server: clients OK but server fails "wbinfo -K"
I have set up a samba 4.4.2 AD server, and it works fine for its Windows and Linux clients. Only the server itself behaves peculiar: Linux accounts show up as DOMAIN\username (in prompt and with whoami), on all Linux clients the user accounts are normal (just their username), and only on the server "wbinfo -K username" fails. On the clients it works. The server complains about that:
2016 May 05
1
dovecot problem with 4.4.3, not with 4.4.2
Hi, my dovecot installation dovecot-2.0.9-19.el6_7.2.x86_64 can't authenticate using winbind from 4.4.3, but it can with winbind from 4.4.2. 4.4.3: May 5 22:11:07 sambaserver auth: pam_winbind(dovecot:auth): getting password (0x00000010) May 5 22:11:07 sambaserver auth: pam_winbind(dovecot:auth): pam_get_item returned a password May 5 22:11:07 sambaserver auth: pam_winbind(dovecot:auth):
2016 Apr 29
0
primary group gets set to 100 on Samba AD server after a while
On 28/04/16 23:12, Gerben Roest wrote: > I did some experimenting on my raspberry pi with samba-4.4.2 as AD > server (fresh install, no upgrade), and adding a new user: > > samba-tool user add grepit --gid-number=513 --login-shell=/bin/bash > > and then checking it: > > root at pi6lan:/etc# wbinfo -i grepit > ROEST\grepit:*:3000017:100::/home/grepit:/bin/bash > >
2016 Apr 28
0
primary group gets set to 100 on Samba AD server after a while
On 26-04-16 23:48, Jonathan Hunter wrote: > I had similar (ish) issues. > > Are you using winbindd and rfc2307 UIDs/GIDs? I had to implement both of > the above on my DC to resolve this. (Neither of which I /wanted/ to do.. > but since switching over and running 'net cache flush' etc., the problem > hasn't reoccurred) Yes, we use winbindd and rfc2307. I have
2016 Apr 26
1
Samba 3, Windows 7 and printer drivers
Sven Schwedas <sven.schwedas at tao.at> writes: > [1:multipart/signed Hide] > > > [1/1:text/plain Hide] > > On 2016-04-26 09:02, Olivier Nicole wrote: >> Hi, >> >> With Samba 3 and Windows XP, it used to be possible to install he >> printer drivers on the Samba server, so when an XP workstation joined >> the domain, it would find the printer
2017 May 05
2
Memory leak in samba-ad-dc on 4.5.x not related to aio?
On Fri, May 05, 2017 at 10:21:05AM +0200, Sven Schwedas wrote: > On 2017-05-05 10:09, Volker Lendecke wrote: > > On Fri, May 05, 2017 at 09:42:47AM +0200, Sven Schwedas via samba wrote: > >>> root 9988 0.8 59.4 1571936 606488 ? S Apr26 114:41 /usr/sbin/samba > > > > Can you post /proc/9988/smaps somewhere? > > Sure,
2017 Sep 05
3
Server GC/name.dom/dom is not registered with our KDC: Miscellaneous failure (see text): Server (GC/name/dom@DOM) unknown
Today's episode of "why is AD break", brought to you by: > [2017/09/05 10:17:06.015617, 3] ../source4/auth/gensec/gensec_gssapi.c:613(gensec_gssapi_update) > Server GC/graz-dc-1b.ad.tao.at/ad.tao.at is not registered with our KDC: Miscellaneous failure (see text): Server (GC/graz-dc-1b.ad.tao.at/ad.tao.at at AD.TAO.AT) unknown > [2017/09/05 10:17:06.015717, 0]
2017 Nov 13
2
Winbind error "Could not fetch our SID - did we join?"
/etc/hostname:villach-file /etc/hosts:# The following lines are desirable for IPv6 capable hosts /etc/hosts:::1 localhost ip6-localhost ip6-loopback /etc/hosts:ff02::1 ip6-allnodes /etc/hosts:ff02::2 ip6-allrouters /etc/hosts:127.0.0.1 localhost /etc/hosts:192.168.16.214 villach-file /etc/krb5.conf:[libdefaults] /etc/krb5.conf: default_realm = AD.TAO.AT /etc/krb5.conf: dns_lookup_realm = true
2014 Jan 15
2
Samba 4 and Debian
I've wasted the last two days trying to get various versions of samba 4 packages getting to run under Wheezy. ? Wheezy's own packages are incomplete betas. ? Inverse provides their own packages (for SOGo), but they only care about getting their one use case to work; smbd doesn't work all, winbind has problems, and the postinst script resets my smb.conf with nonsense. Before I try
2017 Aug 24
5
sysvolreset doesn't reset all ACLs
Ok, rechecked this, your correct. This did work fine. In now at samba 4.6.7, you? This worked untill ( last i checked ) 4.6.5 :-(( now sysvolreset is totaly broken. :-(( New thing for my ToDo list.. Try this script, the rights are my defaults "after a sysvol reset" Place the script somewhere within /var/lib/samba Preffered that location . Run it with : bash script.sh sysvol/ !
2017 Sep 05
4
Server GC/name.dom/dom is not registered with our KDC: Miscellaneous failure (see text): Server (GC/name/dom@DOM) unknown
> Keytabs look reasonable, as far as I can see, but why does > graz-dc-sem have the same SPN output as graz-dc-1b in > addition to its own? A snapshotted server/cloned server? I dont know but thats not correct. I suggest, cleanup the DS with FSMO roles. Then remove a failty server and re-add it as a new installed DC. ( the good DS with FSMO) First backup:
2016 Sep 28
2
Good Bye SAMBA?!?!?
Am 28.09.2016 um 04:01 schrieb Steve Litt via samba: > Why would ANYBODY type a command when they could perform a bunch of > mouse clicks. Better yet, you can automate Windows tools with a screen > scraper and a keyboard injector, or with a top notch language like > Powershell or Visual Basic *lol* why would ANYBODY click in a GUI when he have a console - and i mean that really
2014 May 15
2
routed mode
Hi, I have installed a centos65_guest_1 system on a centos65 host with virt-manager. By default libvirt has a default network in NAT mode. At centos65_guest_1 when pinging to google it works. But I would like to use a routed mode for production enviroment with some services online, like http, ftp, ssh, etc. I have created the virtual network 192.168.100.0/24 with routed mode, and I have
2017 Nov 13
2
Winbind error "Could not fetch our SID - did we join?"
On Mon, 13 Nov 2017 15:20:05 +0100 Sven Schwedas <sven.schwedas at tao.at> wrote: > > > PS, your configs are still wrong. > > It would be *really* helpful if you explained *why*. Sprinkling magic > pixie dust over random config files isn't exactly purposeful > debugging. > Lets start with /etc/krb5.conf Samba doesn't need most of what you will find in it,
2014 Dec 05
2
Samba embedded device?
On Thu, Dec 4, 2014 at 5:19 AM, Sven Schwedas <sven.schwedas at tao.at> wrote: > Tbh, you might get away with using PCEngines' APU boards (the successor > to their Alix boards with a massively upgraded CPU) if individual > machines don't need RAID (because everything is replicated anyway). > I considered that, but what would you use for storage?? They have an mSATA
2017 Apr 20
2
NT_STATUS_NO_LOGON_SERVERS after removing a DC and WERR_BADFILE when trying to remove broken DC
On 2017-04-07 13:44, Sven Schwedas via samba wrote: > In the end I just upgraded all DCs to 4.5 and remote-deleted the broken > ones. Seemed to work without a hitch, manual removal was only necessary > to remove the IPs from DNS\_msdcs.ourdomain\gc\. Apparently not, adding new DCs failed with "WERR_DS_DATABASE_ERROR". `samba-tool dbcheck --fix` solved that. With that out of
2014 Jan 29
2
getent passwd and winbind not work
Hi, I test (replacement of nslcd ) winbind in member server. I used Samba4/Winbind howto and howto for member server. wbinfo -u and wbinfo -g work fine but getent passwd not work (getent not list user from AD) Why ? Anyone have a idea ? thx St?phane ----------------------------------- St?phane PURNELLE Admin. Syst?mes et R?seaux Service Informatique