similar to: Users can't change their own password...

Hello, I'm wondering if there's any easy way to enable a regular user to log into swat and have swat grant them root privelages, so they can use it to configure samba without having root access... Please shoot me an email at choranburg@iss.net if you have any ideas, Thanks, Chadd ********************************************************* Chadd M. Horanburg Internet Security Systems

Hello Guys, Having a bit of trouble transferring an 18GB file for backup purposes to a Samba Server. I think the 2GB limit issue was resolved a long time ago? Running Version: Version 3.0.23c-SerNet-SuSE The error on the windows client side ( this is done in some type of bat script ) file creation error the network connection was aborted by the local system. tailing the samba logs, I think the

I am having problems getting samba to run on HPUX 11. Details: HPUX 11 samba 2.2.2 and 2.2.3a gcc 3.0.1 configure options: --prefix=/samba --with-pam --without-winbind Problem: 1) I am running with logging level at 3 and see many PANIC messages. PANIC: failed to set gid log entry: [2002/03/07 18:55:58, 3] smbd/server.c:exit_server(492) Server exit (normal exit) [2002/03/07 18:56:18, 3]

Hi All, I installed samba 3.0.22 and join it to Win2003 AD domain. Users from my domain can access the samba shares successfully. My problem is that users from trusted domains can not access to my samba shares Wbinfo -m - show all the trusted domains Wbinfo -u - show all the users include the trusted domains users. Any Idea? My smb.conf global parameters: # Global parameters

We have a local network with Samba 2.0.3 on SuSE-Linux and some Windows 95 and Windows 98 clients. All works fine. Now we have got a new Windows XP computer, and we found no way to connect to the Samba server from that computer. 1. The network card works. I can ping the server, and it replies. 2. The Samba server as well as the Windows XP computer are shown in the network neighbourhood. 3.

I'm running 3.4.6 (was running 3.0.28a but upgraded in hopes to fix this issue). Clients running Windows 7 that are NOT joined to the AD domain (samba authenticates against it via "security = server") cannot authenticate to access the server. Clients running Windows 7 that are on the domain as well as Windows XP, Windows 2003 on and off the domain work as expected. Any help would

I've battled this one for a few days now and its costing my sanity so I am hoping that someone here has an answer I am running the samba server 3.0.4 on a linux 2.4.25 server. I can connect to my share point and authenticate fine I can create files or directories in the root of the sharepoint fine I can go into subdirectories and look at all the files... But I cannot create in any

My WinXP clients are able to map a network drive on my samba server. However, it takes 30 seconds to do so, and accessing the contents of the shared drive is also quite slow. Linux (smbclient) and Windows 2000 clients are able to map the share instantly, and access files without delay. I am using Linux 2.4.5, with samba 2.2.3a compiled from source on the server. The delay is consistent at 30

I have a Samba server set up to share files within a small network (with 2 clients) and I use OpenLDAP to store user accounts. I have pretty much got everything working (smbclient prints the correct information and I can browse and log into Samba via Nautilus) except I can't get the Vista client to connect to Samba, as it won't even prompt for a username and password it simply pops up

Using LDAP and the smbldap-tools. When attempting to join the domain with an administrative user, the computer gets added to the Computers list in LDAP with the following attributes: cn: workstation75$ description: Computer gecos: Computer gidNumber: 515 homeDirectory: /dev/null loginShell: /bin/false objectClass: top, account, posixAccount uid: workstation75$ uidNumber:

Hello, I have a Samba 3.0.11/LDAP-Backend PDC configured and I am able to join all kinds of machines quite well. However my Samba 2.2.12 Linux Fileserver is just able to join the domain: ---snip--- [573]root@hal/opt/samba> smbpasswd -j <Domainname> -r <PDC Name> -U Administrator Password: Joined domain <Domainname> ---snip--- When I now try to access my Fileserver with a

Hello, I've got a somehow weird problem with the primary GID of samba users. passdb backend is tdbsam. when I connect to the samba server my gid is set to 2147483404 instead of 1002 (domainusers). The GID 1002 ist configured as my primary group in /etc/passwd. This also happens with other usernames. After deleting group_mapping.tdb this worked for some hours but the error came back.

Hi, I have a samba server which should act as a domain controller. I did not set up the server by myself. I can "see" and use the servers shares with windows and linux clients. Everithing - including the security settings - for the shares works as expected. I can join a client to the domain, this works with manual adding the machine account as well as with the adduser script . I

Hi, I try to install my linux as PDC. I followed the samba project documentation and some other doc. My samba is 3.0.0 alpha2.4 My smb.conf is with the user securrity, domain logons etc... Just like it should be I added the computername with the "$" sign Added the computername in smbpasswd but when i try to connect with my win2000 workstation i get "unknown user name or bad

I've had the following setup working for years now. Subnet A contains linux/windows workstations along with the PDC+LDAP. Subnet B contains a BDC+LDAP and a domain member on the file server that windows users connect too. Whats new is I'm setting up a new domain member in Subnet B. It has joined the domain and net getdomainsid works. From machines in Subnet B I can run smbclient -L and

Hi list, I have the problem, that a samba 2.2.8a server cannot validate the password with a samba 3.0 pdc for a client request. A samba 2.2.1 works fine. Let me explain the situation in more detail: samba 3.0 pdc machine a samba 2.2.8a server machine b (doesn't work) samba 2.2.1 server machine c (works) samba 2.2.8 client machine d Machine b and c should authenticate the passwords

I am unable to mount a share using WinXP from samba 2.2.2 on RH linux. The same share works correctly with Win95 clients. WinXP reports this error: The mapped network drive could not be created because of the following error: The account is not authorized to login from this station. I looked through various archives and applied the registry patch for requiresignorseal=0 in this

after setting up a PDC with ldap according to the book samba 3 by example, almost everything worked out fine, the validations listed in the books turned out as expected with minor differences, but these are the problems : 1. According to the book the account that can be used to join a domain is the Administrator account with the password set from the ldap admin dn which is secret is my

Hi, I encountered a strange problem...some of my windows machines cannot be joined to an Samba 4.17 AD domain (8 of ~90 clients). These are 7 Win7 clients and one WinXP client. The message I receive in windows is: "Logon failure: unknown user name or bad password". All other Win7 and XP machines could be joined...the same OS image has been used to install both the machines that could be

Hi Davor, thanks for the answer. They were actually part of a NT4 domain called mayweg.net (the new realm name). But I did join workgroup "WORKGROUP" before I tried to join the new domain. If it's possible that they're sending the information the wrong way because they were part of a workgroup named after the new realm, is there any way to clear the old data (apart from a new