Displaying 20 results from an estimated 10000 matches similar to: "winbindd... PANIC: could not fetch our SID, did we join?"
2006 Apr 11
0
PANIC: Could not fetch our SID - did we join?
Hi,
I have some problems running Samba and Winbind 3.0.22 in a AD, kerberos
environment.
I have seen previous posts on several forums about this problem but
haven't found any solution for it yet.
I have no problem with the default Samba package that comes with Ubuntu,
3.0.14a.
But I do wan't to upgrade and the only option in that case seems to be
to compile it.
I compiled it with
2007 May 03
0
PANIC: Could not fetch our SID - did we join?
Hey there,
I'm getting the same error as you, "Could not fetch our SID - did we join?".
Have you made any progress with that error? Thanks!
2016 Apr 24
1
Unable to start winbindd, Could not fetch our SID - did we join?
I've been searching this lists archives and using the Googles for two days
now, and keep coming across the same messages from before 2012 with the
errors I'm getting, so either I'm seeing something new, or I've missed
something stupid.
I've been following the HOWTOs here from Samba.org. In each case below, I
uninstalled the provided Samba packages and built from source.
2017 Nov 13
0
Winbind error "Could not fetch our SID - did we join?"
Making no additional changes to the configuration, using "net ads join"
instead of "samba-tool domain join" immediately worked. I'd be really
curious where's the difference between the two and why samba-tool
pretends to not have run into any errors…
On 2017-11-13 13:40, Sven Schwedas via samba wrote:
> On 2017-11-13 13:31, Rowland Penny wrote:
>> On Mon, 13
2017 Nov 13
0
Winbind error "Could not fetch our SID - did we join?"
On 2017-11-13 14:55, Rowland Penny wrote:
> On Mon, 13 Nov 2017 14:32:11 +0100
> Sven Schwedas via samba <samba at lists.samba.org> wrote:
>
>> Making no additional changes to the configuration, using "net ads
>> join" instead of "samba-tool domain join" immediately worked. I'd be
>> really curious where's the difference between the two
2017 Nov 13
0
Winbind error "Could not fetch our SID - did we join?"
On 2017-11-13 16:00, Rowland Penny via samba wrote:
> 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.
>>
2017 Nov 13
2
Winbind error "Could not fetch our SID - did we join?"
On Mon, 13 Nov 2017 14:32:11 +0100
Sven Schwedas via samba <samba at lists.samba.org> wrote:
> Making no additional changes to the configuration, using "net ads
> join" instead of "samba-tool domain join" immediately worked. I'd be
> really curious where's the difference between the two and why
> samba-tool pretends to not have run into any errors…
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,
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
2011 Sep 18
0
upgrade to 3.6.0 Could not fetch our SID - did we join?
Dear
I have upgraded from 3.5.11 to 3.6.0
in old version, Server was connected to an Active Directory and no
problems occurs.
when restarting winbind :
Sep 19 01:17:34 onesys-samba winbindd[4818]: [2011/09/19
01:17:34.326691, 0] winbindd/winbindd_util.c:635(init_domain_list)
Sep 19 01:17:34 onesys-samba winbindd[4818]: Could not fetch our SID -
did we join?
Sep 19 01:17:34 onesys-samba
2005 Jul 08
0
net getlocalsid can't fetch domain SID?
I'm running into an odd problem with my installation of samba, version
3.0.13. Samba is configured to use the tdbsam backend and is running as a
PDC. The issue is that samba can't seem to report its SID correctly:
# net getlocalsid
[2005/07/08 12:27:30, 0] utils/net.c:net_getlocalsid(494)
Can't fetch domain SID for name: DOMSERVR
but, running an alternate command:
# net rpc info
2007 Sep 07
3
PDC (can't fetch domain SID)
os: debian etch 4.0
samba: 3.025c
i am reading through the how-to (using samba 3rd ed), freely available btw
at http://book.opensourceproject.org.cn/sysadmin/samba/sambao3rd/
i am interested in setting up a samba pdc for a good dozen windows xp pro
clients. (i somehow could not wake up from the windows 2003 sbs nightmare).
i have been able to join my debian box to the local windows domain and
2017 Nov 13
2
Winbind error "Could not fetch our SID - did we join?"
We did, in fact, join mere seconds ago, but for some reason, winbind
still can't find itself. ADUC etc meanwhile have no trouble finding the
newly added computer account.
Wiping /var/{lib,cache}/samba/ (and the computer account) makes no
difference, the error persists.
How do I proceed?
--
Mit freundlichen Grüßen, / Best Regards,
Sven Schwedas, Systemadministrator
Mail/XMPP sven.schwedas
2005 Mar 05
2
Can't fetch domain SID
Hi,
I happened to delete /etc/samba/secrets.tdb. Now I can not get DOMAIN
SID by run:
net getlocalsid
Any idea how to recover it? Do I need to reinstall the whole Samba suite?
--
Regards,
Steve Zeng
Systems Administrator
Mainframe Entertainment Inc
T: (604) 628-1000 ext 5293
2017 Nov 13
2
Winbind error "Could not fetch our SID - did we join?"
On 2017-11-13 12:33, Rowland Penny via samba wrote:
> On Mon, 13 Nov 2017 12:05:33 +0100
> Sven Schwedas <sven.schwedas at tao.at> wrote:
>
>> /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
>>
2017 Nov 13
3
Winbind error "Could not fetch our SID - did we join?"
On 2017-11-13 13:31, Rowland Penny wrote:
> On Mon, 13 Nov 2017 13:18:20 +0100
> Sven Schwedas via samba <samba at lists.samba.org> wrote:
>
>> Could we please not waste a week poking at random unrelated stuff this
>> time? These "I try the same stuff no matter what the problem is"
>> boilerplate emails become really grating after the first few times. :/
2015 Mar 27
0
winbindd: Failed to fetch our own, local AD domain join password for winbindd's internal use
Hai Tom,
Im not in 4.2 yet, but maybe i can help analize your problem. ( as long its possible, big power outage in the netherlands.. )
this : https://lists.samba.org/archive/samba/2014-September/185031.html
is a good example how not to setup your samba server.
so before we can think with, please post (and sorry if its again) some info.
Your OS?
Compiles samba or os provided samba, or
2005 Feb 08
1
Domain SID issue
Hello
I have a client who historical had a machinename with an underscore
in it : samba_machine
I had to get rid of the underscore names and changed the name
to samba-machine. At the same time I upgraded to samba-3.0.11 to
get a printer queue problem resolved.
Now it seems the Domain SID has changed, so I changed the new SID
back to the old one with net setlocalsid, because on all machines I had
2015 Mar 26
3
winbindd: Failed to fetch our own, local AD domain join password for winbindd's internal use
Hello,
I apologize in advance for cross-posting (and posting for help) to
samba-technical, but I've been seeking help on the samba list and bugzilla
since last week and have had no replies. Using Google, I've found this
issue referenced only once on the mailing list and once in a bugzilla bug
(10991). Unfortunately, I've found no resolutions.
The problem appears to be specific to
2014 Nov 02
2
SID of member server in Samba domain (smbldap_search_domain_info: NT_STATUS_UNSUCCESSFUL)
I have a domain with Samba 3 acting as PDC, and using LDAP (passdb backend = ldapsam).
I now wanted to add a second Samba 3 machine as a simple file server. I get errors
with getdomainsid and getlocalsid, so there is obviously still something wrong with
my config.
The PDC runs Samba 3.5.6 on Debian Squeeze. Sid queries return:
# net getdomainsid
SID for local machine MY_PDC_HOST is: