similar to: Authentication problem using userid@mydomain.com format

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 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

With Samba 3.0.23c I am unable to join the server to AD. The command and messages return: # ./net ads join createcomputer=OUlevel1/OUlevel2/Servers -Uadminacct adminacct's password: Using short domain name -- DOMAIN Failed to set servicePrincipalNames. Please ensure that the DNS domain of this server matches the AD domain, Or rejoin with using Domain Admin credentials. Disabled account for

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 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

I am having a problem with mapping drives to a samba server (1.9.18p4 and 1.9.17) that is very reproducible. The 1.9.18p4 is a modified server that has some special krb5 support in it (in addition to the stuff you previously added that I sent you). Here are two examples that are repeatable. Each is preceeded by killing any samba daemons that are for connections from the host in question.

Complete new user here. Setting up my first samba configuration, using samba 4.0.6 as a primary domain controller. I have user profiles, network shares, active directory, and domain controller working. But I can not understand how to map windows userid to linux userid (and map groupid as well). I am struggling because much of the documentation is outdated and meant for samba 3.x or targetted

I have a Linux Samba server I access from a Win2K system. I want to allow a process started from a Windows "service" to access a share on the Samba server. The Windows service is set to run as "LocalSystem" instead of a specific userID. What userID do I need to define on the Samba server to allow "LocalSystem" to access files on a Samba share? -- Jim Garrison

Samba 3.0.5 Debian Package Kernel 2.6.7 custom compile on Debian Testing Configure Samba per my KLUG presentation on Samba PDC to Win2K Clients: ftp://ftp.lueckdatasystems.com/pub/presentations/klugsamba3pdc-bookreview.pdf In the error condition, a user account is assigned to the domadmin and ntadmin Linux groups. In smb.conf -> admin users = @domadmin On the workstation there are mappings

Thanks Mike. I'll investigate ssd although it shouldn't be too hard to have sendmail rewrite the userID to remove the domain. I'm investigating this now and will post results. --Mark -----Original Message----- > From: Data Control Systems - Mike Elkevizth <mike at datacontrolsystems.com> > Date: Thu, 21 Jul 2016 12:30:19 -0400 > Subject: Re: [Samba] sendmail getting

We're had some recurring problems with nmbd's on Solaris 2.7 and Irix 6.5 failing to renew their WINS registrations in a timely manner causing the records to become tombstoned. While we've solved it by issuing "pkill" and "killall", respectively, of nmbd nightly from root's crontab, I wanted to alert the authors and other administrators to the problem so similar

I added via visudo my userid for authorization of me ALL(ALL) NOPASSWD: ALL and I still cannot run yum as me. Is this just not possible?

I need/desire to set up a userID for an SSH tunnel, but not allow said user to have a login to the server. For the user to set up the tunnel with: ssh -p 1234 -L 8080:192.168.1.4:80 george at gateway.foo.com Where george would use a password instead of a stored SSH key, could george be created with: useradd -s /sbin/nologin -c "George" george passwd george thanks

Dewayne, Thanks a lot for this patch. I'll hang on to it any probably do some experimenting on the side. The problem with this approach is that our AD/DC/Mail-server is in an office and I have to be concerned about future sysadmins as well as future sendmail updates. I am very reluctant to patch OS software, especially if other solutions are available. At worst, I can drop back and remove