similar to: Samba cannot

Printing from NT4.0 clients to Samba 2.2.3a using the NT4.0 drivers from HP works fine for me, my only problem has been with W2K clients using the W2K drivers from HP. The drivers from www.hp.com appear to be level 3 drivers, that is where they install, and they are downloaded by W2K drivers if they are available when the NT4.0 drivers are also available. Now, whether these drivers from HP are

I've just upgraded to Samba 3.0.2a from 2.2.8a, and I've run into a problem. We have an automated build process for our Windows PCs where first a Windows XP Pro image is copied onto the machine, then after a reboot the local administrator is autologged on and a drive is mapped from the Samba server using Active Directory domain credentials. At this point the new machine hasn't

This problem appears to be a bug. I am seeing the problem running Samba 3.0.2a on both Solaris 8 and RH Linux ES3. This problem was not present in Samba 2.2.8a. The Samba servers are member servers of an Active Directory domain, and all other file and print sharing is working well. Global section of smb.conf included below. On a Windows XP client that hasn't been added to Active

I have Samba 2.2.3a installed and running successfully on Solaris 8 in a test environment. I manually enter printer shares into the smb.conf file, and then I can upload printer drivers to the Samba server from a Windows session without problems. When I try to print to a print queue on this server from a Windows 2000 SP2 machine, the application I am printing from hangs, the CPU usage of the smbd

I wrote about this problem more than a week ago, but got no response. I upgraded to 3.0.3 hoping this issue would go away, but it hasn't. I am seeing the problem running Samba 3.0.2a or 3.0.3 on both Solaris 8 and RH Linux ES3. This problem was not present in Samba 2.2.8a. The Samba servers are member servers of an Active Directory domain, and all other file and print sharing is working

I just attempted to upgrade from Samba 1.9.18p10 to Samba 2.0.4b, and I have had to revert to 1.9.18p10 in less than a day. I attempted to upgrade to 2.0.1 back in January, and had to back off as well. I was hoping the problems I saw then would be resolved in 2.0.4b. I sent a message to this list back in January or February as well, but saw no responses. My environment is about 210 Win95 PCs

Is there any support for file locking in a case where multiple Samba servers are set up with shares for the same NFS mounted filesystem? I don't know how the STATUS..LCK file is used, but for instance, could that file be shared between the multiple Samba servers via and NFS mount? Thanks! -- --------------------------------------------------------------------- Jay D. Anderson

I recently upgraded to Samba 2.0, but I have had to revert back to 1.9.18p10 because of problems I could not resolve. I am running Samba on a Sun Ultra-1 with Solaris 2.6, and I compiled Samba using gcc v2.8.1. The problems I was seeing were with saving Excel files. A user might have a small Excel file and try to save it to their home directory. The save would work for a long time (5 to 10

On Samba 1.9.18p10 and previous versions, each of the multiple users on the same Windows Terminal Server Edition machine would get their own smbd process. With Samba 2.0.x (I'm currently testing 2.0.4b), this has changed so that every user on a WTSE machine uses the same smbd process. File ownerships are assigned correctly, but file locking does not work. If one user on a WTSE machine has a

I am trying to use the "shared mem size" parameter in Samba 2.0.4b, but the size reported by smbstatus does not match the value I am using. Without the parameter, the default is 1MB, and the size reported by smbstatus is indeed 1048576. However, when I set the value of "shared mem size" to 5242880 (5MB), smbstatus says 879608. Is smbstatus not reporting the actual size, or

I am seeing an odd behavior with NT4.0 SP3 workstations trying to rename files on Samba 1.9.18p2 shares on SunOS 4.1.3 servers. Rename, whether it is run from Explorer, winfile.exe, or command prompt fails with "Access Denied I don't see the problem from Win95 PCs at all, and I don't have the problem with shares from Samba 1.9.18p2 shares on Solaris 2.5.1 servers using identical

Hello all, I am trying to make one of my solaris server member of our w2k3 ads domain. ldap and kerberos packages are installed. * when I try to get a ticket granting ticket, no problem ... kinit klist are all running fine .. below my krb5 config file # cat /etc/krb5/krb5.conf [logging] kdc = FILE:/var/log/krb5/krb5kdc.log # admin_server = FILE:/var/log/krb5/kadmind.log default =

Hello, We are using samba-3.0.25a and we want to join our system onto the Active Directory server in a specific location. The argument 'createcomputer' is exactly what we want and it works perfectly when we do a 'net ads join' but fails when we do a 'net rpc join'. The computer object always gets created in the 'Computers' folder. Looking at the code it appears

How can I find the correct path of the ou? When I di this: net ads join createcomputer="Servers/Windows/Computers/AD test" -U Administrator I receive the following error: Administrator's password: Failed to pre-create the machine object in OU createcomputer=Servers/Windows/Computers/AD test. Failed to join domain: No such object

On Tue, 06 Feb 2018 14:09:08 -0500 Dan Oriani via samba <samba at lists.samba.org> wrote: > > I'm not opposed to the idea. Does 'net ads join' support supplying > the machine name as the user, and the one-time-password given to it? > The only reason I'm using adcli at all is the preset-computer option > which I couldn't find an analogue to in 'net

I am trying to reconfigure a samba server to use authentication from the University domain. * smbd seems to start OK * net ads testjoin is fine * net ads join -U xxUSERNAME createcomputer="xxCOMPUTER" fails with: Failed to join domain: failed to set machine spn: Constraint violation (where xxTEXT indicates redaction - sorry I'm not sure what's confidential and what isn't)

-----Original Message----- From: Davenport, Tom Sent: Wednesday, September 11, 2002 3:04 PM To: 'Javid Abdul-AJAVID1' Subject: RE: [Samba] Problems with new users since upgrade to Samba 2.2.5 I create an NT user acct then I go the UNIX box and create a UNIX acct. I have matched the acct settings for the new users to the old users on both sides. I should mention that the problem is with

Quoting Dan Oriani via samba <samba at lists.samba.org>: > Quoting Rowland Penny via samba <samba at lists.samba.org>: > >> On Tue, 06 Feb 2018 14:09:08 -0500 >> Dan Oriani via samba <samba at lists.samba.org> wrote: >> >>> >>> I'm not opposed to the idea. Does 'net ads join' support supplying >>> the machine name as

Has anyone had any success using net ads join to create a new service principal and join Active Directory using samba 3.5.8. This works fine in 3.0.35 but I'm not able to get a working create/join with 3.5.8 In samba 3.0.35 (on a host which is already allowing kerberised loginsvia AD), the following works: net ads join createupn='CIFS/host.domain.com' \

Quoting Dan Oriani via samba <samba at lists.samba.org>: > Quoting Dan Oriani via samba <samba at lists.samba.org>: > >> Quoting Dan Oriani via samba <samba at lists.samba.org>: >> >>> Quoting Rowland Penny via samba <samba at lists.samba.org>: >>> >>>> On Tue, 06 Feb 2018 14:09:08 -0500 >>>> Dan Oriani via samba