similar to: HEAD/TNG Problems.

I'm having problems sharing folders on my Windows PC. Whenever I try to share a folder, I get the option to choose the permissions for Everyone. This much is fine, and normal. I then try to add a user to the list, but I get told the user doesn't exist! My domain is CSMNET and the user 'csm'. I've tried entering 'csm', 'CSMNET\csm', and 'csm@csmnet'

ftp://samba.org/pub/samba/alpha or mirror sites. this version has security = domain tested and, shock-horror, working. it is possible to do SMB connections with WORKSTATIONNAME\username (wow) and actually, this is _necessary_, because otherwise, how are you going to join it to a domain? :-) :-) as root: samedit -S . -U root% -l log [] createuser root -p rootpassword [] exit samedit -S thepdc

ftp://samba.org/pub/samba/alpha and mirror sites rpcclient and samedit etc. on sun ultras were failing because getopt cannot be reused. evidence of this is by doing a samedit "createuser username -p password" and the reported password on-screen is total garbage. this was fixed by using the GNU getopt and getopt_long functions (hooray!) in the same way that rsync does. i have access

ftp://samba.org/pub/samba/alpha and mirror sites 1) i fixed a problem with nmbd's GETDC response, it is responding better but still not perfectly (and 2.0.x and cvs main need to be fixed, as well) as there exists no explanation for the correct response to locate a Domain Controller using GETDC. the upshot of fixing this is that joining an nt workstation to a TNG domain is now _extremely_

when an nt 4.0 workstation or backup domain controller is joined to a domain, the trust account password is set to a well-known initial value. if you are concerned about internal network security, this is not really an acceptable risk: any captured network traffic can be decoded simply from knowing the name of the workstation, which is contained in the network traffic itself. the initial value

update: - fixed smbd for win95-style profile-locating (it now works, thank you to everyone who sent in log files to get this fixed) - various modes tested and confirmed as working: * ROLE_STANDALONE security = user encrypt passwords = yes domain master = no domain logons = no * ROLE_DOMAIN_PDC security = user encrypt passwords = yes domain master = yes

Edit the file called src/EDITME and put the result in a file called Local/Makefile. Then you may proceed ... and next time ... you post an error message you may want to be specific ... not "or something like that" ... On Mon, 21 May 2001, Mager Charles WB wrote: > Again another email ALMOST off the point, but not quite. The first question, > which is to do with samba, is - How

remove unix password sync = yes Reply on a question.... http://www.mail-archive.com/redhat-devel-list@redhat.com/msg04223.html Good Luck, Ries Return-Path: <ries@franksintl.nl> Delivered-To: samba@lists.samba.org Received: from tiny.int.franksintl.nl (goblin.franksintl.nl [195.193.231.154]) by lists.samba.org (Postfix) with ESMTP id 6771C4AC8 for <samba@lists.samba.org>; Thu, 17

Am going thru the learning curve on using samba as a primary controller. Samba is up and running just fine. However, I'm a bit confused on the ntlogin.pol thing. I'm gathering, if all the workstations are winxp, I need to do this?? "Go to the Windows 200x/XP menu Start->Programs->Administrative Tools and select the MMC snap-in called Active Directory Users and Computers

Hi... I have exactly the same problem with lsarpcd giving the error "ERROR: setgroups call failed!". Anyone know of a fix?? MWP > Hello > > I was just installing the new TNG 1.0.5 and after i installed and cleaned the > logs i started the dameons and was unable to access the shares on win98. The > computer showed up in Network Neighborhood but i would get a \\comp03

ftp://samba.org/pub/samba/alpha and mirrors. due to some confusion about how to use samedit's createuser command, i put a warning / security message in whenever createuser hostname$ is used. it basically says, now you can join the workstation to the domain because you have just set the trust account to the insecure, well-known initial value, and you had best join the workstation to the

Hi everyone, First of all, could you please CC me, I am not (yet) subscribed to this list. Now my problem: I created a test setup at my office that uses winbind to authenticate linux users to a Windows NT server (they log in with DOMAIN+username), as described in the winbindd manpage. I followed their setup completely. (at my work I am using RedHat 7.1 and the winbindd daemon found in the

I have compile rpcclient using the last CVS, and have some questions regarding it. I would like to use rpcclient with perl to do a remote shutdown to NT Workstations on lan. >From my linux box ( Running Samba 2.0.6 ) I can successfully connect to the remote NT4.0 Wks, but the list of commands that I have access is only regenum regdeletekey regcreatekey regquerykey regdeleteval

On 02/26/16 09:54, Gene Cumm via Syslinux wrote: >> >> I'm not exactly sure how that would work (how would you mark those clusters >> as wasted when my understanding is that the FAT's can't provide any >> knowledge about them in the first place?) and unless it is automatically >> integrated and ran during the Syslinux installation, it sounds quite >>

Hi, well, I guess that this is something that I need to plan to do :-). I'm developing a plan for a group of updated docs for TNG (and Samba, compared to TNG). Quickly, you're asking for 1) A bulleted list? 2) A Kvivio flowchart? 3) Some other comparison? Could you tell me in general terms: do you need to "sell" TNG to the boss or something? I can't give it to you now.

I need to join my Samba 2.2.3a to a TNG Domain (which stores users and machines account into OpenLDAP) using it as a password server. Provided that TNG is working fine in authenticating users on W2K machines, once they are logged in they should (in my intentions) see Samba 2.2.3a shares. In order to do this I provided the following configuration for Samba: workstation = <tng_domain>

I'm using an ldap-backed TNG PDC for domain logins with no problem. I've got a samba 2.2.8a fileserver that doesn't seem to correctly map usernames to domain SIDS. It is passing authentication requests to the PDC correctly, and allows users to map non-public shares, write to their home directories, etc. When a file's "security' attributes are viewed in windows explorer,

Just a small question before I dare to install Samba TNG: Is there any functionality in the latest Samba TNG (I think 0.3.2) which is *not* implemented in Samba 3.0? TIA! :) -- Best regards, Bernhard Lukas Pericom Communication Consulting GmbH 1060 Wien, Mariahilfer Strasse 47/1/3 Tel. 01 585 49 72 - 42 Fax. 01 585 49 72 - 33 Web. www.pericom.at

Hello, I have inherited a samba-tng PDC (without ldap) that I am to upgrade to samba 3. My first attempt failed miserably. I copied over the smbpasswd and the domain SID, users were able to log in, but most were not able to load their profiles. I think I have to copy over machine IDs, but I'm not sure how to proceed. The migration section of the the howto doesn't seem to apply to

Hello all: I just recieved Windows 2000 Professional Final Release. I am currently running Samba in order to serve my Windows 95 & Windows 98 Machines. From my understanding, I needed to get something called TNG. I read instructions on CVS and it downloaded TNG onto my computer. Then I went on and did "./configure", "./make", and am about to do "./make