search for: _windows_

...#39;t seems to works. I have a samba3 (4.1.17-Debian) NT domain, I have a new AD domain (4.10.4) and I have a user in AD domain with the same credentials in the NT domain. I have joined a windows PC to the AD domain and when the user logon to the PC he can successfully works on all pc/server _windows_ shares joined to NT domain but can't on _samba_ shares joined to the NT domain. Please can someone help me to troubleshoot the problem? Thank you very much Piviul

...sswd -a root` isn't relevant, both because smbpasswd is deprecated in Samba 3.x and because most Samba-LDAP systems are configured to look _only_ to LDAP for their "passdb backend" and so never see the information you tried to set up through `smbpasswd`. Some Samba operations use the _Windows_ privileges. They cannot be performed even by a Samba superuser if that user doesn't also have the right Windows privileges. Somewhere _inside_ Samba you need to define what will be the user you use for joining machines to the domain to include sambaSID <domainSID>-500 (S-1-5-21-...-500) a...

...h before win32.h) and drop the namespace and the conflicting names. On Tue, Jan 23, 2018 at 12:46 AM, Zachary Turner <zturner at google.com> wrote: > That's very possible that a 3rd party indirect header include is > involved. One idea might be like I suggested where you #define _WINDOWS_ > in win32.h and guarantee that it's always included first. Then those other > headers won't be able to #include <windows.h>. but it will probably > greatly expand the amount of stuff you have to add to win32.h, as you will > probably find some callers of functions that...

That's very possible that a 3rd party indirect header include is involved. One idea might be like I suggested where you #define _WINDOWS_ in win32.h and guarantee that it's always included first. Then those other headers won't be able to #include <windows.h>. but it will probably greatly expand the amount of stuff you have to add to win32.h, as you will probably find some callers of functions that aren't yet in yo...

...d that you never intentionally import win32.h and > windows.h from the same translation unit. But then in this example you > did. I wonder if you could enforce that by doing this: > > // win32.h > #pragma once > > // Error if windows.h was included before us. > #if defined(_WINDOWS_) > #error "You're including win32.h after having already included windows.h. > Don't do this!" > #endif > > // And also make sure windows.h can't get included after us > #define _WINDOWS_ > > For the record, I tried the test case you linked when windows...

...space and the > conflicting names. > > > On Tue, Jan 23, 2018 at 12:46 AM, Zachary Turner <zturner at google.com> > wrote: > >> That's very possible that a 3rd party indirect header include is >> involved. One idea might be like I suggested where you #define _WINDOWS_ >> in win32.h and guarantee that it's always included first. Then those other >> headers won't be able to #include <windows.h>. but it will probably >> greatly expand the amount of stuff you have to add to win32.h, as you will >> probably find some callers of...

...ng names. >> >> >> On Tue, Jan 23, 2018 at 12:46 AM, Zachary Turner <zturner at google.com> >> wrote: >> >>> That's very possible that a 3rd party indirect header include is >>> involved. One idea might be like I suggested where you #define _WINDOWS_ >>> in win32.h and guarantee that it's always included first. Then those other >>> headers won't be able to #include <windows.h>. but it will probably >>> greatly expand the amount of stuff you have to add to win32.h, as you will >>> probably find...

...> On Tue, Jan 23, 2018 at 12:46 AM, Zachary Turner <zturner at google.com> >>>> wrote: >>>> >>>>> That's very possible that a 3rd party indirect header include is >>>>> involved. One idea might be like I suggested where you #define _WINDOWS_ >>>>> in win32.h and guarantee that it's always included first. Then those other >>>>> headers won't be able to #include <windows.h>. but it will probably >>>>> greatly expand the amount of stuff you have to add to win32.h, as you will &g...

...gt;> >>> On Tue, Jan 23, 2018 at 12:46 AM, Zachary Turner <zturner at google.com> >>> wrote: >>> >>>> That's very possible that a 3rd party indirect header include is >>>> involved. One idea might be like I suggested where you #define _WINDOWS_ >>>> in win32.h and guarantee that it's always included first. Then those other >>>> headers won't be able to #include <windows.h>. but it will probably >>>> greatly expand the amount of stuff you have to add to win32.h, as you will >>>&g...

...46 AM, Zachary Turner <zturner at google.com> >>>>>> wrote: >>>>>> >>>>>>> That's very possible that a 3rd party indirect header include is >>>>>>> involved. One idea might be like I suggested where you #define _WINDOWS_ >>>>>>> in win32.h and guarantee that it's always included first. Then those other >>>>>>> headers won't be able to #include <windows.h>. but it will probably >>>>>>> greatly expand the amount of stuff you have to add to...

...23, 2018 at 12:46 AM, Zachary Turner <zturner at google.com> >>>>> wrote: >>>>> >>>>>> That's very possible that a 3rd party indirect header include is >>>>>> involved. One idea might be like I suggested where you #define _WINDOWS_ >>>>>> in win32.h and guarantee that it's always included first. Then those other >>>>>> headers won't be able to #include <windows.h>. but it will probably >>>>>> greatly expand the amount of stuff you have to add to win32.h, as...

...gt; I have a samba3 (4.1.17-Debian) NT domain, I have a new AD domain > (4.10.4) and I have a user in AD domain with the same credentials in > the NT domain. I have joined a? windows PC to the AD domain and when > the user logon to the PC he can successfully works on all pc/server > _windows_ shares joined to NT domain but can't on _samba_ shares > joined to the NT domain. Just because they use the same password does not make them the same user. > > Please can someone help me to troubleshoot the problem? Yes, stop listening to spurious people who have never done the upgra...

...t;>>>>>> zturner at google.com> wrote: >>>>>>>> >>>>>>>>> That's very possible that a 3rd party indirect header include is >>>>>>>>> involved. One idea might be like I suggested where you #define _WINDOWS_ >>>>>>>>> in win32.h and guarantee that it's always included first. Then those other >>>>>>>>> headers won't be able to #include <windows.h>. but it will probably >>>>>>>>> greatly expand the amount of...

...rner <zturner at google.com >>>>>>> > wrote: >>>>>>> >>>>>>>> That's very possible that a 3rd party indirect header include is >>>>>>>> involved. One idea might be like I suggested where you #define _WINDOWS_ >>>>>>>> in win32.h and guarantee that it's always included first. Then those other >>>>>>>> headers won't be able to #include <windows.h>. but it will probably >>>>>>>> greatly expand the amount of stuff you ha...

Hi, the problem is that when doing smbclient -L user I'm getting NT_STATUS_ACCESS_DENIED. ,,user'' is using win xp and I can view his shares from other _windows_ computer but not with smbclient. Any ideas why? [misiek@arm ~]$ smbclient -L lookas -d4 Serverzone is -3600 Initialising global parameters params.c:pm_process() - Processing configuration file "/etc/samba/smb.conf" Processing section "[global]" doing parameter netbios name = AR...

Wine seems to be trying to run MS programs. 'wine /windows/Programs/access/office/msaccess.exe' starts 'access'. Then a error message says, FIXME:pthread_rwlock_rdlock FIXME:pthread_rwlock_unlock FIXME:pthread_rwlock_rdlock FIXME:pthread_rwlock_unlock FIXME:pthread_rwlock_rdlock FIXME:pthread_rwlock_unlock FIXME:pthread_rwlock_rdlock FIXME:pthread_rwlock_unlock

...t;>>> zturner at google.com> wrote: >>>>>>>>> >>>>>>>>>> That's very possible that a 3rd party indirect header include is >>>>>>>>>> involved. One idea might be like I suggested where you #define _WINDOWS_ >>>>>>>>>> in win32.h and guarantee that it's always included first. Then those other >>>>>>>>>> headers won't be able to #include <windows.h>. but it will probably >>>>>>>>>> greatly expand th...

...t; zturner at google.com> wrote: >>>>>>>>>> >>>>>>>>>>> That's very possible that a 3rd party indirect header include is >>>>>>>>>>> involved. One idea might be like I suggested where you #define _WINDOWS_ >>>>>>>>>>> in win32.h and guarantee that it's always included first. Then those other >>>>>>>>>>> headers won't be able to #include <windows.h>. but it will probably >>>>>>>>>>> great...

...he windows header. You said at the end that you never intentionally import win32.h and windows.h from the same translation unit. But then in this example you did. I wonder if you could enforce that by doing this: // win32.h #pragma once // Error if windows.h was included before us. #if defined(_WINDOWS_) #error "You're including win32.h after having already included windows.h. Don't do this!" #endif // And also make sure windows.h can't get included after us #define _WINDOWS_ For the record, I tried the test case you linked when windows.h is not included in main.cpp and it...

...gt;>>>> >>>>>>>>>>>> That's very possible that a 3rd party indirect header include >>>>>>>>>>>> is involved. One idea might be like I suggested where you #define >>>>>>>>>>>> _WINDOWS_ in win32.h and guarantee that it's always included first. Then >>>>>>>>>>>> those other headers won't be able to #include <windows.h>. but it will >>>>>>>>>>>> probably greatly expand the amount of stuff you hav...