similar to: NT4.0 rename on Samba 1.9.18p2 share on SunOS 4.1.3

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

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

Dear All, I manage a Debian Squeeze GNU/Linux (with kernel 2.6.32-5-686 #1 SMP) with Samba 3.5.6 (samba 2:3.5.6~dfsg-3squeeze8 package is installed). I have a "test" directory with native Linux ACL permissions. getfacl test's output: # file: test # owner: akos # group: grp # flags: -s- user::rwx group::rwx group:read:r-x mask::rwx other::--- default:user::rwx default:group::rwx

Hi, I am running Linux on RedHat 5.0 and Samba 1.9.18p2 to wish to connect to an NT 4.0 server running NT LAN Manager 4.0. I have gone through the documentation and can still not get smbmount nor smbclient to work. I cannot get smbclient -L to give me a listing of the shares on the server. I DO get a browser list, but no shares. I only have partial access to the server and must go thru the

One more after this, and "make syntax-check" will pass once more. >From 5c360133c0d4e09531d432abca0629798b87ff39 Mon Sep 17 00:00:00 2001 From: Jim Meyering <meyering at redhat.com> Date: Mon, 9 Nov 2009 15:14:53 +0100 Subject: [PATCH libguestfs] indent with spaces, not TABs * HACKING: Expand indentation TABs. * configure.ac: Likewise. * daemon/daemon.h: Likewise. *

I need to be sure that Wine will be able to run some of my XP applications before I commit to linux, so I installed Lucid Puppy 525 ( a cut down version of Lucid) and Wine - the default install version is set to v1.1.43, so that wasted a lot of time. I then installed Wine v1.3.13 , since the stable v1.2 wasn't on offer. I'm going to need Java Runtime Environment, so I started by

From: "Richard W.M. Jones" <rjones at redhat.com> Don't assume that if guestfs_case_sensitive_path returns NULL, that it means the file does not exist. The (previously undefined) behaviour of case_sensitive_path was that a NULL return meant "either the file doesn't exist or some other error". However in commit 973581780d8a006f336684fef6762801402d775d this was

Proposed patches to fix https://bugzilla.redhat.com/show_bug.cgi?id=858126

As described here previously: https://www.redhat.com/archives/libguestfs/2010-March/msg00129.html Here is the three part patch to reimplement virt-win-reg to support exporting and merging Windows Registry entries in the 'regedit' format. Tested by me on a local Windows VM. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-top is 'top'

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