similar to: Unix server joining NT4 Domain--User question

When I run configure for the new release, R-0.63, I get an error: loading cache ./config.cache checking for a BSD compatible install... aux/install-sh -c checking whether ln -s works... yes checking for ranlib... ranlib checking for bison... bison -y checking for ar... ar checking for ratfor... no checking for latex... /psoft/TeX/bin/latex checking for dvips... /psoft/TeX/bin/dvips checking for

When I run configure for the new release, R-0.63, I get an error: loading cache ./config.cache checking for a BSD compatible install... aux/install-sh -c checking whether ln -s works... yes checking for ranlib... ranlib checking for bison... bison -y checking for ar... ar checking for ratfor... no checking for latex... /psoft/TeX/bin/latex checking for dvips... /psoft/TeX/bin/dvips checking for

As an inveterate user of vi, I was pleased to stumble on how to use it for editing R commands. When an interactive R session is launched under unix, the command line editor most likely defaults to emacs. Typing <esc>,<ctrl>+j will switch this to vi editing mode (see below for possible exceptions). excerpted from readline(3) manpage: vi-editing-mode (M-C-j) When in emacs

I have set up samba-1.9.18p10 on Sun Solaris. I have created several shares and whenever a user edits a file it gets set to permission mode 0744, regardless of what it was before. The file permission can than be changed from windows using file properties. To avoid this extra step I added a create mask = 0655 to the share definition. Now the files get created with the correct permission,

Hi, since december 1999 we have successfully running Samba on HP-Unix 10.20 with nmbd version 2.04b. Suddenly it's no longer possible to connect from Win9x clients - a connect from NT-Clients still works, but connection establishing is very slow. Here is an excerpt from the log.smb file for a connect request from a Win95 client: [2000/03/22 16:54:36, 3] smbd/process.c:(974) priming

On Sat, 17 Dec 2016 22:12:28 +0100 Stefan Froehlich via samba <samba at lists.samba.org> wrote: > A new Debian(unstable) machine with Samba 4.5.2 is trying to join an > NT4-style Samba domain hosted on a Debian(wheezy) Server with 3.6.6 > which can't be changed but has been working for some years now with a > couple of windows clients. > > Joining the domain was quite

Hello all- Using samba 2.2.5 on FreeBSD 5 (a few months old). I'm trying to get my FreeBSD box to serve out samba shares using NT4 domain authentication. I've got Win2K PDCs (a couple different domains) running in mixed mode. These are the steps I'm taking: 1) As NT domain administrator, I create machine accounts in the domain for my FreeBSD box. 2) On the FreeBSD box, I

Linux: Fedora Core 2 Samba: 3.0.3 OpenLDAP: 2.1.29 I've noticed a couple of other messages in this month's archives that suggest they're having the same problem as I, but so far no resolution has been reported. I've got a new Samba domain up and running with LDAP that allows me to join Win2K and XP clients, but not NT4 workstations. I've added the machine account with the

On Sat, Dec 17, 2016 at 09:51:57PM +0000, Rowland Penny via samba wrote: > > | netbios name = DALET-STG > > | workgroup = SYNTH > > | wins support = no > > | wins server = herkules.synth.intern > > | client ipc signing = auto > > | server role = member server > > | security = domain > > | password server = herkules.synth.intern > > | idmap

On Sat, Dec 17, 2016 at 05:19:19PM -0500, Sonic wrote: > On Sat, Dec 17, 2016 at 5:07 PM, Stefan Froehlich via samba > <samba at lists.samba.org> wrote: > > In fact the problem was exactly the same with Samba 4.2.10 (shipping > > with Debian jessie). I only upgraded to 4.5.2 before posting to this > > list in order to avoid any "upgrade to the recent

I trying to join a samba-3 box with shares to a Windows 2k dc running in pre 2k mode and act as a member server. Is winbind best to use in something like this? I want to have share abcd to be started to the users that is apart of the windows 2k dc.

Hi, I am trying to join xp clients to an NT4 style domain based on a samba server. The join appears to work and the welcome message pops up. Upon restarting the client, I am not able to log in using domain accounts. When I log in as the local admin, I find that the domain account groups have not been added to the local groups. Once I add the domain accounts manually, everything seems to work

Hello! It seems, that Vista SP1 and Server 2008 cannot join an NT4/Samba-domain. Vista once could join before SP1, if one did some modifications to the system (LAN Manager authentication level, Encryption of secure channel). But these workarounds do not seem to work with SP1 anymore. Microsoft points out that joining NT4-domains with Vista SP1 and Server 2008 is not supported/tested

I am a Unix Admin, trying to join a NT4 domain. I do not have access to the PDC. When setting up a new machine, either Windows or Unix, on the domain, I ask the NT admins to create a new machine account on the domain for my machine. I then "associate" my machine with that machine account. I say "associate" because I'm not exactly sure what happens, something about

Hi all, I try to join samba3 to NT4 domain: My smb.conf is following: [global] workgroup = MYDOM netbios name = LANSERVER server string = Samba Server security = domain hosts allow = 10. 127. log file = /var/log/samba/log.%m max log size = 50 password server = PDC #encrypt passwords = yes #winbind uid = 10000-20000 #winbind gid = 10000-20000 idmap uid = 15000-20000 idmap gid =

Hello I'm having some dificulties joining my Samba 3.0alpha (and 2.2.7a) machine to my NT4 domain. Let me tell you what I'm attempting to accomplish. I want to setup the Samba system to authenticate to my NT domain so that I can use NTLM Proxy authentication with SQUID. Through reading the docs, I'm under the impression that in order to allow thre SQUID/Samba setup to auth on

I have 2 AIX systems that run Samba. We are currently on an NT4 domain and moving to Active directory. I am trying to find out what all would be needed to make that transition. The only authenification is for users connecting to their shares. I read one site via Google that states I need to create a user (Rocky) on both Samba and the AD server with different passwords but this does not seem

Hi, I am still wrestling with WinNT4 domain PDC which does not like a Samba member. I updated PDC to SP6a. I also verified that this admin username/password indeed can be successfully used to join an NT workstation to the domain. I narrowed samba failure down to net join silent failure. It says "Joined domain PORT" but logs reveal that actually joining failed. I did several runs of

A new Debian(unstable) machine with Samba 4.5.2 is trying to join an NT4-style Samba domain hosted on a Debian(wheezy) Server with 3.6.6 which can't be changed but has been working for some years now with a couple of windows clients. Joining the domain was quite easy (only surprise was "client ipc signing"), and "wbinfo -u" gives me a list with all domain users. BUT

Our office is a mix of XP and NT4 clients. I've been running Fedora Core 3 for some time with samba-3.0.10-1.fc3.i386.rpm with no problems. When I upgraded to Fedora Core 4 with samba-3.0.14a-2.i386.rpm NT4 clients can no longer authenticate. [2006/02/08 14:17:22, 5] auth/auth.c:check_ntlm_password(271) check_ntlm_password: unix authentication for user [zzz] FAILED with error