Displaying 20 results from an estimated 1000 matches similar to: "Samba 2.2.3a, print queue status "opening,"highserver load"
2002 Feb 25
2
Samba 2.2.3a, print queue status "opening," high server load
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
1999 Jun 21
0
Samba 2.0.x unusable for this environment
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
1998 Oct 12
1
locking for multiple samba servers sharing same NFS filesystems
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
1999 Feb 02
0
Samba 2.0 problem with Excel
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
1999 Jul 09
1
Samba 1 vs. 2, locking and Windows Terminal Server Edition
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
2004 Apr 14
0
Authentication problem using userid@mydomain.com format
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
2004 Apr 16
0
Strange authentication problem - Samba 3.0.2a
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
1999 Jul 15
3
"shared mem size" parameter and smbstatus
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
2006 Sep 26
1
Samba cannot
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
1998 Mar 27
1
NT4.0 rename on Samba 1.9.18p2 share on SunOS 4.1.3
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
2004 Apr 30
1
Authentication issue still exists in 3.0.3
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
2002 Feb 27
2
2.2.3a printing problems: no printing from Word, spools taking up all CPU on clients
I'm running Samba-2.2.3a plus the printer defaults patch (samba-2.2.3a-5mdk
rpm) on a Linux 2.4.(Mandrake 8.X). This server has been upgraded from
2.2.3, from 2.2.2, which was upgraded from 2.2.1. Everything was working
with the same printer configuration at version 2.2.2 and 2.2.1 (although I
have moved the WINS server from a new machine since then).
The server is a PDC/WINS server, and
2002 Feb 22
1
Password about to expire -- Turn Windlows Client Password Ageing Off?
I have a Domain controlled by a (Samba 2.2.2 upgraded to) Samba 2.2.3a PDC,
with
unix password sync = yes
The PDC (on a Mandrake Linux 8.X box) does not use password ageing, and we
don't want password ageing on our network.
We have a mix of Windows 98, NT4 and 2000 client workstations.
Unfortunately, some of the Windows 2000 users who log in to the domain have
complained that Windows is
2002 Feb 22
1
Antwort: Password about to expire -- Turn Windlows Client Password Ageing Off?
Hi,
there is a "X" value for the acount flags in smbpasswd ... it means no
password expiry! I found it on passdb/passdb.c. If it work?s, maybe I
don?t no! Also the password expire time ist hard coded in passwd.c too ...
set to infinity.
Take a look at the passwd.c code!
Regards, Thomas
Gesendet von: samba-admin@lists.samba.org
An: <samba@lists.samba.org>
Kopie:
2000 Mar 29
3
Samba 2.0.6 Interfaces
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
1999 Sep 08
9
oplock_break problem
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
2002 Sep 11
0
FW: Problems with new users since upgrade to Samba 2.2.5
-----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
2001 Apr 09
1
James Nord's reply to Win2K and multiple Samba 2.07 servers
Hello again,
Thanks James for your replies.
In regards to the slow read/write, the software vendor is aware of the
problem, at some stage they will buffer the read/write, but it won't happen
overnight, the binary file is quite complicated. So there are no updates
available for this particular issue and I don't expect any for a couple of
months. The software in question can generate
2003 Nov 28
1
USRMGR.EXE administration: invalid syntax error message
I try to admin Samba 3.0.0 and 3.0.1pre3 (tried both versions) NT4.0
PDC with NT4.0 machine and NT4.0 USRMGR.EXE and get persistent error
message
1) The group name could not be found
2) The user name could not be found
3) The filename, directory name, or volume label syntax is incorrect.
Loggin into domain under name: root
I can see the user and group listing. When I click on a user to see
his
2003 Oct 15
1
FW: Re: domain groups accessing samba share
-----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