similar to: AIX 7.1 Samba 3.6.23 Windows 2003 Server AD

> On 2/16/2015 10:14 AM, Thomas Schulz wrote: >>> My apologies for being too new to this whole process... >>> >>> Server was AIX 5.3/Samba 2.2.7, authenticating only against the AD. No >>> single sign-on, kerberos, or LDAP to my knowledge; smbd processes never >>> load kerberos or LDAP libraries. Upgraded to AIX 7.1/Samba 3.3.12, which >>>

My apologies for being too new to this whole process... Server was AIX 5.3/Samba 2.2.7, authenticating only against the AD. No single sign-on, kerberos, or LDAP to my knowledge; smbd processes never load kerberos or LDAP libraries. Upgraded to AIX 7.1/Samba 3.3.12, which didn't go smoothly; customer is upgrading to Windows Server 2012 AD in a couple of months, so upgraded again to Samba

> On Fri, Aug 26, 2016 at 12:19:30PM -0400, Thomas Schulz via samba wrote: > > I am testing Samba 4.5.0rc2 on a Solaris 10 i386 box. log.smbd contains > > a new message/error that does not show up on Samba 4.4.5. The error is: > > > > [2016/08/26 11:45:54.886237, 0] > > ../source3/rpc_server/rpc_service_setup.c:539(dcesrv_ep_setup) > > dcesrv_ep_setup:

I am testing Samba 4.5.0rc2 on a Solaris 10 i386 box. log.smbd contains a new message/error that does not show up on Samba 4.4.5. The error is: [2016/08/26 11:45:54.886237, 0] ../source3/rpc_server/rpc_service_setup.c:539(dcesrv_ep_setup) dcesrv_ep_setup: Loading shared RPC modules failed Dispite that, Samba 4.5.0rc2 seems to work correctly. Is this a problem or not? Tom Schulz Applied

This problem shows up on both Linux and Solaris. I am going to show the logs from a Fedora 2.6.25-14.fc9.i686 machine. We are using 'security = domain' with a Windows 2000 domain controller. We are setting 'password server = starfish2' dispite the fact that the documentation says that this in not necessary as we have found it to be necessary. We are setting 'workgroup =

Hello all, We have a script that does a nightly backup of a windows server to a linux fileserver. The linux system uses smbclient to make a tarball of the share. I get this error when running smbclient: Domain=[OURSERVER] OS=[Windows 5.0] Server=[Windows 2000 LAN Manager] tar: dumped 56781 files and directories Total bytes written: 9800680960 write_data: write failure. Error = Connection

Hello, I am running Debian testing x64 and have manually installed the 6.03pre17 deb packages for extlinux, pxelinux, syslinux, syslinux-common, syslinux-stuff and syslinux-utils. I have a working tftpd-hpa 5.2-18 PXE system and can boot PCs to it. All .c32 binaries, gpxelinux.0 and memdisk are from the Debian packages and everything works except for http/https sources of ISOs. I have tried both

> > Good morning. > > I am looking to resolve the above vulnerability on our T-4 Solaris boxes. I have not worked or patch Samba before and not sure of the process. > > When I find and apply the patch will it resolve the issue on the version that we are running or do I need to bring our current version more up to date? > > Any assistance would be greatly appreciated.

Ady, I had not previously tried three slashes, but have now. No difference unfortunately. I've also tried using the web server on the same machine as the PXE server and using 'http://127.0.0.1/Software/Util1.iso' as the URL, again to no avail. It appears not to be able to connect to anything via http or https. Presumably it uses network settings (such as the gateway) provided by the

hi! Sorry in advance if I am not on the right mailing-list and sorry if my question is cover somewhere is doc (I didn't find anything). The result from nmblookup (same result on all platform) for a given samba server isn't what I expect. The key part of my smb.conf is: [global] netbios name = ourserver2 netbios aliases = ourserverdev ourserverlab ourserver name

> On Fri, 30 Sep 2016 10:14:32 -0400 (EDT) > Thomas Schulz via samba <samba at lists.samba.org> wrote: > > > We are running Samba 4.4.6 as a file server. > > In the logs for a few client machines I see entries such as: > > > > [2016/09/29 22:36:58.862575, 0] > > ../source3/param/loadparm.c:4402(widelinks_warning) > > Share 'IPC$'

The good news is I believe I got Weakforce running 1) curl -X GET http://127.0.0.1:8084/?command=ping -u wforce:ourpassword {"status":"ok"}[ 2) after running the sample for loop: for a in {1..101}; do curl -X POST -H "Content-Type: application/json" --data '{"login":"ahu", "remote": "127.0.0.1",

>From searching the web, I found that many people have encountered this problem. The fixes the suggested don't seem to work for me... My smb.conf file looks like this [global] workgroup = OURDOMAIN security = ADS realm = OURDOMAIN.com password server = OURSERVER encrypt passwords = yes add user script = /usr/sbin/useradd %u hosts allow = 192.168.X. 127. winbind uid = 10000-20000 winbind

>> From: schulz at adi.com (Thomas Schulz) >> To: durwin at mgtsciences.com, h.reindl at thelounge.net, > samba at lists.samba.org >> Date: 02/25/2015 06:39 PM >> Subject: Re: [Samba] Workgroup name too long >> Sent by: samba-bounces at lists.samba.org >> >>>> From: Reindl Harald <h.reindl at thelounge.net> >>>> To: samba at

Adding a section of a debug level 5 log at the end that looks like it might have some usefull information. > This problem shows up on both Linux and Solaris. I am going to show > the logs from a Fedora 2.6.25-14.fc9.i686 machine. > > We are using 'security = domain' with a Windows 2000 domain controller. > We are setting 'password server = starfish2' dispite the

>From a discussion on samba technical about the inability to have Samba work as a DC when the original DC is a Windows Server 2000 machine. > > as Andrew asked you previously, the main question is : do you have some > > specific requirements for keeping a DC on that computer (eg. Exchange or > > whatever)? > > > > If you don't need to keep the DC role on

> On 21/04/15 09:17, Peter Grotz - Obel und Partner GbR wrote: > > Hallo, > > > > > > > > samba 4.2 is released for some time now. Sernet usually doesn?t take a lot > > of time to release their new packages. > > > > But now we haven?t heard a peep from them. Are they gone or will there be > > another fine release? > > > >

> On Wed, Jun 29, 2016 at 12:11:51PM -0400, Thomas Schulz wrote: > > > > Here is what I could find. The iso file is created on a Solaris system on > > a file system that is NFS mounted from our main file server. Then it is > > burned to a CD on a Windows 7 PC through a Samba server running on a > > different Solaris machine (Solaris 10) that is also NFS mounting

Arter managing to build Samba 4.1.5 on Solaris 10 i386. I tried to join an existing Windows 2000 Server Active Directory domain as an additional domain controller. The join started to work and then died with the error: Error: Samba was compiled without the posix ACL support that s3fs requires. Try installing libacl1-dev or libacl-devel, then re-run configure and make. I downloaded acl-2.2.52 and

This may not be a Samba problem, but perhaps people here know the answer. We are installing some Windows 8.1 Pro computers. The servers running Samba 4.2.19 and 4.3.0 are not showing up in the Network display. Our domain controller is also not showing up. The Windows 7 computers are showing up. The domain controller is a Windows 2000 machine. I can manually map network drives to the servers