similar to: Strange authentication problem - Samba 3.0.2a

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

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

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

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

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

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

Hi, I have referred to the archive and some of you were having the oplock_break problem. Does anyone have any solution for this? Will reboot fix the problem? Please advise. regards, Bridget

-----Original Message----- From: VR-Bug Support Sent: 15 October 2003 13:42 To: 'Gavin Davenport' Subject: RE: [Samba] Re: domain groups accessing samba share Hi Gavin, This is what I have for my /etc/pam.d/login #%PAM-1.0 auth required pam_securetty.so auth sufficient /lib/security/pam_winbind.so auth sufficient /lib/security/pam_unix.so nodelay

dear list. this question is rather related to samba, although not exclusively. I consider it related enough to ask here, please apologise if you don't. we are in the process of setting up a samba domain at my company. a goal is to replace our current nt4 servers. another goal is to provide an easy way to access the documents on the lan (and peoples home directories) from 'outside'

John Rosatti, Excavators, 3D, NASA and Why Should I care? Well, because! There are two definitions for excavator; one is any person engaging in excavation is called an excavator. The second definition of excavator is, of course, the vehicles called excavators, which are sometimes called diggers, trackhoes, fronthoes, and 360-degree excavators or just 360. This is not to be confused with

Hi, This is a message requesting help for the following problem: Printing Word 97 documents, stored on a Samba server, on an NT4 system to an LPD print queue fails under certain well-defined conditions, creating an empty file called 'Ne<number>:' (e.g. 'Ne120:'). The problem appears to be easily reproducable, as long as you have more than 99 print queues on your NT system.

hello all. I know this is a little bit of topic, but I guess this will interest of you anyway, and I didn't know where else to ask... So here it is: Does anyone here provide a webdav remote access interface to the network? And if yes: what software are you using for it? I'm currently doing this on my network using davenport. (http://davenport.sourceforge.net/) Even though this works

Unwanted space (padding?) is introduced at the extremes of the x and y axes of my lattice plots. I've tried defining the scales using xlim, scale and num.limits in x.scale.components, but haven't succeded in getting overriding the introduction of extra space. Here's the problem: